Vercel vs Netlify vs Cloudflare Pages vs Fly.io vs Railway — Hosting Compared

Hosting comparisons go stale quickly, but the decision axes stay stable: DX, runtime flexibility, edge network, and bill shock tolerance.

Vercel

Still the path of least resistance for Next.js. Preview deploys and DX remain excellent. Watch usage-based pricing as traffic and serverless invocation counts grow.

Netlify

Strong JAMstack heritage, good DX, broad framework support. Competing hard on developer experience and AI-era workflows.

Cloudflare Pages (+ Workers)

Price/performance and global edge are the magnets. Mental model shifts toward Workers; brilliant when it fits, fiddly when your app assumes Node-isms.

Fly.io

Containers close to users without full Kubernetes cosplay. Great for apps that need long-lived processes or custom runtimes.

Railway

Delightful “just deploy the thing” experience for backends and databases in one pane. Ideal for prototypes and small production apps; validate scale assumptions early.

Salt Index cheat sheet

• Next.js marketing + app combo → Vercel first
• Edge-heavy, cost-sensitive → Cloudflare
• Custom containers → Fly.io
• Small team shipping API + DB fast → Railway
• Multi-framework static/SSR mixed → Netlify

Worth its salt means picking the host that matches your runtime — not the one with the prettiest landing page the week you signed up.