Cloudflare vs. Vercel – Which One Should You Use When?

What This Is About

We build websites and apps with Lovable, a Playwright SSG pipeline, and edge deploy. For a long time, our dist/ defaulted to Vercel. Over the past months, more and more projects land on Cloudflare – not out of ideology, but because the balance has shifted.

If you're facing the same decision today: here's the honest comparison from daily practice.

The Two Philosophies

Before diving into features – the two platforms come from different corners:

Vercel is the framework-first platform. Born out of Next.js, optimized for exactly that stack. The mission: "Frontend Cloud" – every framework, every deployment, every preview should feel like magic. DX above all.

Cloudflare is the infrastructure-first platform. Born out of DNS and CDN, expanded into a complete edge suite. The mission: get the whole internet onto their network – with Workers, R2, D1, KV, Durable Objects as building blocks. Web hosting (Pages) is just one application of that.

This DNA shapes every design decision. Once you grasp that, the choice becomes clearer.

Hosting & Edge Network

Cloudflare has a structural advantage here: the V8 Isolates architecture of Workers boots in under a millisecond – no real cold starts. Vercel's Serverless Functions run on AWS Lambda underneath and have the classic cold-start problem, even with Edge Functions.

Developer Experience

This is where Vercel still shines brightest:

• Preview deployments per pull request, automatically
• Framework detection works out of the box for 30+ frameworks
• Analytics, Speed Insights, Log Drains cleanly integrated
• CLI is excellent, the dashboard is tidy
• v0 as in-house AI builder hooks in directly

Cloudflare Pages has caught up massively in 2025/2026. Git integration, preview deployments, build logs – it all works. But: at many points you notice that hosting is one platform among many for Cloudflare, not the core. The dashboard can overwhelm, the docs are good but broad.

My take: For solo devs and small teams, Vercel remains more pleasant. But those already running Cloudflare infrastructure (DNS, R2, Workers) benefit from the consolidated platform.

Backend Suite

This is where the game turns.

Vercel offers:

• Serverless / Edge Functions
• KV (via Redis partner)
• Postgres (via Neon partner)
• Blob Storage (relatively new)

Cloudflare offers:

• Workers (Compute)
• D1 (SQLite at the edge)
• R2 (S3-compatible storage, zero egress fees)
• KV (Key-Value)
• Durable Objects (Stateful Workers)
• Queues, Vectorize (vector DB), AI Workers

Cloudflare has the full backend stack – first-party, with consistent billing and no external partners. Vercel is strategically weaker here, which they know themselves: they're investing heavily, but Cloudflare's multi-year head start won't be closed quickly.

If you want the bigger picture: we broke down Cloudflare's real strategy in detail.

Pricing

Now it gets concrete. Both have generous free tiers, but once you scale, costs diverge dramatically.

The egress topic is Cloudflare's killer advantage. If you run a traffic-heavy site – image/video-heavy, downloads, large assets – you save four to five figures per year on Cloudflare easily.

Vercel's bandwidth costs are the most common nasty surprise in our client conversations. A viral landing page can produce a $500 bill that would have cost $0 on Cloudflare.

Lock-in

Vercel lock-in builds subtly:

• next/image, next/font, ISR only work maximally well on Vercel
• vercel.json and Edge Config are proprietary
• Migrating a large Next.js app to Cloudflare is doable but work

Cloudflare bets on open standards:

• Workers use standard Web APIs (Fetch, Request, Response)
• R2 is S3-compatible
• D1 is SQLite – portable
• Migrating away from Cloudflare would be comparatively painless

That's not a coincidence. Cloudflare's strategy works through low switching costs – easy to enter, easy to leave, but you stay because it's good.

Our Decision Matrix

From 50+ deployed projects, here are our rules of thumb:

Pick Vercel when:

• You're building a pure Next.js app (ISR, App Router, RSC)
• Your team is small and needs maximum DX
• You need preview deployments for non-technical stakeholders
• You use v0 as an AI builder in your workflow
• Traffic stays manageable (< 100 GB/month)

Pick Cloudflare when:

• You're building a Vite/SPA with prerendering (our stack)
• You need backend pieces: DB, storage, queues, workers
• Traffic-heavy use cases: images, videos, downloads
• You value low switching costs and open standards
• Cost control during growth is critical
• You need DDoS protection and bot management at enterprise level

Both work well when:

• You use Cloudflare for DNS (free, excellent) and host on Vercel
• You put R2 as asset storage in front of a Vercel-hosted app

Our Own Journey

This site (till-freitag.com) currently still runs on Vercel – the setup works, no reason for migration stress. For new client projects, however, we increasingly pick Cloudflare as default, especially when:

• the app has a backend share (auth, DB, file uploads)
• imagery and downloads dominate
• budget is tight and predictability matters

Migrating a Lovable project from Vercel to Cloudflare Pages takes about 15 minutes once you've done it once. We'll write a separate tutorial on that soon.

Bottom Line

There's no "Vercel is dead" or "Cloudflare wins everything." Both have their strengths:

• Vercel = best DX, perfect for Next.js, expensive at scale
• Cloudflare = best infrastructure, complete backend suite, best prices

If you're starting fresh today with no existing Next.js investment, Cloudflare is the strategically smarter choice in most cases. If you think deeply in Next.js + DX terms, Vercel remains the obvious answer.

The honest truth: the bet we described in our strategy article is playing out. Cloudflare is systematically pulling the backend for the next generation of AI-generated apps onto its network – and we're migrating along.

👉 Building a Vibe Coding app and wondering which stack carries you long-term? Talk to us.