Vercel vs Netlify vs Cloudflare Pages for Founders (2026)
Every build on this site eventually runs into the same fork in the road: the code works, and now something has to serve it. Our own answer is boring. This site runs on WordPress hosting, the side projects run on a Windows box in a closet, and GitHub holds the code. But hosting a new SaaS is a different animal, and it deserves better than whichever platform had the best demo video that week.
Vercel, Netlify, and Cloudflare Pages all take a git push and hand back a live URL with a preview deployment for every pull request. On a feature grid they look like the same product with three logos. The pricing mechanics tell a different story: Vercel meters almost everything, Netlify rebuilt its plans around credits, and Cloudflare stayed flat and cheap in a way that looks like a typo. Pick wrong and you either overpay from day one or meet a surprisingly large invoice the month a newsletter mention triples your traffic.
Here’s how the three actually compare in 2026, with numbers pulled from each vendor’s own pricing pages this week.
The 30-Second Verdict
If you only read one section, read this:
- Building on Next.js and want the shortest distance from code to production: Vercel. Pro runs $20 per developer seat and includes a terabyte of transfer.
- Shipping a marketing site plus a small app, and you value deploy workflow over shaving dollars: Netlify. Personal is $9 a month, Pro is $20 with unlimited team members.
- Hosting anything with real traffic while keeping the bill near zero: Cloudflare. Static requests are free and unlimited, and the paid tier is a flat $5 for the whole account.
Everything below is the reasoning, plus the pricing table and the fine print each landing page quietly skips.
What Each Platform Actually Is
Vercel is the company behind Next.js, and it shows. Push code, get a URL, and every framework-specific trick (image optimization, incremental static regeneration, edge middleware) works the way the framework intends, because the host and the framework come from the same people. Preview deployments and the built-in toolbar make it a pleasant place to iterate. That polish is also the brand, and it’s why the pricing has grown more line items than anyone wants to read.
Netlify invented much of the workflow this category now takes for granted: deploy previews, atomic deploys, instant rollbacks. In 2025 and 2026 it rebuilt pricing around credits, which changed the math for new accounts. The workflow itself is still excellent, and framework support is the broadest of the three. You bring an Astro, Vue, Svelte, or Next project and Netlify usually figures out the build without an argument.
Cloudflare Pages is the odd one out in an interesting way. Static requests are free and unlimited, there is no bandwidth bill at all, and the paid tier is a flat $5 a month for the entire account. The catch is direction. Cloudflare has spent the past two years converging Pages and Workers, and it now points new static deployments at Workers with static assets. Pages still works and its docs were updated this month, but the company publishes a migration guide for leaving it, which tells you where the energy is going.
2026 Pricing, Side by Side
All figures below come from the vendors’ own pages, checked September 24, 2026. These change more often than firmware, so treat this as a snapshot.
| Vercel | Netlify | Cloudflare Pages | |
|---|---|---|---|
| Free tier | 100 GB transfer, 1M edge requests, basic builds, unlimited deployments. Non-commercial per the fair-use terms. | 300 credits a month: 15 credits per production deploy, 20 per GB of bandwidth, so roughly 15 GB if bandwidth is all you buy. | Unlimited static requests and bandwidth; 100K dynamic requests per day; 500 builds per month. |
| First paid tier | Pro: $20/mo per developer seat | Personal: $9/mo, 1,000 credits. Pro: $20/mo, 3,000 credits, unlimited members | Workers Paid: $5/mo flat for the account |
| Transfer on paid | 1 TB included, then about $0.15/GB | Credits only; bandwidth works out to $0.13/GB | No bandwidth charge exists |
| Serverless | Fluid compute, 4 active CPU hours free, metered after | Functions billed in credits, 10 per GB-hour | 10M requests plus 30M CPU-ms included on the $5 plan |
| Framework sweet spot | Next.js, unapologetically | Everything, with the least friction | Static and edge; Next.js through an adapter |
| The catch | Usage metering on many axes | Credit model confuses old plans vs new | 10ms CPU cap on free; Pages is winding down |
Three details worth spelling out. Vercel’s Pro plan is per developer seat, so a three-person team bills $60 a month before any usage. Netlify’s Pro flipped that in April 2026 with unlimited members and 3,000 included credits, though each production deploy costs 15 credits, so 3,000 credits is 200 deploys, or 150 GB of bandwidth, or any mix of the two. Cloudflare’s paid tier is per account, not per seat, and its own docs walk through a site serving 15 million requests a month where 80% hit static assets: total bill, $5.
Vercel: Paying for the Shortest Path to Production
The case for Vercel is the case for not thinking about infrastructure. A Next.js app just works, preview URLs show up on every pull request, and the observability dashboards are good enough that you check them even when nothing is wrong. When the app starts making money, the metering maps to real usage, and the included allowances (1 TB of transfer, 10M edge requests on Pro) are big enough that most early-stage projects never see an overage line.
The honest downsides. Hobby, the free plan, is aimed at personal and non-commercial projects under Vercel’s fair-use terms, and developer communities carry a steady stream of Hobby suspension stories. Vercel is within its rights whenever it enforces those terms; you should just know the terms before you build a business on the free tier. The free plan also includes one hour of runtime logs, which is like being handed a flashlight with a one-hour battery. And pricing is a components game: transfer, edge requests, function invocations, image optimization, all metered separately, so the bill you predict and the bill you receive can drift apart on a traffic spike.
My honest framing after years of watching this from the outside: Vercel is the best product in this comparison, and the one I’d least want to explain to a founder who just wants to know what things cost. Start on Hobby, move to Pro the week the project has revenue, and set a spend alert on day one.
Netlify: The Workflow Pick With a New Price Tag
Netlify’s pitch hasn’t changed much and never needed to: deploy previews for every branch, a broad build system that handles whatever framework you bring, and enough ancillary features that a small site can skip a backend, including forms with unlimited submissions on credit plans, blob storage, even a managed database. Pro with unlimited members at $20 a month is a genuinely good team deal, since Netlify charges one price for the account where Vercel charges per seat for the same privilege.
The complication is the credit system, and I’ll be blunt about why it matters: a lot of what you’ll read about Netlify pricing describes the legacy plans, which still exist for older accounts. New signups get credits. The free plan’s 300 credits a month make it a builder’s tier, not a hosting tier: twenty production deploys, or about fifteen gigabytes of bandwidth, and then it waits for next month. The old 100 GB free-bandwidth number that powered a thousand blog posts belongs to the legacy plans.
The trade to weigh is simple. Netlify’s credit rates work out to $0.13 per GB of bandwidth, roughly the same as Vercel’s overage rate and dramatically more than Cloudflare’s zero. What you’re buying instead is workflow and breadth. If your project is a content-heavy site with a few dynamic endpoints, and a team shares one account, the unlimited members make Pro cheaper than Vercel for any team larger than one. If raw bandwidth is your cost driver, this isn’t the right pick.
Cloudflare: The Cheapest Serious Bill in the Room
Here is the entire pricing story for Cloudflare: static asset requests are free and unlimited, and the paid tier is $5 a month for the whole account, covering 10 million dynamic requests and 30 million CPU milliseconds. There are no egress charges because the business model isn’t metering your traffic. A side project with modest dynamic needs can run for years on the free plan, and Cloudflare’s own worked example (15 million monthly requests, 80% static) stays at $5 because static requests never enter the meter.
The tradeoffs are real, and the first one is philosophical. Pages is in its later chapters as a product name. Cloudflare’s docs are blunt that new features land in Workers, and there’s an official migration guide from Pages to Workers with static assets. Existing Pages sites keep working; building fresh on Pages in 2026 means choosing the platform the vendor is gently walking away from.
The second trade is the runtime. Workers run on V8 isolates rather than Node, so most things work and a few things don’t, or need the adapter route. Next.js support exists through OpenNext, but it’s an adapter, not a native home. The free plan’s 10ms CPU cap per invocation is fine for serving pages and hostile to heavy processing. One small bureaucratic quirk worth knowing: new accounts can’t create unlimited Pages projects in their first 48 hours, and the 100-project cap per account doesn’t get raised casually.
What the Pricing Pages Don’t Mention
Every host meters something different. Vercel meters transfer, then requests, then CPU. Netlify folds everything into credits. Cloudflare meters dynamic requests and CPU while ignoring bandwidth. Three different mental models, so “which is cheapest” has no answer until you know your traffic shape.
Free tiers are development tiers. Vercel’s Hobby is non-commercial. Netlify’s 300 credits are a build sandbox. Cloudflare’s free tier is the only one I’d confidently serve real customer traffic from, and even there the CPU cap shapes what you can run.
Reviews in this category age badly. Half the comparisons you’ll find describe Netlify’s legacy plans and treat Cloudflare Pages as if the convergence isn’t happening. Check dates. Anything written before mid-2025 is describing a different Netlify and a different Cloudflare.
Hosting is half the decision. Where your database lives shapes your architecture more than where your HTML is served from. We compared the backend side of this same decision (Supabase, Firebase, and Neon) in a separate piece.
How to Choose in One Afternoon
Every one of these runs a real project on its free tier, so test with your actual app instead of trusting anyone’s benchmark, including mine. Two hours per host, timeboxed hard.
- Deploy your real repo, not a starter template, and note where each platform argues with you.
- Check your framework’s fit. Next.js is first-class on Vercel and adapter-territory on Cloudflare; everything else is comfortable on all three.
- Price your worst-month traffic on each platform’s calculator, not your average month.
Then pick by deliverable. A Next.js SaaS with paying users points at Vercel Pro. A content-heavy site plus a small app, shared by a team, points at Netlify Pro’s unlimited seats. A bootstrapped project with real traffic and no revenue yet points at Cloudflare without much hesitation. And if you’re still building the app itself, our Lovable vs Bolt vs v0 comparison covers the tools that get you to a deployable codebase in the first place.
How This Comparison Was Put Together
Pricing came straight from the vendors: Vercel’s pricing page, Netlify’s machine-readable pricing file, plus the Workers and Pages documentation Cloudflare publishes, all pulled September 24, 2026. Netlify’s bandwidth math is my own arithmetic from their published credit rates, and I’ve labeled it as such. The qualitative points come from the vendors’ own docs and developer community threads, cross-checked against several independent comparisons published this year.
Full disclosure about our own setup, since this site runs on WordPress with the code in GitHub and cron jobs on a Windows box: nobody here has run three paid hosting accounts side by side. What I can offer from running a one-person operation (the about page has the honest version) is what actually drives these decisions at small scale: predictable bills beat peak performance, and a surprise invoice hurts more than a slower cold start. Nothing here is sponsored, and no vendor saw it early.
Key Takeaways
- Vercel Pro is $20 per developer seat with 1 TB of transfer included; the pick for Next.js products with revenue.
- Netlify prices new accounts in credits (Free 300, Personal $9, Pro $20 with unlimited members); legacy plans still exist, so older articles mislead.
- Cloudflare serves static assets free and unlimited with no bandwidth billing; the $5 Workers tier covers 10 million dynamic requests.
- The free tiers differ in kind: Vercel’s is non-commercial, Netlify’s is a build sandbox, Cloudflare’s can serve real traffic.
- Test with your real repo on all three free tiers; the free-to-paid jump is where the mental models diverge.
Ready to deploy? Start free where it fits, then pay for the tier your traffic actually demands. And once the hosting is sorted, the next question is usually how to grow the thing you shipped; the AI Blueprint course covers the founder-ops side of running a one-person business (we earn a commission if you buy through that link).
