Skip to main content

Vercel vs Cloudflare

Vercel vs Cloudflare comes down to framework integration and infrastructure economics. Vercel offers first-party Next.js support, while Cloudflare Workers offers lower usage rates and no bandwidth charges.

Author
Sean WhitemanFounder, Easel.sh
Facts checked
Disclosure
Easel competes with both

The short answer

Choose Vercel if

  • You want to run Next.js without an adapter
  • You need more memory for server-side code
  • You need a wider selection of language runtimes
  • You run many builds at once

Choose Cloudflare if

  • You want lower bandwidth and compute costs
  • You need compute distributed globally by default
  • You want integrated storage and database services
  • You're comfortable adapting to the Workers runtime
FeatureVercelCloudflare
Paid plan$20/mo + additional seats$5/mo per account
Data transferIncluded usage, then meteredNo egress fees
Function memoryUp to 4 GB on Pro128 MB per isolate
Execution limit800s on Pro5 min CPU; no HTTP wall-time limit
Next.jsFirst-party supportvinext or OpenNext
Compute placementConfigurable regionsNearest data center by default
Data servicesBlob, cache and integrationsKV, D1, R2, Durable Objects
Key facts from each vendor's own pages, checked November 18, 2026.

Cloudflare Pages or Workers?

Cloudflare now recommends Workers rather than Pages for new web applications.

If you're researching Cloudflare Pages vs Vercel, it's worth understanding how Cloudflare's hosting products have evolved. Cloudflare's Pages documentation, updated in August 2026, identifies Workers as its primary application development platform and explicitly recommends starting new projects with Workers.

Workers static assets allows you to deploy HTML, CSS, JavaScript and other files alongside your server-side code. This means a single Worker can serve your frontend assets and execute application logic. Workers also provides capabilities that aren't available on Pages, including gradual deployments, cron triggers and queue consumers.

Pages remains available and is still a documented option for hosting Next.js static exports. It also supports custom domains whose DNS isn't managed by Cloudflare, which Workers doesn't. For new full-stack applications, however, Workers is the more relevant comparison with Vercel.

Pricing

Cloudflare Workers has a lower starting price, lower compute rates and no egress charges.

As of November 2026, Cloudflare Workers Paid starts at $5 per month per account, including 10 million requests and 30 million CPU milliseconds. Vercel Pro starts at $20 per month, including one deploying member and $20 of usage credit. Each additional deploying member costs $20 per month, bringing the base subscription for a team of five developers to $100.

Cloudflare's usage pricing is also considerably simpler. Workers charges for requests and CPU time, without separate charges for provisioned memory, request duration or bandwidth. Requests to static assets are free and unlimited. Vercel meters CDN requests, data transfer, function invocations, active CPU time and provisioned memory separately, although Pro includes usage allowances.

For teams evaluating Cloudflare vs Vercel primarily on cost, Cloudflare's pricing is particularly attractive for applications that serve substantial traffic or transfer large amounts of data. The actual difference depends on your workload and included allowances. Our Vercel pricing calculator can help you estimate your application's costs on Vercel.

FeatureVercelCloudflare
Paid subscription$20/mo + seats$5/mo per account
Function requests$0.60 per million$0.30 per million
CPU time$0.128/hour$0.072/hour
Provisioned memory$0.0106/GB-hourNo separate charge
Data transfer$0.15/GBFree
Static asset requestsMetered beyond allowanceFree and unlimited
On-demand rates checked November 18, 2026. Vercel rates shown for its iad1 region. Cloudflare's CPU rate is converted from its published rate per million CPU milliseconds. Included allowances and execution environments differ. Cloudflare Containers are excluded from the Workers egress policy.

Free plans and limits

Cloudflare Workers offers a substantial free request allowance, while Vercel Hobby includes more memory and fewer CPU restrictions.

Cloudflare Workers Free includes 100,000 requests per day, with CPU execution limited to 10 milliseconds per invocation. Requests to static assets are free and unlimited. When you exceed the daily Worker request allowance, subsequent Worker requests return an error until the quota resets at midnight UTC.

