Vercel vs Netlify vs Cloudflare Pages: Hosting for Astro/Next.js

Comparing Vercel vs Netlify vs Cloudflare Pages on price, performance, and framework support, the short answer is this. Vercel is the best fit for Next.js thanks to zero-configuration support for the App Router and Server Components. Netlify remains a simple option for basic Astro sites but loses on price and speed as traffic grows. Cloudflare Pages gives the best price-to-performance ratio at any traffic volume, but its Next.js support is partial - some App Router features, ISR, and Middleware work with limitations.

In Exceltic.dev’s web development projects, the hosting decision usually comes up right after the choice between Astro and Next.js. Teams either copy whatever a neighboring project used or default to the free tier without calculating what happens to the budget once traffic grows 5-10x. We consistently see the same pattern: the platform gets picked by default, and six months later a bandwidth bill arrives that nobody warned them about at the start.

Below is an honest breakdown of the three platforms: pricing based on official rate cards as of mid-2026, the limits that actually cause overage billing, and the technical difference in Next.js support between Vercel and Cloudflare Pages that most comparisons skip over.

The pain here is concrete. A team picks hosting at project start, when there’s no traffic yet, and doesn’t revisit the decision until the first large bill arrives. By then, migrating between platforms already costs weeks of work - rewriting edge functions, reconfiguring SSR from scratch, and verifying that redirects and cache headers haven’t broken.

Edge function: server-side code that doesn’t run in a single data center but is replicated across hundreds of the provider’s points of presence, handling the request closer to the user.

In short: Next.js with deep SSR and Server Components - Vercel. A simple Astro site with forms and no dedicated DevOps resource - Netlify. Medium-to-high traffic, static content, or Astro without advanced Next.js features - Cloudflare Pages.

Pricing and Limits Compared: Vercel vs Netlify vs Cloudflare Pages

The three platforms calculate traffic costs in fundamentally different ways, so comparing them on a single “price per month” number is pointless.

Prices reflect the official rate cards for Vercel, Netlify, and Cloudflare Pages as of mid-2026 and are subject to change - check the current pricing page before making a decision.

When to Choose Vercel

Vercel makes sense when the framework is Next.js specifically - not just “any JS framework.”

• The project uses App Router, Server Components, ISR, or Edge Middleware in production - Vercel is the only platform where these work without adapters or workarounds.
• The team is willing to pay for developer experience: preview deployments on every pull request, built-in observability, Neon integration without manual infrastructure setup.
• Traffic is predictable and stays within a few hundred gigabytes - bandwidth overage isn’t a critical budget risk.
• There’s no dedicated DevOps resource on the team - Vercel handles infrastructure configuration entirely on its side.

For teams deciding on framework and hosting at the same time - for example, when migrating from WordPress to Next.js - Vercel settles both questions at once: the same company builds the platform and the framework, so compatibility is guaranteed at the architecture level, not just in the documentation.

When to Choose Netlify

Netlify remains a solid option where built-in services matter more than maximum performance.

• The site is static or has light SSR, without a deep dependency on Next.js-specific features.
• You need a built-in form, authentication (Identity), or A/B testing without connecting third-party services.
• The team is small, and the Pro tier’s unlimited members for $20 a month beats Vercel’s per-seat pricing.
• Traffic is moderate: Netlify is the most expensive of the three per unit of traffic when converted to credits (20 credits per GB), so budget needs to be planned ahead of time at the growth stage.

When to Choose Cloudflare Pages

Cloudflare Pages wins where traffic is the main budget risk.

• Traffic is growing unpredictably or is already large - static assets are served free with no upper limit on any tier.
• The stack is Astro, a purely static site, or SSR without deep Next.js specifics (Remix, SvelteKit, and Nuxt work without the limitations described below).
• Edge function response latency matters - V8 isolates start faster than the competitors’ container runtimes, especially after an idle period.
• Next.js is in the project but without complex Server Components and ISR scenarios - the modern adapter covers most needs here, as detailed in the next section.

Next.js on Cloudflare Pages: What Specifically Doesn’t Work

This is where the difference that most comparison articles skip over begins: Next.js support on Cloudflare has historically been incomplete, and in 2026 that’s still true, though the situation has improved.

Edge runtime: a restricted JavaScript execution environment that doesn’t support the full Node.js API - modules like fs, child_process, and parts of crypto are unavailable in it.

The official @cloudflare/next-on-pages adapter can deploy Next.js on Cloudflare Pages, but it only works through the Edge runtime, which brings three concrete limitations. Incremental Static Regeneration doesn’t build for the edge runtime - Cloudflare explicitly recommends rewriting such pages as regular SSR. Some Server Components APIs that depend on Node.js-specific modules either error out or don’t work at all. Node Middleware, added in Next.js 15.2, isn’t supported yet even in the newer, recommended adapter.

Since 2025, Cloudflare itself recommends the OpenNext adapter instead of next-on-pages, deploying through Workers rather than Pages. OpenNext gets closer to full Node.js compatibility thanks to the nodejs_compat flag, but Middleware on the Node.js runtime and some advanced Server Components scenarios remain uncertain there too.

