Netlify

What Netlify actually is

Netlify is a Git-connected deployment platform: push code, and the platform builds it, ships it to a global edge network, and gives every pull request its own preview URL. It started in 2014 as MakerLoop, founded by Danish entrepreneur Mathias Biilmann with Christian Bach joining as co-founder in 2015, was renamed Netlify in 2017, and is headquartered in San Francisco with a global team. The company coined the term "Jamstack" in 2016, raised through several venture rounds, and bought its way up the stack — FeaturePeek, OneGraph, Quirrel, Gatsby in 2023, and Stackbit — to move from static hosting toward a full application platform. Wikipedia records revenue of about $33 million (2023) with roughly 244 employees.

The product today is broader than the "static site host" label that still follows it. Alongside builds and CDN serving, Netlify offers functions and edge functions, forms, identity, split testing, structured data via Netlify Database, file storage via Blob, an AI gateway, and — as of late 2025 — Agent Runners that let AI agents open and deploy changes. In our view the core (atomic deploys, previews, edge delivery) is the part worth buying; the surrounding services vary in maturity and each one adds another dependency on Netlify's runtime.

The other thing to know before reading any review of this platform, ours included: pricing changed fundamentally in April 2026. Netlify moved from per-seat subscriptions to credit-based plans, made Pro seats unlimited, doubled bandwidth credit rates, and raised compute rates while cutting web-request rates. Anyone quoting you pre-2026 Netlify pricing is describing plans that new customers can no longer buy.

The company's recent direction is unmistakable: an official MCP server launched in June 2025, AI Agent Runners in October 2025, and a Windsurf IDE-native deployment integration before that. Netlify is positioning itself as the place where AI-generated code goes to become production software — the Bolt.new partnership alone claimed one million AI-generated websites on the platform. Whether or not you care about that pipeline, it explains where engineering effort is going, and it is consistent with the credit-based pricing model: meter what machines and agents actually consume instead of counting human seats.

Pricing: what you really pay

Current credit-based plans, as published:

• Free — $0 forever. 300 credits, deploy from AI, Git, or API, unlimited deploy previews, custom domains with SSL, functions, AI models, Netlify Database, Blob storage, firewall traffic rules and basic rate limiting, global CDN.
• Personal — $9/month. 1,000 credits, plus smart secret detection, 1-day observability, priority email support.
• Pro — $20/month with unlimited members. 3,000 credits, plus private organization repos, shared environment variables, 3+ concurrent builds, and 30 days of analytics and metrics.
• Enterprise — custom pricing. Unlimited credits, 99.99% SLA, enterprise network tier, high-performance builds, SSO and SCIM, log drains, 24/7 dedicated support.

Credits convert to usage at published rates: production deploys cost 15 credits each (about $0.10), compute is 10 credits per GB-hour (about $0.07), bandwidth is 20 credits per GB (about $0.13), and web requests are 2 credits per 10,000 (about $0.01), priced at the Pro credit pack rate of $10 per 1,500 credits. Auto-recharge packs are $5 for 500 credits on Personal and $10 for 1,500 on Pro.

What we make of this model: it is genuinely simpler than per-seat billing for teams — the April 2026 change that removed seat charges on Pro ended the old complaint that every Git contributor cost $20/month — and the per-unit costs are visible rather than hidden behind "contact us". But credits abstract real resources, and the April update simultaneously doubled bandwidth from 10 to 20 credits per GB and compute from 5 to 10 credits per GB-hour. A bandwidth-heavy site that felt cheap at the old rate should re-run the numbers. For comparison, the legacy Starter plan offered 100 GB/month then $55 per 100 GB and 300 build minutes then $7 per 500; legacy Pro was $19 per member per month with 1 TB and 25,000 build minutes. Legacy plans still exist for existing customers but new signups land on credits.

Performance & infrastructure

Netlify serves sites from a global edge network — the company's own description is worldwide edge locations with atomic deploys and instant cache invalidation, running on "the world's best cloud providers" without naming a fixed facility list. That makes our usual datacenter count meaningless here: there is no published number of locations to record, and we will not invent one. What matters instead is behavior: deploys are immutable snapshots, cache invalidation is instant on publish, and reverting production to any previous version is a single action — which is why we record "snapshots included" as yes for Netlify even though the word means deploy snapshots, not disk images.

