Netlify Pricing Explained: Free, Personal, Pro, and Enterprise

Netlify's Free plan costs $0/month with 300 credits, and unlike some competitors, Netlify's own materials state that commercial projects are allowed on it - the limit is your credit usage, not what kind of project it is. Every Netlify plan, free through Enterprise, runs on the same underlying credit system; what changes plan to plan is how many credits you get and which extra features come with it. This checks Netlify's own current pricing page and docs, dated September 2026, for what each plan actually costs and includes. Our Netlify vs Vercel comparison covers the same Free-plan commercial-use point if you're choosing between the two, and our Vercel pricing guide covers Vercel's plans in the same format as this one.

What does the Free plan actually include?

Free is $0/month with a 300-credit monthly allowance, and Netlify's pricing page lists it as built for an "Individual" (Netlify, "Pricing and Plans", checked September 2026). Its feature list on that page includes "Deploy from AI, Git, or API," "Private by default until you publish," unlimited deploy previews, custom domains with SSL, Functions and AI models, Netlify Database for structured data, Blob storage for files and images, and basic firewall traffic rules and rate limiting.

On the commercial question specifically, Netlify's own blog introducing this plan is direct: "On the Free plan, you can deploy commercial projects, personal sites, or other creative explorations you want to share on the web" (Netlify, "Introducing Netlify's Free plan", checked September 2026). The constraint on Free isn't project type - it's whether 300 credits a month covers your actual usage.

What do credits actually cost, and what happens when they run out?

Credits convert to real spend at a stated rate - Netlify's pricing page prices them at $10 per 1,500 credits, or roughly $0.00667 per credit - and different actions draw down your balance at different rates:

(Source: Netlify, "Pricing and Plans", checked September 2026.) That's a real difference from a plan that meters bandwidth and compute separately - on Netlify, a busy month of deploys can compete with a busy month of traffic for the same pool, so a site that deploys constantly and also gets real traffic can burn through its allowance from either direction.

Running out isn't a soft warning - Netlify's own documentation describes a hard stop: "Once your credit balance is completely used up, all of your web projects (sites/apps) are paused and visitors to your web projects will find a Site not available page at each of your web project's URLs" (Netlify Docs, "How credits work", checked September 2026). That applies to every project on the account, both custom domains and Netlify's own .netlify.app subdomains, until the next billing cycle resets the balance or you add more credits.

What does the Personal plan add?

Personal is $9/month for 1,000 credits, also positioned for an "Individual" account on Netlify's pricing page (same source). It's everything in Free, plus smart secret detection, one day of observability data, and priority email support. It's the middle step for someone who's outgrown Free's 300 credits but doesn't need Pro's team features.

What does the Pro plan cost and include?

Pro is $20/month "with unlimited members," per Netlify's own listing, and includes 3,000 credits at its entry tier (Netlify pricing). Netlify positions Pro for a "Team" rather than an individual account. On top of everything in Personal, Pro adds private organization repositories, shared environment variables, "3+ concurrent builds," and "30-day analytics & metrics." The unlimited-members detail matters if you're comparing this to a per-seat pricing model elsewhere - Netlify doesn't charge Pro by headcount, only by the credit pool the whole team draws from.

What does Enterprise cost and include?

Enterprise pricing is custom, with unlimited credits included (same source). Beyond Pro, Netlify's page lists a "99.99% SLA," an enterprise network tier, high-performance builds, SSO and SCIM for identity management, log drains, and organization-wide management tools, plus "24/7 dedicated support." As with most enterprise tiers across hosting vendors, there's no public number here to compare - it's a sales conversation once your team needs SSO or a contractual SLA.

Which plan actually fits which situation?

• A personal project, including one you're monetizing: Free, as long as 300 credits genuinely covers your deploy frequency and traffic - Netlify's own materials don't gate this by project type the way some competing free tiers do.
• You've outgrown 300 credits but you're still one person: Personal, for the extra credit headroom plus secret scanning and priority support.
• A team that needs shared repos, more concurrent builds, and real analytics: Pro, priced by credits rather than seats.
• A team that needs an SLA, SSO/SCIM, or dedicated support: Enterprise - talk to Netlify's sales team for a number.

Where does this fit with an exported or AI-built project?

If your codebase came out of an AI builder, Netlify is a documented deploy target for it - Lovable's own docs list Netlify (alongside Vercel) among the platforms that "connect directly to your GitHub repository and automatically build and deploy on each push" (Lovable Documentation, "Deploying and hosting outside Lovable", checked September 2026). Whichever host you pick, the underlying checklist doesn't change: re-enter your environment variables and secrets, confirm your database connects independently of the builder, and update any OAuth callback URLs before cutting traffic over. Our Netlify vs Vercel comparison covers the free-tier trade-off between the two in more depth if you haven't picked a host yet.

If you're publishing a reviewed folder of plain HTML and CSS rather than deploying a framework project, our checklist for publishing an AI-generated static site walks through Netlify's manual-deploy path specifically, plus the public-URL checks that apply regardless of host.

Figment doesn't compete in this space directly - a site published from a Figma design through Figment is hosted on Figment's own infrastructure by default, with HTML/CSS export on Figment's paid plans if you'd rather self-host the result on Netlify yourself.

Bottom line: Netlify's four plans - Free, Personal, Pro, Enterprise - all share one credit system rather than separate named quotas per resource, and Netlify's own materials treat commercial use as allowed even on the free tier. The real planning question isn't what kind of project this is; it's how many credits your deploys, bandwidth, compute and requests will burn in a month - and that number is worth checking against your plan before you rely on it in production.