The three that matter
Jamstack hosting has consolidated into three serious platforms: Netlify, Vercel and Cloudflare Pages (which is increasingly folded into Cloudflare Workers). We have shipped production sites on all three, and the "which one?" question lands in our inbox most weeks. Here is the honest read on where each one wins in 2026.
Build speed
All three build quickly on a small project. The differences show up at scale.
Vercel builds fast and caches aggressively. Its monorepo and Turborepo support is the best of the three, and the incremental build pipeline for Next.js is tight. Netlify is close behind, with build plugins, generous cache controls and solid monorepo support. Vercel has pulled slightly ahead on pure Next.js timing, but the Netlify build experience is still strong. Cloudflare Pages builds are catching up. They have historically been the slowest, particularly on large Next.js apps, though Cloudflare is closing the gap via the Workers build pipeline, which is where the platform is heading.
For a content site that rebuilds in minutes, it barely matters. For an eCommerce build that rebuilds in half an hour, Vercel or Netlify will save your afternoon.
Runtime differences
This is where the platforms diverge most.
Vercel: Serverless plus Edge
Vercel offers AWS Lambda-based Serverless Functions for Node workloads and Edge Functions for globally distributed light logic. The Edge runtime is Web Standard APIs only. The integration with Next.js App Router is tighter than anything else on the market.
Netlify: Functions plus Edge Functions
Netlify Functions run on AWS Lambda. Netlify Edge Functions run on Deno Deploy. Framework-agnostic, good developer experience. Less magical than Vercel with Next.js, which for some teams is a feature rather than a bug.
Cloudflare Pages and Workers
Cloudflare is its own thing. Workers are not serverless functions in the traditional sense. They run on a V8 isolate model that starts in milliseconds and runs globally by default. No cold starts to speak of. You get KV, R2, D1, Durable Objects, Queues and Hyperdrive as part of the platform. Commit to the Workers ecosystem and the capability you can access in one coherent stack is large.
The trade-off is Cloudflare's runtime is Web Standard APIs with Cloudflare-specific bindings, not Node. Plenty of libraries work. Plenty do not. Check before you commit.
Pricing at scale
Every platform's free tier looks great. The question is what happens when traffic grows.
Vercel's bandwidth and function-invocation tiers are the ones we see clients get caught on. Overage pricing is real, and a viral day can produce a surprising bill in AUD. The Enterprise plan is strong but priced accordingly. Netlify pricing is more predictable for traditional site traffic, with build minute overages and bandwidth as the usual culprits. Large-site pricing is where negotiation happens, same as everywhere else.
Cloudflare is the cheapest at scale by a meaningful margin. Bandwidth is effectively free on cached content, and Workers pricing scales gently. For high-traffic sites, Cloudflare is the cost winner.
For most small-to-midsize marketing sites, all three are affordable. For a content site doing real traffic, or a project that streams a lot of bandwidth, Cloudflare's pricing is worth a serious look.
Framework alignment
This is the hidden decision factor.
Vercel is Next.js-native. Every new Next.js feature lands on Vercel first, and the platform is co-designed with the framework. If you are on Next.js App Router, you will have the easiest life on Vercel. Netlify is framework-agnostic and has worked hard to keep it that way. Astro, Gatsby, Eleventy, SvelteKit, Nuxt, Hugo all deploy cleanly. If your team uses several frameworks, Netlify is the least painful shared platform. Cloudflare is Workers-native, with good adapters for the major frameworks and genuinely strong support for Astro, Remix, SvelteKit and Hono. Next.js on Cloudflare is viable but not as frictionless as on Vercel. The story keeps improving.
If you are deep into Next.js, Vercel is the path of least resistance. Anywhere else, the decision opens up.
AU latency notes
We build a lot of Australian sites, so POPs matter.
All three have a Sydney presence. Cloudflare additionally runs a Melbourne POP and expanded coverage across APAC. For static asset delivery, all three are indistinguishable from a Sydney or Melbourne browser. Sub-50ms for cached content.
For function execution, Cloudflare runs Workers in-country on its Australian POPs. Vercel and Netlify Edge Functions likewise execute close. Vercel Serverless Functions can be configured to run in Sydney, but the default region matters. We have seen Aussie sites deploy with us-east-1 as the default and then wonder why their API routes feel slow.
Always check the default region for serverless functions. It is the single most common performance bug we find on projects handed to us from other developers.
When each one wins
Vercel wins when the project is Next.js, the team wants the most integrated framework experience available, and traffic is predictable enough that the pricing is manageable.
Netlify wins when the project uses several frameworks or one that is not Next.js, the team wants a framework-agnostic platform with good DX, and the build-plugin ecosystem is useful.
Cloudflare wins when cost at scale matters, when the project can embrace the Workers ecosystem, when you want a single coherent developer platform including storage and compute, or when you need true global edge execution with no cold starts.
Preview deploys and developer workflow
Modern Jamstack hosting has converged on per-branch preview URLs, atomic deploys and instant rollbacks. All three platforms do this well. The polish differs.
Vercel preview URLs, visual comments and team review workflow are the slickest of the three. Non-developers can leave feedback directly on a preview deployment without a meeting. Netlify deploy previews are solid, and the Deploy Pipeline and plugin ecosystem give you a lot of control over build steps. Branch deploys and split testing are first-class. Cloudflare Pages previews work, but the collaborative polish lags Vercel and Netlify. The platform is more developer-focused. The stakeholder-review experience is not the headline.
If your client workflow leans on non-technical stakeholders reviewing previews, that is a real factor worth weighing.
What we default to
For a new Next.js project, we still start with Vercel. For an Astro or multi-framework project, Netlify. For anything cost-sensitive or heavily read-dominated, Cloudflare. None of these are permanent answers. They are where we start the conversation.
If you are picking a host for a new build, or wondering whether your current platform is still the right fit, we would be happy to sanity-check it against your traffic and framework.