# Check dependency compatibility with the Workers runtime
npx @opennextjs/cloudflare build

# Run locally in an environment close to Workers production
npx wrangler pages dev .vercel/output/static

In practice, this means: if a Next.js project uses ISR or complex Server Components scenarios, migrating to Cloudflare requires a technical audit of specific dependencies, not a one-time adapter switch in the config.

Astro on Any Host: Why the Choice Is Simpler

Astro is a special case in this comparison, because by default it ships static HTML, and static HTML works equally well on any of the three platforms.

We covered the mechanics of this architecture in the article on INP optimization: Astro ships JavaScript to the browser only for interactive “islands,” while the rest of the markup stays static HTML with no hydration at all. For hosting, this means the job reduces to serving files through a CDN - which is exactly where Cloudflare Pages wins on price with no functional trade-off.

Astro’s SSR mode is also simpler to host than Next.js SSR, because the islands architecture doesn’t require the level of rendering-and-runtime integration that React Server Components are built on. Astro’s adapters for Vercel, Netlify, and Cloudflare cover SSR without the edge-specific limitations described in the previous section.

If a project is migrating from a no-code builder like Webflow, the hosting choice for Astro is usually secondary to the content and structure migration itself - covered in detail in migrating from Webflow to Astro.

Real Case: What Traffic Growth Actually Costs

In a typical marketing site project on a headless stack with 200,000-500,000 visits a month and media-heavy content (a blog with images, video on landing pages), the difference between platforms becomes noticeable within the first quarter.

On Vercel Pro, at 2-3 TB of traffic per month, overage beyond the included 1 TB Fast Data Transfer adds roughly $150-300 a month on top of the base per-seat fee. On Netlify Pro, a 3,000-credit package at 20 credits per GB covers around 150 GB of traffic - for a media-heavy site that’s less than half a month, and you need to buy more credits after that. On Cloudflare Pages, the same volume of static traffic stays free on any tier - only requests to functions (SSR, API) are billed, and the $5-a-month Workers Paid plan covers 10 million such requests.

Exact figures for a specific project depend on media weight and the share of SSR requests per page - this is a range for a typical project, not a guarantee for any given stack.

Who This Choice Matters For

The hosting choice affects budget most for startups and SaaS companies launching a product site from scratch that don’t know in advance what traffic will look like in six months. For a company with 15+ employees where the marketing site already generates leads, the difference between platforms isn’t measured in convenience but in real money as traffic grows.

The worst outcome comes from a “default” choice made without any calculation: if a team picked Vercel because “that’s what everyone does” for a Next.js project with media-heavy content and growing traffic, the overage bill won’t show up right away - it’ll hit 2-3 months after a successful launch, right when traffic is already generating revenue for the business, not when the stack was chosen.

Frequently Asked Questions

Can you host an Astro site on Vercel if the project already uses Next.js for another product?

Yes, Vercel supports Astro on par with Next.js without any loss of functionality. It’s a reasonable choice if the team already works with Vercel and wants to keep both projects in one account and one billing dashboard, even though the platform itself doesn’t give Astro any specific advantage over Cloudflare Pages.

What happens if you exceed the free credit limit on Netlify?

The site doesn’t get shut down automatically, but new deploys and traffic processing stop until you top up credits or move to a paid tier. For a production site with real traffic, that’s critical: it makes sense to move to a Personal or Pro tier right away rather than rely on the free limit as a long-term solution.

Does Cloudflare Pages support Next.js Server Actions?

Partially, and only through the current OpenNext adapter deploying to Workers, not the classic next-on-pages. Server Actions that don’t use Node.js-specific modules usually work correctly, but before a production launch, every scenario should be tested on a real build rather than relying on general compatibility claims.

Is it hard to migrate a site between Vercel and Cloudflare Pages?

Difficulty depends on whether the project uses platform-specific features. A purely static Astro site migrates in hours - only the deployment target changes. A Next.js project with ISR, Server Components, or Edge Middleware will require a technical audit and likely some rewriting of server logic to fit the target platform’s limitations.

Which hosting is cheapest at high traffic volumes?

Cloudflare Pages is almost always cheaper at the growth stage, because static traffic isn’t billed at all, and functions cost noticeably less than Vercel’s bandwidth overage or Netlify’s traffic credits. The difference is especially visible for media-heavy sites - image-heavy blogs, landing pages with video - where traffic, not compute, drives most of the bill.

What to Do Next

• Estimate a realistic traffic range for the next 6-12 months, not just current numbers - the hosting decision should account for growth, not just launch.
• For Next.js with App Router, Server Components, and ISR in production, choose Vercel - these features work with limitations on other platforms.
• For Astro and static sites with growing traffic, Cloudflare Pages almost always gives the best price-to-performance ratio.
• If a project is already migrating to a new stack, lock in the hosting choice as part of the architecture decision before development starts, not after the first traffic bill.

If you’re choosing hosting for an Astro or Next.js site right now and want to avoid a surprise bandwidth bill a few months after launch, describe your traffic volume and framework requirements to the Exceltic.dev team. We’ll go through the architecture and give you an honest read on which platform fits your stack.