Netlify pricing

About

Netlify is a web development and deployment platform (a frontend cloud / PaaS) that lets developers deploy sites and apps from Git, an AI agent, or an API, with a global CDN, serverless functions, edge rendering, a managed database, and blob storage. In 2026 Netlify has leaned into agentic development, adding Agent Runners (running AI agent tasks in the background) and an AI Gateway for adding AI-model functionality to projects.

Founded in 2014 by Mathias Biilmann and Christian Bach, Netlify popularized the “Jamstack” architecture and grew into a frontend cloud used by a community that surpassed 8 million developers by 2026. It raised roughly $212M across its Series A–D rounds, reaching a $2 billion valuation in its 2021 Series D led by Bessemer Venture Partners, and acquired Gatsby (2023), OneGraph (2021), and FeaturePeek (2021) along the way. Its primary competitor is Vercel; both compete with self-host alternatives like Coolify and Dokploy and with hyperscaler edge products.

Netlify serves everyone from individual developers building side projects to enterprise engineering organizations. Its 2026 pricing is deliberately seat-free: paid plans are a flat monthly fee (Personal $9, Pro $20 with unlimited members) plus a credit-based usage pool, with an Enterprise tier for teams that need SLAs, SSO/SCIM, and dedicated support. That structure is a sharp break from the per-seat model Netlify ran for most of its history, and it was re-architected explicitly for AI-paced development where a single developer can trigger hundreds of deploys and large inference bills.

Pricing summary : credit-based usage pool across four flat-fee plans

Netlify uses a freemium + credit-based usage model with two dimensions:

1. Flat plan fee: Free ($0 forever), Personal ($9/month), Pro ($20/month with unlimited members), and Enterprise (custom, starting at $500/month). There is no per-seat charge.
2. Monthly credit pool + usage: Each plan includes a credit allotment — 300 credits (Free), 1,000 credits (Personal), 3,000 credits (Pro) — consumed by usage. Metered usage rates: production deploys 15 credits each, AI inference varies by AI model, compute 10 credits per GB-hour, bandwidth 20 credits per GB, and web requests 2 credits per 10,000 requests.

What makes this different: Netlify folds heterogeneous usage — deploys, compute, bandwidth, web requests, and AI inference — into a single credit-based billing currency, and its Pro plan removes per-seat pricing entirely (unlimited members for $20/month). The result is a freemium plan fee layered over a pure-usage credit pool — the same entitlement-to-credits shift reshaping AI-era billing across the corpus.

Pricing by product

Netlify platform (plans)

Usage credits (metered — draws down the monthly pool)

Sales motions across products: PLG / self-serve for Free, Personal, and Pro (sign up and pay online); sales-led for Enterprise (custom quote, $500/month floor).

AI inference pricing (Agent Runners & AI Gateway)

AI inference is a usage meter that covers both Agent Runners (running AI agent tasks in the background) and AI Gateway (adding AI-model functionality to a project). Netlify measures AI inference by the cost set by AI-model providers, converting model-usage tokens to USD, and then converting every $1 USD of AI-model spend to 180 Netlify credits. There are no special AI-Gateway credits — it draws from the same plan credit pool (or add-on credits).

Netlify publishes per-model USD token rates (per 1 million tokens) before the credit conversion. Providers supported: Anthropic, Gemini, and OpenAI. A sample of published rates (per 1M tokens):

Per Netlify AI features pricing docs (rates last updated Jun 16, 2026). These provider rates are subject to change with the market and are the pre-conversion USD basis; actual billing converts $1 to 180 credits.

Hidden costs : how the credit pool and AI inference convert to real bills

The $9 / $20 plan fees understate what heavy AI-inference or high-bandwidth users pay once the included credit pool (300 / 1,000 / 3,000 credits) is exhausted and add-on credits are consumed. The dangerous dimension is AI inference: the meter is 180 credits per $1 of underlying model spend, so a Pro plan’s entire 3,000-credit pool corresponds to only about $16.67 of raw model spend before the pool is gone. The historical worst case is bandwidth — the $104K DDoS bill (see Pricing evolution) — which today would draw down 20 credits per GB.