Vercel's free Hobby plan is restricted to personal, non-commercial projects. Its functions support up to 2 GB of memory and a maximum execution duration of 300 seconds. When you exceed a usage limit, you generally need to wait for the 30-day usage window to reset or upgrade to a paid plan.

Cloudflare also allows an unlimited number of users to manage a Pages project through its dashboard. Vercel charges for additional members who can deploy on Pro, while read-only Viewer seats are free. For teams hosting static sites together, this is another reason to consider Pages.

Next.js

Vercel runs Next.js directly, while Cloudflare recommends vinext, a reimplementation of Next.js built on Vite.

Vercel develops Next.js and provides first-party hosting support for its framework features, including Incremental Static Regeneration (ISR), middleware, image optimization and skew protection. If you're already building with Next.js, Vercel requires less consideration of runtime and framework compatibility.

Cloudflare now recommends vinext as the default way to deploy Next.js applications on Workers. Vinext supports the App Router, Pages Router, React Server Components, Server Actions, streaming SSR and ISR. Cloudflare announced vinext 1.0 as production-ready on September 28, 2026, although its November 5 documentation still describes it as being in beta and recommends running a compatibility check before migrating an existing production application.

Moving to vinext may require application changes. Vercel-specific configuration and packages need to be replaced, native modules such as sharp aren't supported, and persistent ISR caching requires configuration. Image optimization is partially supported. Cloudflare also maintains documentation for the OpenNext adapter for existing applications that can't yet migrate to vinext. Unlike vinext, OpenNext adapts the actual Next.js framework to run on Workers.

FeatureVercelCloudflare
FrameworkNext.jsNext.js API reimplementation
App and Pages RouterSupportedSupported
React Server ComponentsSupportedSupported
Server ActionsSupportedSupported
Streaming SSRSupportedSupported
ISRManagedPersistent cache configurable
Image optimizationBuilt inPartial support
Cloudflare column shows vinext, per Cloudflare's Next.js docs (updated November 5, 2026) and its Vercel migration docs (updated November 11, 2026). OpenNext has a different compatibility profile.

Functions and runtime

Vercel supports larger workloads and more language runtimes, while Workers offers distributed execution with CPU-based limits.

Cloudflare Workers executes code in lightweight isolates with a memory limit of 128 MB per isolate. Vercel Pro functions support up to 4 GB of memory and a wider selection of runtimes, including Node.js, Bun, Python, Rust, Go, Ruby, WebAssembly and Edge. This makes Vercel more flexible for applications with substantial memory requirements or native dependencies.

The platforms also measure execution time differently. Vercel Pro functions have a standard maximum duration of 800 seconds. Workers Paid supports up to five minutes of CPU time per request, but imposes no fixed wall-clock duration while the client remains connected. Time spent waiting for a database query or external API doesn't count toward the Worker's CPU limit.

Workers runs code in the data center closest to the incoming request by default, with placement options for applications that benefit from running closer to their backend. Vercel provides configurable function execution regions. Workers also supports many Node.js APIs, although some, including child_process, worker_threads and vm, are non-functional stubs.

FeatureVercelCloudflare
Maximum memory4 GB128 MB per isolate
Execution duration800 secondsNo fixed HTTP wall-time limit
CPU time limit—Up to 5 minutes
Compute placementConfigurable regionsNearest data center by default
Node.js environmentNode.js runtimeCompatibility layer
Pro and Workers Paid limits, checked November 18, 2026. Cloudflare's CPU limit and Vercel's function duration measure different things and shouldn't be compared directly.

Builds, previews and rollbacks

Both platforms build previews automatically, but Vercel supports far higher build concurrency, while Cloudflare includes monthly build minutes.

Vercel automatically creates preview deployments for pull requests, giving developers a URL where they can test changes before merging them into production. Cloudflare's Workers Builds runs a preview build for every branch other than production and, on GitHub, posts the preview URL as a comment on the pull request. Previews can also be created with Wrangler, each with its own environment variables, secrets and resource bindings.

Vercel meters build resources and supports up to 500 concurrent builds on Pro, with a maximum build duration of 45 minutes. Workers Paid includes 6,000 monthly build minutes, supports six concurrent builds and has a maximum build duration of 20 minutes. Additional Cloudflare build minutes cost $0.005 each.

