Code · May 16, 2026

How to deploy a full-stack app in 2026: Vercel, Fly.io, Railway, and the realistic paths

The deployment landscape simplified in 2026. Here are the four realistic paths — Vercel, Fly.io, Railway, Cloudflare — and which one fits your stack, traffic, and team.

By ByteLedger Team

Full-stack deployment in 2026 finally got boring in the good way. The Heroku-shaped gap from 2022 was filled by Fly.io, Railway, and a handful of others. Vercel locked in the Next.js market. Cloudflare came at it from the edge. The four-way landscape is real: each has a clear best-fit. This guide walks through them by what you're actually deploying.

What changed in 2026

Render and Heroku lost share to Fly.io and Railway, which offer better defaults at similar prices.
Cloudflare Workers + D1 + R2 matured into a real full-stack platform for edge-first apps. Bundled pricing makes it cheapest at moderate scale.
Vercel Functions ship Bun + Node 22 runtimes with much faster cold starts than 2023 (~20ms vs 200ms).

The four options

Vercel. Default for Next.js and Remix. Best deployment DX in the category — push to git, get a preview URL, merge to main, ship to prod. Hobby tier is generous; Pro at $20/seat is fine for small teams. Trade-off: pricing scales aggressively at high bandwidth; you don't run a Postgres on Vercel.

Fly.io. Best for apps that need persistent compute, databases, or anything stateful. Runs Docker images close to users (40+ regions). Managed Postgres + Redis. Pricing is honest and predictable — closest thing to "Heroku that didn't die".

Railway. Best for "I want all my services in one dashboard". Postgres, Redis, web, worker, cron — all in a project, all networked. Easiest onboarding. Trade-off: less edge-optimized; smaller scale ceiling than Fly.

Cloudflare Workers + D1 + R2. Best for edge-first apps. Workers (compute) + D1 (SQLite-class DB) + R2 (S3-compatible storage) + Pages (static). Cheapest at moderate scale. Trade-off: edge runtime is limited (no native modules, time-bounded execution).

Picks by what you're building

Project	Recommended platform
Next.js marketing or content site	Vercel or Cloudflare Pages
Next.js + DB-heavy product	Vercel + Neon/Supabase (or migrate to Fly)
Remix / TanStack Start app	Vercel or Fly.io
Express/Hono/Fastify backend	Fly.io or Railway
Background workers + cron	Fly.io or Railway
Edge-first, global low-latency	Cloudflare Workers
Side project, fastest time-to-deploy	Railway or Vercel
Production at scale, want flexibility	Fly.io

What real cost looks like

Small app (1k MAU, light DB):

Vercel Hobby + Neon free: $0
Railway starter: ~$5
Fly.io: ~$0 (free tier covers small)

Growing app (50k MAU, real DB):

Vercel Pro + Neon Scale: ~$50-100/mo
Railway: ~$30-60/mo
Fly.io: ~$30-50/mo

Production app (500k MAU):

Vercel Enterprise tier: typically $1k+/mo
Fly.io: ~$200-400/mo
Railway: ~$300-500/mo (gets harder to scale)
Cloudflare: ~$50-150/mo

Numbers approximate; the takeaway is Vercel charges more at scale, the others stay more affordable.

The hidden cost of each

Vercel: Bandwidth and function execution can spike. Watch your dashboard.
Fly.io: Capacity planning is your job; you'll right-size memory and CPU manually.
Railway: Less edge-optimized; resource limits on free tier kick in fast.
Cloudflare: Runtime constraints. Some npm packages don't work. D1 has limits.

A simple deployment recipe (Fly.io example)

fly launch from your repo root.
Confirm Dockerfile / runtime; Fly generates one if missing.
fly secrets set DATABASE_URL=...
fly deploy
fly status — done.

Comparable simplicity on Vercel (vercel), Railway (connect git), and Cloudflare (wrangler deploy).

What to skip

Raw AWS / EC2 for a side project. The leverage of a managed platform far outweighs the AWS price advantage at small scale.
Heroku. Lost the lead; not improving. Existing apps fine; new apps elsewhere.
DIY VPS (DigitalOcean droplet) for production. Possible but you're now also a sysadmin.

FAQ

Vercel vs Cloudflare for Next.js? Vercel for full Next.js feature set. Cloudflare Pages for static or edge-routes-only apps; some Next features require workarounds.

Where do I host Postgres? Neon, Supabase, Fly Postgres, Railway Postgres, AWS RDS — all viable. Neon and Supabase are easiest for serverless platforms.

What about Docker / Kubernetes? Worth it past ~10 services or specific scale needs. For a single app, the managed platform is enough.

Can I self-host? Yes — Coolify, Dokku, CapRover give you "Heroku at home". Trade-off is ops time.