Fly.io vs Vercel
Two sides of the hosting decision: container platform and frontend cloud. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
Which fits you
- Your users are spread across continents and the app runs in Docker
Use it whenYour app runs in Docker and should serve users in several regions.
Trade-offMore operations work than a PaaS.
- You built a Next.js or other frontend-heavy app and want preview URLs on every pull request
Use it whenYour app is Next.js, or you want a preview URL on every pull request with no setup.
Trade-offThe Hobby plan is non-commercial; costs grow with usage.
At a glance
| Used by | 66 makers' products · 52 open-source projects | No maker's product yet |
|---|---|---|
| Cost at default usagerequests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours | $15/mo Pay As You Go | $40/mo Pro + Flat Rate CDN 10M |
| Moved to it on GitHubpull requests since Oct 2024 | 11 from Vercel | 7 from Fly.io |
| Downloads | 5.7M/wk+93% vs npm | |
| Pricing | Usage-based. · paid from $1.94/mo (shared-cpu-1x) | Free Hobby plan (non-commercial); Pro per seat plus usage. · paid from $20/mo |
| Free tier | No | Yes |
| Open source | No | No |
| Incidents, 90 daysfrom its status page | 25+ (11 major) | 31 (10 major) |
Cost as you grow
At 100k requests Vercel costs less ($0 vs $13); from about 5M requests Fly.io does ($15 vs $40). They're different kinds of tool — container platform and frontend cloud — so the prices don't buy the same thing.
The numbers, plan by plan
| Requests per month | Fly.io | Vercel |
|---|---|---|
| 0.1 | $13 Pay As You Go | $0 Hobby |
| 0.5 | $13 Pay As You Go | $0 Hobby |
| 1 | $13 Pay As You Go | $0 Hobby |
| 5 | $15 Pay As You Go | $40 Pro + Flat Rate CDN 10M |
| 10 | $17 Pay As You Go | $40 Pro + Flat Rate CDN 10M |
| 50 | $33 Pay As You Go | $127 Pro + Flat Rate CDN 50M |
| 100 | $53 Pay As You Go | $353 Pro + Flat Rate CDN 150M |
| 500 | $213 Pay As You Go | $2,766 Pro (on-demand CDN) |
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Fly.io to Vercel" or the reverse — real code changes, by developers in general rather than makers only.
- Auction correction Block 7: harden Vercel to Fly reliabilitycarmaziums/carmazium · 2026-09-27
- Block 1: harden Vercel to Fly backend readscarmaziums/carmazium · 2026-09-25
- Migrate Vercel runtime to Fly.io, Cloudflare, and Xatafratercem-design/cultcodex-v2 · 2026-09-15
- Migrate off Vercel to Fly.io (Django gunicorn, Mumbai)samy123-cmd/career-reality · 2026-08-06
- Switch production deployment from Vercel to Fly.io container runtimekhamanihendrix1-sys/meridian-signal-service · 2026-06-27
- Move from vercel to flysnide/davesnider.com · 2026-06-02
- Remove Vercel serverless API; route everything to Fly backendpolluxchou/15signals · 2026-05-22
- Migrate all apps from Vercel to Fly.io for persistent VM supportCamJohnson26/agent-first-fizzbuzz-scalable · 2026-04-19
- Configure Vercel frontend to use Fly API base URLMrMiless44/Infamous-freight · 2025-12-24
- Migrate host from Vercel to FlySiege-Perilous/tableslayer · 2024-12-19
- Migrate JeremyOS from Fly to Vercel (KV + Blob)jeremyPharmer/jeremyOS · 2026-08-31
- infrastructure(vb-manager-next-mobile): Migrate deployment from Fly.io to Verceliamharryliu/vigilant-broccoli · 2026-08-19
- chore: deploy the backend to Fly.io and the frontend to Vercel (PET-53)AntePrkacin/personal-expense-tracker · 2026-08-04
- Migrate hosting from Fly.io to VercelHelloImFranky/trusty_algebra_tutor · 2026-07-11
- Deploy backend to Fly.io and frontend to Vercel (#100)jonathanstelman/indy-explorer · 2026-05-24
- feat: Redirect fly.dev traffic to Vercel domaingabrieltan0506-prog/mvstudiopro · 2026-05-16
- Deploys to Fly.io but images not linking due to vercel adapterplayfulprogramming/playfulprogramming · 2024-12-03
What makers say
Makers on using it for hosting, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.
Machines on Fly made it easy to build SSL-secured proxies and backends for keeping cross-internet Pig automations safe and encrypted.
Shoutout to @flyDev - Deploying Mascotly globally was seamless thanks to Fly.io. It made it super easy to get our backend up and running close to users with minimal config. Fast, reliable, and developer-friendly - couldn’t ask for more! 🚀🌍
Fly’s setup process was smooth and intuitive. Hosting APIs globally with minimal configuration was a huge time-saver.
No maker quote about Vercel for hosting yet.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.

