Head-to-head

Vercel vs Cloudflare Pages

Two hosts, side by side. Pricing, features, and the trade-offs that actually matter.

Vercel from Free

The default home for Next.js, with a polished DX and a love-it-or-hate-it bill.

HQ US · founded 2015

Static + edge-functions hosting on the world's biggest CDN, free for almost everyone.

HQ US · founded 2009

Quick verdict

Cheapest: Cloudflare Pages wins on entry price (Free vs Free).
More features: Vercel ships more first-party platform features out of the box.
Region: Vercel is HQ'd in US; Cloudflare Pages in US.

Cheapest plans, side by side

VercelCloudflare Pages
Entry planHobbyFree
PriceFreeFree
CPU
RAM0 GB0 GB
Disk— GB— GB
Bandwidth100 GBunmetered

Feature parity

VercelCloudflare Pages
Managed Postgres×
Managed Redis×
Object storage
One-click apps×
Private network××
IPv6×
DDoS protection
Snapshots××
Public API
Terraform×

Vercel pros

  • +Push to GitHub, get a preview URL — no other host has tightened this loop further
  • +Image optimisation, ISR, edge functions all wired in by default
  • +Generous free tier covers solo side projects

Vercel cons

  • Bandwidth and function execution beyond the free tier scale aggressively
  • Pro plan starts at $20/seat/month — expensive for a solo dev
  • Long-running functions are not the platform's strength (15-min cap, costly)

Cloudflare Pages pros

  • +Unlimited bandwidth on the free tier — no caveats
  • +Cloudflare's CDN is in 300+ cities; latency is near-optimal everywhere
  • +Workers (edge functions) and KV/D1/R2 in the same dashboard

Cloudflare Pages cons

  • Build runners are shared and slower than Vercel/Netlify on cold cache
  • Workers have a different mental model than Lambda — porting Express apps is non-trivial
  • Logs and observability lag behind Vercel's polish