Rendering Strategy → Hosting Compatibility

Not all platforms support all rendering strategies. Start here to eliminate incompatible options before comparing cost or features.

Watch out: Cloudflare Workers uses V8 isolates, not Node.js. Code depending on Node built-ins (fs, path, net) or npm packages that use them will fail without modification. This catches teams moving from Vercel or Railway.

Cost Reality Calculator

Directional estimates based on published pricing tiers. Actual costs vary -- check each platform's current pricing page before committing.

100,000
10K100K1M5M10M
50%
3

Lock-in Exposure

If you adopt these features today, here's what migration looks like in 18 months. Lock-in isn't inherently bad -- but it should be a conscious choice.

Hosting Selector

Answer 6 questions. Get a ranked recommendation with reasoning and warnings.

Operational Complexity Spectrum

Where each platform sits on the zero-ops to full-control axis. Click a platform for details.

Zero-ops Full control
Neither extreme is free. Zero-ops costs dollars at scale and lock-in over time. Full control costs engineering time and operational risk. The right position depends on your team, not your preferences.

Vercel vs Cloudflare

These two dominate the modern hosting conversation. Adjust your context below for a tailored verdict.

Vercel vs Cloudflare
Factor Vercel Cloudflare
Next.js DX Native, first-class Good, not identical
Cost at 1M req/mo $$ $
Cost at 10M req/mo $$$+ $
Runtime Node.js (familiar) V8 isolates (not Node)
Cold starts Occasional Near-zero (isolates)
Global edge ~30 regions 300+ locations
Lock-in surface Moderate (ISR, Image Optimization) Moderate (KV, Durable Objects)
Observability Built-in analytics Workers Analytics or third-party