Archetype A: an AI-agent side project on Pro

A solo developer on Pro ($20) uses Agent Runners to iterate on an app, spending roughly $30 of Claude Sonnet inference in a month, plus modest compute and bandwidth.

Lesson: even light agentic use doubles the headline $20 fee, because the included pool is sized for human-paced iteration, not for an agent making dozens of model calls per task.

Archetype B: a small team hit by a traffic spike

A 5-person team on Pro serves a viral asset and pushes 4TB of bandwidth in a month.

Lesson: a single heavy dimension — bandwidth or AI inference on a large model — can exhaust the included credits and drive add-on-credit purchases far beyond the $20 base. Setting an AI inference spending limit and monitoring the credit balance is essential; see thresholding and alerting on usage and our take on AI cost unpredictability and bill shock.

Want to estimate your own Netlify bill? Use the Netlify pricing calculator to model your monthly cost based on deploys, compute, bandwidth, web requests, and AI inference. (Netlify also offers a cost calculator on its own pricing page.)

Pricing evolution : from seat-based hosting to a credit-based usage pool

Netlify’s pricing arc runs from a per-seat, multi-metric legacy model to a seat-free credit pool re-architected for AI-paced development. The Wayback CDX API was unreachable at capture time, so no historical pricing-page screenshots are attached; the dates and figures below are sourced from Netlify’s own blog/changelog and corroborating community threads rather than archived captures.

Cadence

Tracked range: 2022-06 to 2026-07. Quarters not listed were verified stable against the sources cited (0 price changes, 0 SKU additions found).

Notable changes

• 2022-06-02 — Seat-based plan changes (raised limits, forced 7+ member teams to Enterprise, billed Git contributors) triggered a contentious Hacker News reaction (“Tell HN: Netlify changing Starter plan”).
• 2022-06-13 — Partial walk-back: Netlify paused the build-trigger change and introduced the paid Git Contributor role (netlify.com/blog/changes-to-our-recent-pricing-update/).
• 2024-02-27 — The $104K bill-shock incident: a free-tier static site absorbed ~190TB of traffic; the CEO waived the bill after the Reddit post reached 1,783 upvotes (corroborated by cybernews.com).
• 2024-12-11 — New always-free Free plan with hard usage notifications at 50/75/90/100% of monthly limits (netlify.com/blog/introducing-netlify-free-plan/).
• 2025-09-04 — Credit-based pricing launches for new accounts, collapsing 15+ metrics into one credit balance and adding AI-inference metering (netlify.com/changelog/netlify-pricing-update-introducing-credit-based-plans/).
• 2026-04-14 — Seat-based pricing removed from the credit Pro plan; $20 per seat becomes a flat $20/mo for unlimited members (netlify.com/changelog/2026-04-14-pricing-updates-april-2026/).

The $104K bill in detail

In February 2024, a developer discovered a ~$104,000 Netlify bill on what had been a free-tier static site with ~200 daily visitors. Investigation traced it to a single 3.44MB MP3 file downloaded roughly 55 million times over several days — about 190TB of egress. Netlify first offered a discount to a ~$5,000 liability; once the Reddit r/webdev post trended (1,783 upvotes, 798 comments), the CEO waived the charge entirely. The episode is a canonical usage-based bill-shock case because, at the time, Netlify offered no spending-limit capability — the meter simply ran. Netlify’s later moves map directly onto this: the December 2024 Free plan added staged usage notifications and instant-upgrade prompts, and the credit-based plans expose an AI inference credit usage limit that halts new agent runs and pauses AI Gateway when hit. The lesson for any usage-priced platform — hard caps and default alerts are a trust feature, not an edge case — echoes our analysis of AI cost unpredictability and bill shock.

