comparison / 11 — updated may 2026

Vercel vs Netlify vs Railway vs Render vs Fly.io

Moving off Vercel? Here's how Netlify, Railway, Render, and Fly.io stack up — different deployment paradigms, different pricing models, and clearer paths to predictable monthly bills than Vercel's usage-based scaling.

entry tier
Vercelfree Hobby (non-commercial)
Netlifyfree · 300 credits/mo
Railway$5/mo Hobby (no free)
Renderfree web service (sleeps)
Fly.iopay-as-you-go (no free)
first paid tier
Vercel$20/dev/mo Pro
Netlify$9/mo Personal · $20/mo Pro
Railway$5/mo Hobby · $20/mo Pro
Render$7/mo Starter · $19/user Pro workspace
Fly.io~$2-20/mo typical usage
deployment model
Vercelserverless · functions
Netlifyserverless · functions
Railwaycontainers · long-running
Rendermanaged services · containers
Fly.ioglobal VMs · per-region
updated
May 2026
verdict.txt — comparisons/vercel-alternatives.mdhonest
$cat verdict.txt

Netlify if you want a Vercel-like experience with a flat-fee Pro plan ($20/mo unlimited seats). Railway if you're shipping full-stack apps and want container deployments with one bill. Render if you need traditional web services + managed databases without the Vercel premium. Fly.io if global edge VMs are the deciding feature. Vercel still wins for tightest Next.js integration if you can stomach the per-developer pricing at scale.

scoreboard / at a glance

At a glance

One row per dimension, the values side-by-side. The olive dot marks the clear winner for that dimension when there is one — most rows are a wash, and that’s the point.

Vercel Inc.

Vercel

Frontend cloud — serverless functions, edge network, the Next.js company's own platform. Free Hobby for non-commercial; $20/dev/mo Pro with usage credits.

Netlify Inc.

Netlify

Vercel's longest-standing alternative. Build/deploy/serve static + functions. Credit-based pricing model since 2025; flat Pro $20/mo unlimited seats as of April 2026.

Railway Corp.

Railway

Container-shaped PaaS. Deploy any Dockerfile or Nixpacks build. Includes databases, Redis, cron — full-stack-in-one-bill. No real free tier, $5/mo Hobby is the floor.

Render Inc.

Render

Traditional PaaS — web services, background workers, cron jobs, managed Postgres and Redis. Free static sites; web services from $7/mo always-on or free with cold starts.

Fly.io

Fly.io

Global edge VMs. Deploy Firecracker microVMs across 35+ regions, pay per second. Pure usage-based — no monthly subscription, $5 trial credit on signup.

Free tierRender's free tier is the only one that lets you host a real always-running service (with cold-start tradeoff). Netlify's free tier is hard-capped so won't surprise-bill. Vercel's Hobby bans commercial use.
Hobby · non-commercial only
free · 300 credits/mo · hard cap
no free · $5/mo Hobby is the floor
free web services (15min idle sleep)
no free · $5 trial credit only
Cheapest commercial tierRailway's $5/mo Hobby is the cheapest entry tier (includes $5 usage credit). Render's $7/mo Starter is comparable per-service. Vercel and Netlify Pro at $20/mo set a higher floor.
$20/dev/mo Pro
$9/mo Personal · $20 Pro
$5/mo Hobby
$7/mo Starter (per service)
~$2-20/mo typical small app
Pricing modelRender's flat $7/mo per service is the most predictable. Vercel/Netlify/Railway mix subscription + usage which can surprise-bill. Fly.io's pure usage-based is predictable if your traffic is — unpredictable if not.
subscription + usage credits + overage
credit-based (Sep 2025+)
subscription + usage credits + overage
flat per-service subscription
pure pay-as-you-go (per second)
What you deployAll five accept arbitrary code. Vercel and Netlify are framework-aware (auto-detect, optimize). Railway and Fly.io are container-shaped. Render straddles both.
Next.js, Nuxt, SvelteKit (any framework)
any static + functions
any Dockerfile or buildpack
web services, workers, cron
any Dockerfile or fly.toml
Built-in servicesRailway includes everything you need for a full-stack app in one bill — Postgres, Redis, cron, private networking. Render is similar. Vercel and Netlify lean serverless-only and require external DBs.
edge functions + cron + storage + analytics
edge functions + forms + identity + blobs
Postgres + Redis + cron + private networking
Postgres + Redis + cron + private networking
Postgres + Redis + Tigris object storage
Global edgeFly.io has the most regions and lets you explicitly control which regions run your machines. Vercel and Netlify auto-distribute static assets but functions run in fewer regions. Railway and Render are single-region per service.
yes · 18+ regions · auto
yes · 6+ regions
no · single region per service
no · single region per service
yes · 35+ regions · explicit per-region
Vendor lock-inRailway, Render, and Fly.io accept standard Docker containers — portable to any container host. Vercel's Next.js features (ISR, Image Optimization, Server Actions) are deeply tied to the platform.
high · Next.js + Vercel features tightly coupled
medium · most apps portable
low · standard containers
low · standard PaaS shapes
low · standard Docker + simple fly.toml
pricing / three scenarios