Security defaults are better than the price suggests. All plans get automated network-wide DDoS protection by default, HTTPS on every custom domain, smart secret detection on paid tiers, and firewall traffic rules with basic rate limiting on Free. Advanced Web Security rules (access control and malicious-request protection) are the paid upsell.

We have not benchmarked Netlify — our dated sysbench, fio, and iperf3 runs cover VPS plans (see /benchmarks), and there is no meaningful CPU to measure on a managed deploy platform. The performance claims worth trusting are architectural: edge delivery close to users, no origin servers for you to run, and functions that execute at the edge when you write them as Edge Functions. The performance claim worth treating carefully is any latency number you read in marketing material, including Netlify's, because your result depends entirely on cache hit rates and how much logic you push to the edge.

Where it falls short

Credit pricing is new and has already moved once. Rates for bandwidth and compute doubled within the current pricing regime while seats became free — a reasonable trade for teams, a bad one for high-traffic static sites — and we would not assume today's rates are final. Budget with headroom and watch the changelog.

The dependency concentration is real. Builds, forms, identity, functions, database, and blob storage all live inside one vendor's runtime, and the more of them you adopt, the more your application is a Netlify application rather than a web application that happens to be hosted there. Portability is highest for static assets and lowest for identity, forms, and edge functions. We like the platform; we still advise keeping your data and auth layer replaceable.

Support scales with plan in the usual way: community and forum support on Free, priority email on Personal, and the 99.99% SLA plus 24/7 dedicated support only on Enterprise. Netlify has had high-profile platform incidents over the years, and without an SLA on the self-serve tiers you carry that risk yourself. Finally, the build system is powerful but opinionated — complex monorepo or non-standard build workflows sometimes fight it, and heavy builds burn credits at 15 per production deploy plus compute time.

Who should pick this

Our pick for frontend teams whose workflow is "merge to Git, ship to production." Marketing sites, docs, JAMstack storefronts, and SaaS frontends that want deploy previews on every pull request, instant rollback, and zero server administration get the most out of Netlify, and the Free plan (300 credits, unlimited previews) is enough for real projects. The Pro plan at $20/month with unlimited members is now one of the better team deals in this market — for a small team it beats per-seat alternatives outright.

We would look elsewhere for compute-heavy backends, workloads needing long-running processes or GPUs, teams that require an SLA without enterprise pricing, or organizations that want to own their infrastructure outright (a VPS in our /category/vps-providers listings plus a CDN will be cheaper at scale and fully under your control). And if your site is mostly high-volume static delivery, model the $0.13/GB bandwidth rate before committing — dedicated hosting with a plain CDN can cost less.

Key takeaways

• Git-connected build-and-deploy platform founded in 2014 (San Francisco), from the team that coined "Jamstack"; Gatsby and Stackbit acquisitions folded in since 2023.
• Pricing is credit-based as of April 2026: Free ($0, 300 credits), Personal ($9/month, 1,000), Pro ($20/month, unlimited members, 3,000), Enterprise (custom, 99.99% SLA).
• Usage rates are published openly: roughly $0.10 per production deploy, $0.07 per GB-hour compute, $0.13 per GB bandwidth, $0.01 per 10k web requests.
• Deploys are immutable snapshots with one-click rollback to any version; unlimited deploy previews on every plan.
• Automated DDoS protection and HTTPS are included on all plans; advanced security rules are the upsell.
• SLA and 24/7 support are Enterprise-only, and credit rates have already changed once — treat pricing as moving and re-check it.

Sources

• https://www.netlify.com/pricing/
• https://www.netlify.com/pricing/pro
• https://www.netlify.com/changelog/2026-04-14-pricing-updates-april-2026.md
• https://www.netlify.com/about/
• https://www.netlify.com/platform/core/edge/
• https://docs.netlify.com/manage/security/secure-access-to-sites/overview
• https://en.wikipedia.org/wiki/Netlify