What’s unique : credit-based usage and seat-free Pro pricing

One credit currency across everything. Netlify collapsed what it describes as 15+ separate metrics, add-on packages, and usage tiers into a single credit balance. Deploys (15 credits each), compute (10 credits/GB-hour), bandwidth (20 credits/GB), web requests (2 credits/10k), and AI inference all draw from the same monthly pool. That is a rarer commitment than most “credit” systems, which typically reserve credits for one dimension (e.g., AI features) and bill the rest separately. It maps onto the hybrid credit-pool model seen at peers like Vercel and Cursor.

AI inference priced as a pass-through, not a markup. Netlify meters AI at 180 credits per $1 of underlying model spend, and publishes the raw provider USD token rates (Anthropic, Gemini, OpenAI) that feed the conversion. There is no separate “AI credit” — the AI meter tracks provider pricing almost transparently, which is unusual: many platforms bundle inference into opaque per-request or per-token markups. It is closer to a metered pass-through than a resold token model.

Seat-free by design, for AI-paced work. Removing per-seat pricing (April 2026) was not a generic simplification — Netlify framed it around AI development that “doubled our community in one year” past 8 million developers. When a single developer with an agent can generate hundreds of deploys, charging per human seat stops correlating with value; usage does. This is a deliberate value-metric change, not just packaging.

A visible Enterprise floor. Netlify publishes “Custom, starts at $500/month” on the Enterprise card — most contact-sales tiers hide any number. The disclosed floor sets buyer expectations and pre-qualifies self-serve teams before they ever talk to sales.

Bill-shock scars baked into the product. The December 2024 Free plan’s staged usage notifications and the credit plans’ AI inference credit usage limit are direct product responses to the 2024 $104K incident — an example of a pricing model that visibly encodes a past trust failure into its controls.

Strengths & weaknesses

Billing UX : credit pool controls, spending limits, and add-on credits

• Monthly credit pool — each plan includes a fixed credit allotment (300 / 1,000 / 3,000 credits on Free / Personal / Pro) shown on the pricing page and consumed by usage.
• AI inference credit usage limit — teams can set a cap on AI inference; once reached, no new agent runs can start, active agent runs stop, and AI Gateway usage is paused (per Netlify AI features docs).
• Add-on credits and auto recharge — teams can buy add-on credits and configure auto recharge when the pool runs low (per Netlify billing docs).
• Usage and billing insights — Account usage insights shows AI inference and other usage meters over time.
• Cost calculator — a Calculate your cost / Use our calculator tool on the pricing page models monthly cost from usage.

Strategic wins : what Netlify got right in the model shift

1. Re-based the value metric from seats to usage before rivals

By removing per-seat pricing, Netlify aligned billing with the thing that actually scales in AI-era development — usage, not headcount. When one developer plus an agent can do the work of a team, per-seat pricing both under-monetizes and annoys. Choosing usage as the value metric is the harder, more durable call, and it mirrors the broader SaaS-to-usage migration reshaping developer tools.

2. Made AI cost legible with a published pass-through

Rather than burying inference in an opaque markup, Netlify publishes provider USD token rates and a single 180-credits-per-$1 conversion. Legibility is a trust move: developers can sanity-check the AI meter against Anthropic/OpenAI list prices. It positions Netlify as a neutral conduit for AI spend rather than a reseller skimming margin invisibly.

3. Turned a bill-shock disaster into product guardrails

The 2024 $104K incident could have been a permanent reputation wound. Instead Netlify shipped staged usage notifications (Dec 2024) and an AI inference spending limit on credit plans — converting a trust failure into named controls. Encoding hard caps and default alerts is exactly the guardrail discipline we argue for in FinOps for AI cost management.

4. Kept a visible Enterprise floor to pre-qualify buyers

