Netlify Review

Netlify still fits the job it invented, a Git-connected frontend on a global CDN, and in 2026 the invoice depends on which plan generation the team is stuck on. A new signup cannot buy the old member price, so credit tiers are the only offer a fresh account will see.

An older team can keep Legacy billing, and the switch to credits cannot be reversed, so model both invoices before you move.

This review is for developers, engineering leads, and indie hackers who need the real monthly cost, not a feature tour. It prices the credit tiers, the meters that spend them, and the Legacy allowances that still surprise a team that never migrated.

The fuller cross-site sheet is the Netlify pricing page on Dupple.

Toolradar data: the September 2026 hosting and deployment ranking evaluated 297 tools. Netlify has its own page in that catalog and is not one of the 10 names at the top of the list.

How we compared: Netlify, Vercel, Cloudflare Pages, Render, Firebase Hosting, and Railway, with USD figures read on each vendor's pricing page or billing docs on September 24, 2026. No hands-on deploy was run for this piece and nobody paid to be included.

If you open Netlify through a link here, Devshot may earn a commission, and that does not change the verdict.

Netlify is a composable web platform: you connect a repo, it builds, and the CDN serves it with HTTPS on a custom domain. The same account can run serverless and edge functions, scheduled and background functions, Database, and Blob storage.

That covers light backend work, and it is the wrong host if you need to size a long-running process.

Forms ship with the platform, so a contact form does not add another vendor. Agent Runners, announced on October 1, 2025, meter model spend separately from the CPU that hosts the run, so an agent can draw credits while the page is quiet. Firewall rules and basic rate limiting are on every credit plan, including Free.

New accounts from September 4, 2025 onward are credit plans only: Free, Personal, Pro, or a custom Enterprise contract. Older Free, Starter, and Pro teams can keep Legacy plans, which is why an older write-up can still match an old dashboard.

Enterprise lists a 99.99% SLA, SSO and SCIM, log drains, and unlimited credits for teams that need a contract.

The daily loop is a Git push, with an API and an AI deploy path beside it, and the charge lands on a successful production publish rather than a pull request.

That publish spends 15 credits, while Deploy Previews, branch deploys, failed builds, and rollbacks spend zero, so review work does not drain the month.

Credits expire in date order, monthly first, then rollover, then packs that do not expire, so an older pack is the last buffer. Auto recharge stays off until a Team Owner enables it for the whole team, not for one site, so a single project cannot refill the shared balance.

When the balance hits zero, every project pauses and visitors get a Site not available page, a team-wide outage rather than a warning on one site. One concurrent build on Free means the whole team builds one at a time, so a second site waits on a launch day.

Edge functions draw web requests rather than compute, on the same meter as pages and assets, while compute covers serverless work, preview servers, Agent Runners, and database compute. A background job hits that second meter, which is the one that surprises a quiet frontend.

Read the plan generation before the sticker, because a credit subscription and a Legacy seat fee are different products under the same name.

Credit prices below were checked on Netlify's pricing page and the credit-plan docs on September 24, 2026.

Legacy rates are from the Legacy plan docs the same day, and Enterprise is a quote on Netlify, Vercel, Render, and Railway.

Free includes 300 credits and will not sell you more, so the ceiling never turns into a bill. Spend that allotment only on production deploys and you get 20 publishes, because each one is 15 credits. Spend it only on bandwidth and you get 15 GB, and a real month mixes meters, so the wall arrives sooner than either extreme.

Personal adds a 500-credit pack with auto recharge, off unless an owner enables it for the whole team. Pro's pack is 1,500 credits, and Netlify's own calculator prices a production deploy at $0.10, bandwidth at $0.13 per GB, and compute at $0.07 per GB-hour at that pack rate.

Those pack dollars sit on top of the subscription, so a tier-only budget misses a busy month.

Rollover starts at the $33 tier, 5,000 credits, and unused monthly credits last one extra cycle. The 10,000, 15,000, and 20,000 tiers roll over too, while the 3,000-credit tier does not, so the cheapest Pro forfeits what you do not spend.

A downgrade deletes leftover monthly credits and rollover credits, while packs stay, so spend the monthly balance before you step down.

An extra concurrent build is $40/mo, and each Live Preview Server past the included one is $15/mo, both on top of the tier. Twenty Legacy Pro members are twenty seat fees, at $19 per member including active Git contributors, before bandwidth, while the same twenty on credit Pro do not multiply the subscription.

Legacy bandwidth is 100 GB on Free and Starter. Free stops serving at that ceiling instead of billing, and Starter pays $55 per extra 100 GB, while Legacy Pro includes 1 TB before the same package.

Build minutes over the Legacy Pro pool are $7 per 500, and edge functions past 2 million are $2 per million. Forms past 100 per site are a paid Legacy package, while credit plans leave forms unmetered.

Vercel Pro is per user at the same monthly rate as credit Pro, with a usage credit equal to the seat fee, so each added developer still costs a seat. Hobby is free, a solo plan rather than a team plan.

Cloudflare Pages does not bill static asset requests, and Pages Functions draw Workers. The paid plan has a $5 minimum, 10 million requests included, then $0.30 per million, with no egress fee, which favors a site made of files.

Render static sites are free, and a Starter instance is 512 MB and 0.5 CPU at the flat price in the table. The Pro workspace is $25/mo with unlimited seats and 25 GB of bandwidth, then the per-GB rate in the table.

Firebase Spark needs no card, with 10 GB stored and 360 MB of transfer a day, then Blaze storage at $0.026 per GB. Cloud Functions are not on Spark, so any function forces the paid Google plan.

Railway's Hobby fee equals its usage credit, CPU and memory stop when the service stops, and egress is $0.05 per GB.

Netlify fits a frontend team that wants previews, a CDN, and forms without a server, on credit Pro so headcount does not multiply the subscription. A solo project inside 1,000 credits belongs on Personal. A hobby repo that can go offline belongs on Free, but a customer URL does not.

Skip it for a long-running process, a websocket server, or a database you size yourself. Those jobs want a dyno or a VM, which is a Heroku or Railway call, or a VM on the VPS hosting list and the DigitalOcean review.

A Next.js app that wants the framework's own host should read the Vercel review first.

Stay off Legacy Pro if you are about to add contractors, because they count as members and each one adds a seat fee. Stay off credit Free when a spike would be worse than a bill, because the plan stops the site instead of charging you.

Password protection and shared env vars wait for Pro, so a locked client preview is not a Free feature.

If the product is Postgres and the frontend is only the shell, start with Postgres hosting and the Supabase review.

Pipelines past deploy previews belong on the CI/CD tools list, and the function-versus-container choice is serverless platforms.

Credit tiers moved again in July 2026, so subscribe free if you want the next change in the inbox.