Pricing at three scales

Three receipts, three scales. The line items are the same; the prices move. Every number is from the public May 2026 pricing page — we round to the nearest dollar but don’t invent.

hobby.txt — personal project · single static site or small app · low trafficmonthly
LINE ITEMVercelNetlifyRailwayRenderFly.io
HostingHobby · non-commercialfreeFree · 300 creditsfreeHobby · $5 base + usage$5Free static site or web servicefree~256MB shared VM$2
TOTAL · monthlyfreefree$5/mofree$2/mo
>Vercel Hobby, Netlify Free, and Render Free all cost $0 for personal sites — Vercel bans commercial use though. Fly.io's minimal always-on VM runs ~$2/mo. Railway has no real free tier so $5/mo is the floor even for hobby sites. For a personal project that just needs to be online, Render Free (with cold starts accepted) or Netlify Free is the path.
side project.txt — paying customers · ~5k MAU · always-on productionmonthly
LINE ITEMVercelNetlifyRailwayRenderFly.io
HostingPro · $20/dev + usage$20Pro · $20 flat unlimited seats$20Hobby · $5 + ~$10 usage$15Starter · $7 + Pro workspace $19$26Small VM + Postgres typical$15
TOTAL · monthly$20/mo$20/mo$15/mo$26/mo$15/mo
>At side-project scale Railway ($15 typical) and Fly.io ($15 typical) come out cheapest. Vercel and Netlify Pro both hit $20 flat. Render's per-service + workspace seat model adds up faster than expected ($26+ with one service). Note: Vercel Hobby is commercially restricted — you legitimately need Pro once you have paying customers.
scale.txt — production · ~50k MAU · marketing site + product + worker + cronmonthly
LINE ITEMVercelNetlifyRailwayRenderFly.io
HostingPro + usage typical$80Pro + credit overage$50Pro $20 + usage typical$50Standard service + Postgres + workspace$70Multi-region machines + Postgres$60
TOTAL · monthly$80/mo$50/mo$50/mo$70/mo$60/mo
>At 50k MAU production scale, Vercel typically lands $50-150/mo depending on Edge Function usage and bandwidth. Netlify Pro stays closer to $50 thanks to flat-fee model. Railway and Fly.io land at $50-60 typical. Render's per-service-plus-workspace-seat math adds up to $70 for an equivalent setup. Self-hosted alternatives (Coolify on Hetzner, Caprover on DigitalOcean) can run the same workload for $10-30/mo if ops appetite exists.
verdict / pick one

When to pick which

pick / vercel

Pick Vercel if…

  • Next.js is your framework — Vercel's Next.js features (ISR, Image Optimization, Server Actions) are deepest on their platform.
  • Edge functions in 18+ regions matter for global low-latency apps.
  • Preview deployments per PR is core to your workflow and the team integrations (GitHub, Slack, Linear) are worth the premium.
  • You're funded enough that $20/dev/mo + usage doesn't dominate your infrastructure bill.
  • AI Gateway, Image Optimization, BotID, and Vercel's other platform products are part of your roadmap.
pick / netlify

Pick Netlify if…

  • You want a Vercel-like serverless experience with flat $20/mo unlimited seats (changed April 2026).
  • Build-time-first workflow — Netlify's build hooks, deploy contexts, and split testing are mature.
  • Forms, Identity, and Edge Functions are part of your shape — Netlify ships these built-in.
  • Credit-based pricing with hard caps on free tier means no surprise bills.
  • Your stack is framework-agnostic (Astro, SvelteKit, Hugo, Next.js all first-class).
pick / railway

Pick Railway if…

  • You're shipping full-stack apps (frontend + backend + database) and want one bill, one dashboard.
  • Containers are your shape — Railway accepts Dockerfile, Nixpacks, or any buildpack with sensible defaults.
  • Built-in Postgres, Redis, cron, and private networking eliminate side integrations.
  • $5/mo Hobby is the cheapest commercial entry across this set.
  • Database-heavy apps where you'd otherwise pay Supabase/Neon plus a separate host.
pick / render

Pick Render if…

  • Flat per-service pricing is your shape — no usage surprises, just $7/mo per always-on web service.
  • You need traditional PaaS shapes (web services, background workers, cron jobs, managed databases) without serverless quirks.
  • Managed Postgres and Redis included with familiar SQL access.
  • Free tier with cold-start sleep is acceptable for non-commercial side projects.
  • Predictable billing matters more than per-feature optimization.
pick / fly.io

