Fly.io vs Railway
Of the 3,549 makers' products we know the hosting of, 124 chose Railway (3%) and 74 Fly.io (2%); 4 use both. Among the 860 launched in 2026, Fly.io is in 1% and Railway in 8%, against 3% and 2% of those launched in 2024 or earlier. They're different kinds of tool, container platform and paaS, so the counts don't measure the same choice. Fly.io is the more common pick among Astro products (5 vs 4). At our calculator's default usage, Fly.io comes to $15 a month and Railway $45, at list prices. On GitHub, 15 public pull requests moved projects from Fly.io to Railway, and 12 the other way.
Two sides of the hosting decision: container platform and paaS. 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 have a long-running server, a background worker and a database to deploy together
Use it whenYour app is a server plus a database and a worker, and you want them in one project.
Trade-offUsage-based billing needs watching; fewer regions and compliance options than a hyperscaler.
At a glance
| Used by | 74 makers' products · 55 open-source projects | 124 makers' products |
|---|---|---|
| Cost at default usagerequests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours | $15/mo Pay As You Go | $45/mo Hobby |
| Moved to it on GitHubpull requests since Oct 2024 | 12 from Railway | 15 from Fly.io |
| Downloads | ||
| Pricing | Usage-based. · paid from $1.94/mo (shared-cpu-1x) | Usage-based with a small monthly minimum. · paid from $5/mo minimum usage |
| Free tier | No | No |
| Open source | No | No |
| Incidents, 90 daysfrom its status page | 25+ (14 major) | no public status feed |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for hosting.
| Framework | |||
|---|---|---|---|
| 17 | 42 | All 1312 Next.js products' picks → | |
| 5 | 4 | All 112 Astro products' picks → |
New launches vs older products
A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the hosting decision (by the year they launched on Product Hunt).
| Launched | Products | ||
|---|---|---|---|
| 2022 or earlier | 3% 4 | 1% 1 | 118 |
| 2023 | 3% 3 | 2% 2 | 89 |
| 2024 | 3% 20 | 2% 11 | 582 |
| 2025 | 3% 22 | 4% 24 | 629 |
| 2026 | 1% 10 | 8% 68 | 860 |
Cost as you grow
At 100k requests Fly.io costs less ($13 vs $40); and still does at 500M requests ($213 vs $540). They're different kinds of tool — container platform and paaS — so the prices don't buy the same thing.
The numbers, plan by plan
| Requests per month | Fly.io | Railway |
|---|---|---|
| 0.1 | $13 Pay As You Go | $40 Hobby |
| 0.5 | $13 Pay As You Go | $41 Hobby |
| 1 | $13 Pay As You Go | $41 Hobby |
| 5 | $15 Pay As You Go | $45 Hobby |
| 10 | $17 Pay As You Go | $50 Hobby |
| 50 | $33 Pay As You Go | $90 Hobby |
| 100 | $53 Pay As You Go | $140 Hobby |
| 500 | $213 Pay As You Go | $540 Hobby |
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Fly.io to Railway" or the reverse — real code changes, by developers in general rather than makers only.
- chore(docs): correct stale Railway infra references to Fly in agent runbooks + CLAUDEGetCollectRx/Collect-RX · 2026-07-21
- Repoint production API base from dead Railway backend to live Fly.io Braingenewgeorge76/gemini2 · 2026-07-15
- chore(deploy): migrate deployment and configuration from Railway to Fly.iomaru-story/wedding-ecosystem · 2026-07-10
- ops: switch deploy target from Railway to Fly.ioQuantum-Global-Group/sigma · 2026-05-16
- deploy: switch from Railway to Fly.io (Tokyo region)TripAndCode/transit-app · 2026-05-09
- chore: switch deployment target from Railway to Fly.ioChristopher-Crumley/ai-clinical-copilot · 2026-04-28
- fix(#216): update deploy workflow from Railway to fly.iowkliwk/recallth-backend · 2026-04-24
- Migrate from Railway to Fly.io for mTLS supportmyrobotaxi/telemetry · 2026-03-23
- chore: migrate sidecar deploy from Railway to Fly.ioboovines/forward · 2026-03-08
- Migrate deployment from Railway to Fly.ioenboxorg/enbox · 2026-02-16
- Cut over the public A2A gate from Fly to Railwaydlescanogithub/argentine-a2a · 2026-10-01
- feat(infra): migrate cloud production from Fly.io to Railwaykennygeiler/DeployAI · 2026-08-11
- Cut over marrow from Fly to Railway (CI smoke + docs)F0rge/f0rge · 2026-08-02
- Switch deployment from Fly.io to Railwayhedde-whatever/lumen · 2026-06-08
- fix: update API URL from fly.dev to Railwaymarcelrezkova/CarValueEngine · 2026-05-26
- chore(deploy): switch from Fly.io to Railway + tsx runtimedropdowner1/dropdowner1.github.io · 2026-05-19
- chore(deploy): migrate server from Fly.io to Railwayashlrai/ashlr-plugin · 2026-05-01
- Migrate backend from Fly.io to Railway; harden CORS parsingjonx0037/multimodal-financial-rag · 2026-04-18
- Move from Fly to Railway, and mongo to sqlitenoisebridge/nb.wtf · 2026-04-13
- chore(infra): migrate backend deployment from Fly.io to RailwayRatioraji/wiki-generator · 2026-03-23
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.
Helped us deploy Openchangelog all over the globe for lightning-fast changelog serving worldwide.
Their edge infra is key to our ability to have fast edge ingest on our services.
Railway makes deploying and scaling our backend effortless. Push to main, it's live. No Dockerfiles to debug, no infra to babysit. We went from zero to production in an afternoon.
Railway made it simple to ship Git Pitcher’s web and API services quickly. I used it to deploy the production app without spending time fighting infrastructure.
Railway is the most DevX friendly infra platform we've used. David Banys and their team are super responsive and solve any problems we encounter.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- Platform-wide outages, including one when Google Cloud blocked Railway's account, took customer services down. HNHN 2HN 3HN 4
- It adds a middle layer on Google Cloud that controls your availability, features and security. HNHN 2
- API tokens grant every operation without clear warnings, which let an agent instantly delete a production database. HNHN 2
Who uses each
What makers pair each with
Neither quite right?
See the whole hosting decision →Questions
Fly.io or Railway: which do makers choose?
Of the 3,549 makers' products we know the hosting of, 124 chose Railway (3%) and 74 Fly.io (2%); 4 use both. Among the 860 launched in 2026, Fly.io is in 1% and Railway in 8%, against 3% and 2% of those launched in 2024 or earlier. They're different kinds of tool, container platform and paaS, so the counts don't measure the same choice. Fly.io is the more common pick among Astro products (5 vs 4). At our calculator's default usage, Fly.io comes to $15 a month and Railway $45, at list prices. On GitHub, 15 public pull requests moved projects from Fly.io to Railway, and 12 the other way. Choose Fly.io if your users are spread across continents and the app runs in Docker; choose Railway if you have a long-running server, a background worker and a database to deploy together.
Can you use Fly.io and Railway together?
4 makers' products we track use both, often one replacing the other or each for a different part of the product: Blink.new, Cronloop AI, stagewise, BetterClaw.
When should I pick Fly.io over Railway?
Pick Fly.io if: Your users are spread across continents and the app runs in Docker.
When should I pick Railway over Fly.io?
Pick Railway if: You have a long-running server, a background worker and a database to deploy together.
Which is cheaper, Fly.io or Railway?
At requests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours: Fly.io $15/mo (Pay As You Go), Railway $45/mo (Hobby), at list prices.
How do Fly.io and Railway compare in cost as you grow?
At 100k requests Fly.io costs less ($13 vs $40); and still does at 500M requests ($213 vs $540). Cheapest usable plan at each scale, at list prices.
Are people switching from Fly.io to Railway?
Public GitHub pull requests since 2024-10-02: 15 from Fly.io to Railway, 12 from Railway to Fly.io.