Disclosing “starts at $500/month” on the Enterprise card is a quiet win: it filters out teams that would waste sales cycles and anchors serious buyers. Transparency at the top of the range is rare and reduces friction in the self-serve-to-sales handoff.

Areas to improve : where the credit model still leaks trust

1. Right-size the included AI credit pool

3,000 Pro credits mapping to only ~$16.67 of raw model spend means any real agentic workflow blows through the pool almost immediately, making the “$20 Pro” headline feel like a teaser. Fix: publish an explicit “AI credits included” figure in dollars-of-model-spend terms on the pricing page, or raise the AI-inclusive allotment so the headline price survives light real usage.

2. Show cost per dimension, not just a credit balance

Collapsing everything into one credit currency simplifies the meter but obscures where money goes — a user cannot easily see “I spent $X on bandwidth vs $Y on AI.” Fix: in usage insights, break the credit burn back down into dollar-denominated dimension buckets so finance teams can attribute spend, in line with tracking and metering usage events.

3. Unify the plan lineage and make Legacy migration painless

Prospects now face Free/Personal/Pro/Enterprise credit plans plus a parallel Legacy plan universe for pre-September-2025 accounts. Fix: give legacy accounts a clear, incentivized migration path and a side-by-side “what your bill becomes on credits” estimator so the fragmentation resolves over time.

4. Default the spending caps ON

The AI inference credit usage limit and add-on-credit auto-recharge exist, but bill-shock happens when protections are opt-in. Fix: default a conservative spending cap and staged alerts for new accounts (as the Free plan already does), so the next $104K scenario is impossible by default rather than avoidable by expertise.

Key takeaways

1. Pick a value metric that survives your customers’ next efficiency gain. Netlify’s per-seat model quietly broke when AI let one developer do a team’s work; usage tracks value better in an agentic world. If your metric can be gamed away by a productivity tool, it is already obsolete.
2. Bill-shock is a trust problem, not a billing edge case. A single missing spending cap produced a $104K bill and a 1,783-upvote reputation event. Default alerts and hard caps are cheaper than the goodwill you lose without them.
3. Legibility beats margin games on AI cost. Publishing provider token rates and a single 180-credits-per-$1 conversion buys trust that an opaque markup destroys. Buyers increasingly back-calculate; assume they can see through resold-token pricing.
4. A visible Enterprise floor is a feature, not a leak. “Starts at $500/month” pre-qualifies buyers and sets anchor expectations; hiding all numbers just adds friction to the sales handoff.
5. Simplifying metrics has a hidden cost — attribution. Folding many meters into one credit currency is easier to track but harder to reason about. Give customers a way to see cost per dimension or you trade transparency for tidiness.

UBP implications

1. Credit pools are becoming the default packaging for heterogeneous AI usage. Netlify’s single-currency pool over deploys, compute, bandwidth, and inference shows how prepaid-credit models let a platform meter wildly different resources under one balance — the packaging pattern to watch as AI workloads mix compute and tokens.
2. AI inference is pushing platforms toward pass-through metering. When the underlying cost is a volatile third-party token price, resellers increasingly expose the provider rate plus a fixed conversion rather than a fat opaque markup — a structural shift in how usage-based pricing models handle bought-in cost.
3. Spending controls are graduating from feature to table stakes. Post-Netlify, a usage-priced platform without default caps and staged alerts carries reputational tail risk; guardrails are now part of the pricing model itself, not an afterthought.

Sources

• Netlify pricing page (accessed 2026-07-06)
• Netlify AI features pricing docs (accessed 2026-07-06)
• Netlify credit-based pricing plans (docs) (accessed 2026-07-06)
• Netlify changelog — introducing credit-based plans (accessed 2026-07-06)
• Netlify changelog — pricing updates (April 14, 2026) (accessed 2026-07-06)
• Netlify blog — changes to our recent pricing update (2022 walk-back) (accessed 2026-07-06)