Pick Fly.io if…

  • Global edge VMs are the killer feature — deploy machines across 35+ regions, route traffic per-region.
  • Pure pay-as-you-go pricing fits your shape — no subscription, only resource usage by the second.
  • You're comfortable with Dockerfile + fly.toml — Fly's deployment model is closer to AWS than Vercel.
  • Edge-native apps (gaming, multiplayer, low-latency APIs) benefit from per-region machine placement.
  • You're a developer who prefers infrastructure-as-config over UI dashboards.
gotchas / observed

Gotchas, both directions

Common pitfalls visible in public docs and community discussion. None of these will stop you shipping; all of them will cost you an afternoon if you don’t know about them.

  • Vercel / commercial Hobby ban

    Free Hobby plan bans commercial use

    Vercel's Hobby (free) plan explicitly prohibits commercial use. The moment your project has paying customers or generates revenue, you need to upgrade to Pro ($20/dev/mo). This isn't a soft suggestion — Vercel monitors for commercial use signals and will require an upgrade. Plan for the Pro cost from the start if your project will charge.

  • Vercel / usage surprise bills

    Pro $20 plan + usage credits can spike to $200+

    Vercel Pro's $20 includes $20 usage credit. A traffic spike, unoptimized image transformations, or heavy Edge Function usage can push your bill to $200+ unexpectedly. Set Spend Management caps the day you sign up for Pro. The 'my $20/mo plan cost $286' stories are real and well-documented.

  • Netlify / credit-based since 2025

    Pricing model changed to credits in Sep 2025 and refined April 2026

    Netlify moved to a credit-based pricing model in September 2025 and refined it in April 2026 (Pro now flat-fee with unlimited team members). Older comparison articles describing 'build minutes' and 'bandwidth' as separate metering are outdated. Everything bills as credits now (10 credits = 1 GB-hour of serverless compute).

  • Railway / no actual free tier

    $5/mo Hobby is the floor; you always pay the base fee

    Railway's Hobby plan is $5/mo and includes $5 usage credit, but the $5 base fee is always charged even if you use $0. There's no permanently free tier. The $5 trial credit on signup is one-time. For 'I just want to host something free' shapes, Railway isn't the right tool — try Render free web services or Cloudflare Pages.

  • Render / per-service plus workspace seat math

    Pro plan costs more than expected at small team sizes

    Render's pricing is $7/mo per web service plus $19/user/mo for the Pro workspace plan. A solo dev with one web service and one Postgres pays $7 + $19 = $26/mo, not the $7 the marketing page leads with. Add a second service or another team member and the math compounds.

  • Fly.io / free tier removed in 2024

    No more 'free 3 VMs' — pay-as-you-go from machine #1

    Fly.io deprecated its free Hobby plan (3 shared VMs, 160GB bandwidth) in 2024. New accounts get $5 trial credit only. After that, every machine bills per second from the start. For genuinely-free hosting, Fly.io isn't the answer anymore — Render free tier or Cloudflare Workers free tier are the surviving options.

migration / observed patterns

Migrating between them

Editorial framing only — we have not migrated either way ourselves. What follows is the pattern visible in public post-mortems, GitHub issue threads, and conference talks. Take it as observed-pattern, not lived experience.

Vercel ━▶ Netlify

The most common migration in this space. Both platforms accept the same build outputs from Next.js, Astro, SvelteKit, etc. Most Vercel projects deploy to Netlify with `netlify init` and a one-line `[build]` block in netlify.toml. Edge functions translate (Vercel Edge Functions → Netlify Edge Functions, both Deno-based). Image optimization differs slightly; preview deployments work the same.

The migration is usually a weekend, not a project. Keep DNS pointed at Vercel until Netlify build is green, then flip. Plan ~1 hour to translate vercel.json rewrites/headers into netlify.toml syntax.

Vercel ━▶ Railway

Bigger conceptual shift — Vercel is serverless-first, Railway is container-first. For a Next.js app this means containerizing (a Dockerfile or Nixpacks buildpack handles 90% of cases). You lose Vercel's ISR/Image Optimization but gain a long-running server you can SSH into and stable database co-location.

Most teams migrate to Railway specifically to consolidate database + app on one bill. If you're paying Supabase $25 + Vercel $20 = $45/mo for a small app, Railway at ~$15 doing both is the math. Budget a weekend for the containerization + DB import.

Vercel ━▶ Fly.io

Fly.io is closer to AWS than Vercel — you write a fly.toml, build a Docker image, choose regions explicitly. The serverless mental model doesn't carry over. For Next.js this means running a long-running Node server (with `fly launch` auto-generating the Dockerfile) and accepting that Vercel-specific features like ISR or Image Optimization won't be there out of the box.

Teams migrate to Fly.io specifically for global edge VM placement (gaming, multiplayer, real-time apps). For typical SaaS the migration isn't worth the operational complexity. Budget 1-2 weeks if you go this route.