In short
Choose Vercel if you use Next.js and want its newest features with minimal setup. Choose Cloudflare if cost at scale matters: its Workers plan starts at $5 a month, static asset requests are free and it has no bandwidth charges. The trade-off is the Workers runtime, which can need some adaptation. Vercel's Hobby tier is non-commercial; Pro is $20 per developer seat.
The core difference
Vercel is a developer platform that's built around frontend frameworks. It makes Next.js, and it aims to make deployment nearly invisible.

Cloudflare runs one of the world's largest edge networks, and it has built a developer platform on top: Workers for compute, static asset hosting, plus storage products such as R2, D1 and KV. Older guides refer to Cloudflare Pages, and Cloudflare has since been directing new projects towards Workers with static assets. Check the current docs when starting a new project.

Pricing
From the Vercel and Cloudflare Workers pricing pages, checked on 4 November 2026.
| Vercel Pro | Cloudflare Workers Paid | |
|---|---|---|
| Base price | $20/month, per developer seat | $5/month minimum, per account |
| Bandwidth | 1 TB/month, then metered | No charge for egress or bandwidth |
| Static assets | Count towards transfer | Free and unlimited requests |
| Compute | Active CPU, memory and invocations metered | 10M requests and 30M CPU ms included; then $0.30 per million requests, $0.02 per million CPU ms |
| Free tier | Hobby: non-commercial, 100 GB | 100,000 requests a day, 10 ms CPU each |
A worked example
Cloudflare's own docs give an example: a Worker receiving 15 million requests a month at 7 ms of CPU per request costs about $8.00, made up of the $5 base, $1.50 for extra requests and $1.50 for extra CPU time.
Now suppose a site that's mostly static serves 5 TB a month. On Cloudflare, the bandwidth itself costs nothing, because static assets are free. On Vercel Pro, 4 TB is above the included allowance, so you would pay Vercel's metered rate for it. Check the page for the current rate in your region. For a media-heavy or high-traffic site, this one line can dominate your bill.
The opposite can be true for small teams with low traffic, where the two are close and developer productivity is worth more than a few dollars.
Runtime differences
This is the catch with Cloudflare. Workers use a V8 isolate-based runtime and not a traditional Node.js server. Compatibility has improved a lot, but libraries that depend on Node internals or native binaries may need changes or a compatibility flag. Paid plan CPU limits default to 30 seconds per invocation, with up to 5 minutes available, and that matters for heavier jobs.
Cold starts are generally very small, thanks to this model, which is one reason it's attractive for APIs and edge logic. And since time spent waiting on a network doesn't count as CPU time, it can be very cheap for workloads that mostly wait on other services, including many AI calls.
Vercel's functions run on a more conventional Node.js environment, so most libraries simply work. See what serverless is for the concepts.
Next.js
If you depend on the latest Next.js features, then Vercel is the path of least resistance, since it builds the framework. Cloudflare supports Next.js through the OpenNext adapter, which covers a lot, but you should verify any feature you rely on, particularly around caching, image optimisation and streaming.
If you use Astro, SvelteKit, Remix or a static site, both are good options, and Cloudflare's pricing becomes hard to ignore. Consider too whether you need a framework at all: your site may not need one.
The wider platform
Cloudflare offers a broad set of low-level building blocks, including object storage with zero egress fees, a SQL database, key-value storage, queues and security tools such as its WAF and DDoS protection. It can serve as your whole stack, but your code becomes tied to its APIs as a result.
Vercel focuses on the frontend workflow, including preview deployments, analytics, and AI tooling such as its SDK and gateway. You'll typically pair it with a separate database from a provider such as Neon or Supabase.
Developer experience
Vercel's strength is how little you need to think about. Connect a repository and most projects work the first time, with polished previews and logs. Team members who aren't infrastructure specialists can usually manage it.
Cloudflare's dashboard and tooling have improved, but the platform is broader, and you may need to understand more concepts. If your team is small and shipping quickly matters most, that difference can be worth more than the hosting bill, at least in the early stages.
You can combine them
These aren't mutually exclusive. Cloudflare is commonly placed in front of other hosts for DNS and protection, and some teams use R2 for heavy media while running their app on Vercel. Check for caching conflicts before putting one CDN in front of another, and read how a CDN works.
How to choose
- Next.js with its newest features, small team: Vercel.
- High traffic or heavy media on a budget: Cloudflare.
- Mostly static site: Cloudflare, as static requests are free.
- APIs and edge logic with low CPU use: Cloudflare.
- Libraries that need full Node.js or native modules: Vercel, or a container host such as Railway.
- Long-running background jobs: neither may be ideal, so consider a server or a platform designed for them.
Try deploying your real project to both before you decide, since runtime compatibility is hard to judge in advance.
If you want help working out what your hosting should cost, book a call.
Common questions
Is Cloudflare cheaper than Vercel?
Often, especially at high traffic. Cloudflare doesn't charge for bandwidth, and static asset requests are free, on a $5 monthly minimum. Vercel Pro is $20 per developer seat, with metered usage. For a small project, the difference may be minor.
Can I host Next.js on Cloudflare?
Yes, commonly through the OpenNext adapter, but not every feature behaves the same as it does on Vercel. Test caching, image optimisation and anything newer before committing, especially if your app relies on the framework's latest features.
What are the limits of Cloudflare Workers?
It isn't a full Node.js server, so some packages may need changes. Paid plans allow up to 5 minutes of CPU time per invocation, with a 30-second default. Free plans allow 10 ms of CPU and 100,000 requests a day.
Should I use Cloudflare in front of Vercel?
Often it isn't needed, as Vercel has its own CDN, and stacking two can complicate caching and analytics. Some teams do it for DNS or extra security features. Check Vercel's current guidance before putting a proxy in front of it.