Bottom line

Netlify in 2026 prices a frontend cloud on a credit-based usage pool with seat-free flat plans — Free, Personal ($9), Pro ($20 with unlimited members), and Enterprise (from $500/mo) — folding deploys, compute, bandwidth, web requests, and AI inference into one credit currency, with AI metered at 180 credits per $1 of underlying model spend.

Want to compare Netlify against other frontend-cloud pricing? Browse the pricing blueprint.

Pricing timeline : Major events on a vertical axis

Each milestone below corresponds to a public pricing change, product launch, or material adjustment. Major events use a filled marker; minor adjustments use a faded one.

Credit-based plans with Agent Runners and AI inference metering

Jul 2026

Netlify pricing is structured as Free ($0) / Personal ($9) / Pro ($20, unlimited members) / Enterprise (custom from $500/mo), each with a monthly credit pool (300 / 1,000 / 3,000 credits on Free/Personal/Pro). AI inference (Agent Runners + AI Gateway) is metered at 180 credits per $1 of underlying AI-model spend.

Seat-based pricing removed from credit Pro plan

Apr 2026

Netlify removed per-seat charges from the credit Pro plan: previously $20 per seat (including active Git contributors), now a flat $20/month for 3,000 credits with unlimited team-member seats. Framed by CEO Mathias Biilmann around AI development that 'doubled our community in one year' past 8M developers. Source: netlify.com/changelog/2026-04-14-pricing-updates-april-2026/.

Credit-based pricing launches for new accounts

Sep 2025

All new Netlify accounts moved to credit-based plans, collapsing 15+ separate metrics into a single credit balance and adding AI-inference metering (180 credits per $1 of model spend) for AI Gateway / Agent Runners. Pro at launch was still seat-based ($20/member/month, 5,000 credits/seat). Accounts created before 2025-09-04 became 'Legacy' plans with no forced migration. Source: netlify.com/changelog/netlify-pricing-update-introducing-credit-based-plans/ and netlify.com/blog/new-pricing-credits/.

New Free plan with hard usage notifications

Dec 2024

Netlify introduced an always-free Free plan (100GB bandwidth, 300 build minutes, 125,000 function + 1M edge-function invocations, 10GB storage) with usage notifications at 50/75/90/100% of monthly limits and no credit card required — a direct answer to bill-shock concerns. Source: netlify.com/blog/introducing-netlify-free-plan/ (HN item, 28 pts, 2024-12-11).

The $104K bill-shock incident (no spending caps)

Feb 2024

A developer's free-tier static site absorbed ~190TB of traffic — later found to be ~55 million downloads of a single 3.44MB MP3 — and Netlify issued a ~$104,000 bill. The Reddit r/webdev post reached 1,783 upvotes / 798 comments; after it trended, the CEO waived the entire charge. Netlify had no spending-limit capability at the time. Corroborated by cybernews.com and the Netlify support forum follow-up (answers.netlify.com/t/113472).

Partial walk-back: Git Contributor role, build-trigger change paused

Jun 2022

After the backlash Netlify published 'Improved workflow and new role for pricing changes': it paused the build-trigger change, introduced a paid Git Contributor role (auto-approved, removed after 30 days inactive, off by default), and kept the 7+ member Enterprise requirement with carve-outs for open source, early-stage startups, and agencies. Source: netlify.com/blog/changes-to-our-recent-pricing-update/.

Seat-based plan changes trigger community backlash

Jun 2022

Netlify raised limits and required teams of 7+ members to move to Enterprise on its legacy seat-based plans (Starter/Pro/Business, roughly $19/member/month). The change — especially charging for Git contributors who only triggered builds — drew a contentious Hacker News reaction ('Tell HN: Netlify changing Starter plan'). Prices on the pre-change plans are unknown here (Wayback CDX was unreachable at capture time; no historical screenshot). Source: news.ycombinator.com/item?id=31937401.