Both platforms support deployment rollbacks. Vercel Pro can roll back to earlier production deployments, while Cloudflare can restore any of its 100 most recent Worker versions. Cloudflare rollbacks may be restricted when an application has changed its Durable Object classes or removed resources that an earlier deployment depended on.

FeatureVercelCloudflare
Concurrent buildsUp to 5006
Maximum build duration45 minutes20 minutes
Included build minutesMetered builds6,000/month
Preview deploymentsAutomatic per PRAutomatic per branch
RollbacksEarlier production deployments100 most recent versions
Pro and Workers Paid, checked November 18, 2026.

Built-in storage and services

Cloudflare offers a broader collection of integrated infrastructure services, many with usage included in Workers Paid.

Cloudflare's application platform includes KV for key-value storage, D1 for SQL databases, Durable Objects for stateful compute, Queues for asynchronous processing and R2 for object storage. Workers Paid includes usage allowances for KV, D1, Durable Objects and Queues within its $5 monthly subscription.

R2 is billed separately and provides object storage without egress charges. Cloudflare also offers image storage, delivery and transformation through its Images product. Developers can build applications using these services without integrating a separate infrastructure provider for each component.

Vercel provides its own Blob storage and runtime cache, with databases and other services available through Marketplace integrations such as Neon, Supabase and Upstash. This works particularly well for developers who already use these providers or prefer to choose their infrastructure services independently.

FeatureVercelCloudflare
Object storageVercel BlobR2
SQL databaseMarketplace integrationsD1
Key-value storageMarketplace integrationsKV
Application cachingRuntime CacheKV and cache APIs
Stateful compute—Durable Objects
Checked November 18, 2026 against each vendor's docs.

Where Easel fits

If you're considering leaving Vercel because of pricing but don't want to adapt your application to a different runtime, Easel is another option.

Easel follows Vercel's deployment conventions and runs on infrastructure we operate ourselves. Pro costs $20 per month for the entire workspace, with $20 of included usage and no additional seat fees. Next.js applications usually move from Vercel without code changes.

Cloudflare offers a lower starting price and no Workers egress fees. Easel is intended for developers who prefer Vercel-style application hosting without per-seat pricing.

Explore Easel's pricing or read our Vercel migration guide.

Frequently asked questions

Is Cloudflare cheaper than Vercel?

Cloudflare Workers has a lower starting price, lower published request and CPU rates, and no bandwidth charges. As of November 2026, Workers Paid starts at $5 per month, while Vercel Pro starts at $20 per month. Total savings depend on your application's resource consumption and included usage allowances.

Is Cloudflare Pages still recommended?

Cloudflare now recommends Workers for new projects. Workers static assets combines frontend hosting with server-side application execution. Pages remains available and is still a documented option for static exports and custom domains whose DNS isn't managed by Cloudflare.

Can I run Next.js on Cloudflare?

Yes. Cloudflare recommends vinext, a Vite-based reimplementation of the Next.js API surface. It also documents the OpenNext adapter for existing applications that can't yet migrate to vinext. Both approaches have compatibility differences from running Next.js directly on Vercel.

Is Cloudflare or Vercel better for Next.js?

Vercel is the more straightforward choice for developers who want first-party Next.js support without adapting their application to another runtime. Cloudflare is attractive for developers who prioritize lower infrastructure costs and distributed execution, provided their application is compatible with vinext or OpenNext.

Does Cloudflare Workers have a free plan?

Yes. Cloudflare Workers Free includes 100,000 requests per day, with a CPU limit of 10 milliseconds per invocation. Requests to static assets are free and unlimited. The daily Worker request allowance resets at midnight UTC.

Is it difficult to migrate from Vercel to Cloudflare?

It depends on your application's dependencies and framework features. Applications using Vercel-specific configuration, storage packages, native Node.js modules or advanced Next.js features may require changes. Cloudflare provides a migration guide and recommends checking compatibility before moving an existing production application to vinext.

Start deploying

Free to start. Import a repository and get a production URL in a few minutes.