Every comparison of these three reads the same way: a feature table, a "choose X if" section, and a pricing breakdown lifted from each platform's own marketing page. Most of them are written by people who've deployed to one of the three and read about the other two. We haven't. We run production work on Vercel, Netlify, and Cloudflare Pages, and we pick between them per project, not by habit. This is that decision, written down properly.
One thing this article isn't: a comparison of no-code AI app builders like Lovable or bolt.new. Those tools generate an app and deploy it somewhere; this is about choosing where a real, hand-built app actually runs. Different question, different article.
The quick verdict
If you want the short version before the detail, here it is. Everything below explains the reasoning.
| Platform | Best for | Watch out for |
|---|---|---|
| Vercel | Next.js-heavy builds, teams who value preview deploys and DX above cost | Function and bandwidth costs can climb fast at scale |
| Netlify | Framework-agnostic teams who want forms, functions, and a CMS without bolting on extra services | Less first-party depth on any single framework compared to Vercel and Next.js |
| Cloudflare Pages | Cost-sensitive or high-traffic projects, teams already on Cloudflare for DNS or WAF | SSR and image handling on the edge runtime need more care than on Vercel |
Who this is for
This is written for developers and agencies deploying a real application, not choosing a website builder. If you're comparing Next.js, Astro, SvelteKit, or similar frameworks against these three hosts, keep reading. If you built something in a prompt-to-app tool and just need it live somewhere, the decision looks different and we'll cover that separately.
The three contenders
Vercel is the company behind Next.js, and it shows. Git-based deploys, instant preview URLs on every pull request, and the tightest possible integration with the framework most React teams reach for by default.
Netlify got to git-based deploys and preview URLs first, and it's stayed framework-agnostic the whole way through. Forms, serverless functions, and a headless CMS option all live under one roof, which matters if you don't want to wire up four separate services for a mid-size site.
Cloudflare Pages runs on Cloudflare's own network, which is one of the largest edge networks in the world. It started as the newest and least polished of the three; that gap has closed a lot, and the tradeoff now is more about runtime maturity than raw features.
Pricing: what the free tier actually gets you
Every one of these platforms has a generous free tier and a Pro tier that starts adding up once you have real traffic or a team on it. The honest answer is that none of them are "cheap" once you're running serious function usage or bandwidth, and the number that actually decides your bill depends entirely on your traffic shape, not the sticker price.
| Free tier | Vercel | Netlify | Cloudflare Pages |
|---|---|---|---|
| Bandwidth | 100 GB/month | No fixed cap, drawn from a shared 300 credits/month pool (20 credits per GB) | Unlimited |
| Build minutes | No fixed cap, limited instead to 100 deployments/day, 100 builds/hour, 45 min max per build | No separate build-minute billing, each production deploy costs 15 credits from the shared pool | Not minutes-based, capped at 500 builds/month, 1 concurrent build, 20 min timeout |
| Serverless / edge function invocations | 1,000,000/month included | No fixed count, functions draw from Compute credits (10 credits per GB-hour) in the shared pool | 100,000 requests/day (shares the Workers free plan quota) |
| Team seats included | 1 (solo, on the Hobby plan) | 1 free member, plus unlimited free Git Contributor roles on public repos | Unlimited |
Netlify's cells look different in shape, not just in number, on purpose. Its September 2025 pricing redesign replaced separate bandwidth, build-minute, and function-invocation caps with a single shared credit pool, so there's no standalone "GB" or "minutes" figure to quote the way there is for the other two. That's how their current plan actually works, not a gap in this table.
If cost at scale is the deciding factor for your project, Cloudflare Pages is usually where that conversation ends up, largely because bandwidth is bundled into Cloudflare's own network rather than metered the way it is elsewhere. That's a general pattern, not a promise about your specific bill.
Framework support, and deploying Astro specifically
All three platforms support the popular frameworks: Next.js, Astro, SvelteKit, Remix, Nuxt. Vercel's Next.js support is first-party and unsurprisingly the deepest of the three. For everything else, the gap is smaller than the marketing suggests.
We use Astro on a lot of our own builds, including this site, so it's worth calling out specifically since most comparison articles skip it entirely. Astro has an official adapter for all three platforms. Vercel and Netlify's adapters are the most mature and give you server-side rendering, image optimisation, and hybrid rendering with no real friction. Cloudflare Pages' Astro adapter works, but SSR routes run on Cloudflare's edge runtime rather than Node.js, which means a handful of Node-specific APIs and some image optimisation approaches need a workaround or a different package. For a mostly-static Astro site it's a non-issue. For a heavily server-rendered one, budget extra setup time on Cloudflare.
Performance and the edge network
All three run on a global edge network and will feel fast for the vast majority of sites. Cloudflare's network is Cloudflare's actual core product, built over more than a decade for a different purpose entirely, so its edge footprint is large by any measure. Vercel's compute model has moved toward reusing warm instances across requests rather than a cold start per request, which closes a gap that used to favour Cloudflare more clearly. In practice, for a typical marketing site or app, the difference between the three is not what determines the user experience. Image optimisation, bundle size, and how much you're rendering on each request matter far more than which network you picked.
What each one is actually best for
Vercel is best for teams building on Next.js who want the tightest possible integration, fast preview deploys on every branch, and are willing to pay for that convenience. If your team lives and dies by pull request previews and Next.js-specific features like ISR, this is the path of least resistance.
Netlify is best for teams who don't want to stitch together a form handler, a function runtime, and a CMS from three different vendors. If you're framework-agnostic and want one dashboard for deploys, forms, and functions, Netlify still does that better than most.
Cloudflare Pages is best for projects where cost at scale or raw edge performance is the priority, or where you're already running DNS, WAF, or R2 storage through Cloudflare and want one less vendor relationship to manage.
Broken down by the type of app rather than the type of team:
| App type | Vercel | Netlify | Cloudflare Pages |
|---|---|---|---|
| Static marketing site (Astro, plain HTML) | Good fit | Good fit | Good fit, usually cheapest at scale |
| Next.js app using ISR or server actions | Native fit | Works, some Next.js-specific features lag behind Vercel | Works, but expect more manual configuration |
| Server-rendered Astro app | Good fit | Good fit | Works, budget time for edge runtime quirks |
| Site with forms, no separate backend | Needs a form service bolted on | Native fit, built-in form handling | Needs a form service bolted on |
| High-traffic content site, cost-sensitive | Works, watch bandwidth costs | Works, watch bandwidth costs | Native fit |
How we actually decide
We don't have a house default. Every project starts with the same short list of questions, and the platform falls out of the answers rather than the other way round.
- Is the client already on Cloudflare for DNS, WAF, or storage? If so, Cloudflare Pages usually wins on simplicity alone, one less vendor and one less bill.
- Is the build Next.js-heavy and dependent on features like ISR? That points to Vercel, since the first-party integration removes a category of edge-case bugs.
- Is traffic cost-sensitive or genuinely high-volume? That's usually a Cloudflare Pages conversation.
- Does the project need forms, functions, and light content management without extra services bolted on? That's where Netlify still earns its place.
None of this is a permanent allegiance to any one platform. We've moved projects between them when requirements changed, and we'd rather tell a client the honest tradeoff than sell them on whichever one we happen to prefer that month.
The honest part
We're not going to tell you one of these is objectively "best," because it isn't true. Anyone who tells you that is usually selling something, their own hosting product, an affiliate link, or a services pitch dressed up as a comparison. All three platforms are good enough to run a serious production app. The decision is about fit to your specific project, team, and budget, not about which logo is superior.
We also won't pretend pricing is simple. Free tiers are genuinely generous on all three, and the moment you outgrow them, the bill depends on your specific traffic pattern more than the platform's list price. Get a real estimate from your own usage numbers before committing, not from a blog post's example figures.
FAQ
Is Cloudflare Pages cheaper than Vercel?
Usually, once you're past the free tier, mainly because Cloudflare bundles bandwidth into its own network rather than metering it separately. The gap narrows or disappears for smaller, mostly-static sites where both platforms' free tiers cover you comfortably.
Can you deploy Astro to Cloudflare Pages?
Yes, using Astro's official Cloudflare adapter. Static and hybrid Astro sites deploy with no real friction. Heavily server-rendered Astro sites need a bit more care, since SSR routes run on Cloudflare's edge runtime rather than Node.js.
What are the best Vercel alternatives?
Netlify and Cloudflare Pages are the two most direct alternatives for frontend and full-stack app deploys. If you need a real backend alongside the frontend, Render, Railway, and Fly.io are worth a look too, though that's a different comparison to this one.
Do we have to pick one platform for every project?
No, and we don't. We deploy different client projects to different platforms depending on what each one actually needs. There's no rule that says an agency, or you, has to standardise on one.
If you'd rather have someone who's actually deployed to all three make the call for your project, that's exactly what our Web Development service covers.
Jinnat Ul Hasan
Founder & CEO, Whizz People
