Netlify vs Railway
Of the 3,549 makers' products we know the hosting of, 265 chose Netlify (7%) and 124 Railway (3%); 2 use both. Among the 860 launched in 2026, Netlify is in 4% and Railway in 8%, against 7% and 2% of those launched in 2024 or earlier. They're different kinds of tool, frontend cloud and paaS, so the counts don't measure the same choice. At our calculator's default usage, Netlify comes to $30 a month and Railway $45, at list prices. On GitHub, 7 public pull requests moved projects from Netlify to Railway, and 0 the other way.
Two sides of the hosting decision: frontend cloud 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
- You built a Next.js or other frontend-heavy app and want preview URLs on every pull request
Use it whenYour site is static or JAMstack on a framework other than Next.js.
Trade-offServer-side features run as functions with time limits; long-running work needs another host.
- 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 | 265 makers' products · 62 open-source projects | 124 makers' products |
|---|---|---|
| Cost at default usagerequests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours | $30/mo Pro 3,000 credits | $45/mo Hobby |
| Moved to it on GitHubpull requests since Oct 2024 | fewer than 3 | 7 from Netlify |
| Downloads | 375.2k/wk−47% vs npm | |
| Pricing | Free tier; paid plans from $9/month, billed by monthly credits. · paid from $9/mo | Usage-based with a small monthly minimum. · paid from $5/mo minimum usage |
| Free tier | Yes | No |
| Open source | No | No |
| Incidents, 90 daysfrom its status page | 15 (4 major) | no public status feed |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for hosting.
| Framework | |||
|---|---|---|---|
| 58 | 42 | All 1312 Next.js products' picks → | |
| 24 | 4 | All 112 Astro products' picks → | |
| 9 | 0 | All 147 React products' picks → | |
| 4 | 1 | All 14 Nuxt products' picks → | |
| 2 | 1 | All 8 Ruby on Rails 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 | 13% 15 | 1% 1 | 118 |
| 2023 | 3% 3 | 2% 2 | 89 |
| 2024 | 6% 36 | 2% 11 | 582 |
| 2025 | 6% 35 | 4% 24 | 629 |
| 2026 | 4% 32 | 8% 68 | 860 |
Cost as you grow
At 100k requests Netlify costs less ($9.00 vs $40); from about 10M requests Railway does ($50 vs $56). They're different kinds of tool — frontend cloud and paaS — so the prices don't buy the same thing.
The numbers, plan by plan
| Requests per month | Netlify | Railway |
|---|---|---|
| 0.1 | $9.00 Personal | $40 Hobby |
| 0.5 | $9.00 Personal | $41 Hobby |
| 1 | $12 Personal | $41 Hobby |
| 5 | $30 Pro 3,000 credits | $45 Hobby |
| 10 | $56 Pro 5,000 credits | $50 Hobby |
| 50 | $262 Pro 20,000 credits | $90 Hobby |
| 100 | $529 Pro 20,000 credits | $140 Hobby |
| 500 | $2,662 Pro 20,000 credits | $540 Hobby |
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Netlify to Railway" or the reverse — real code changes, by developers in general rather than makers only.
- Migrate Cee Jay Solutions from Supabase/Netlify to RailwayJolly11nth/Cee-Jay-Solutions · 2026-09-25
- Link Netlify frontend to Railway backend using environment variablesMAAx-Dev-s/CryptoVision-pro · 2026-09-06
- Migrate hosting from Netlify to RailwayBraden-Long/uva-cs4971-hoos-helping · 2026-08-20
- Add Netlify edge proxy to connect frontend to Railway APIrextest84-source/verifyid · 2026-06-08
- Netlify to railwayblinkorb/destiny-2-pattern-tracker · 2026-01-24
- redirect netlify traffic to railwaychrisgioia64/contra-costa-map · 2025-12-26
- fix: fallback api base on netlify to railway prodomarabdelwahed22/student-grade-tracker · 2025-12-20
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.
Hosts tidymacapp.com and serves the app itself. Deploying is dragging a folder onto a page. For a solo dev shipping a $9 utility, that's exactly the right amount of infrastructure.
Our front end runs on Netlify, as do most of our examples where serverless functions are used. It's so easy to get started, and so powerful once you start pushing harder.
Upwork - hiring contractors Netlify - hosting the front end What have been the most influential books, podcasts, or other resources? Paul Graham’s blog.
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
Netlify or Railway: which do makers choose?
Of the 3,549 makers' products we know the hosting of, 265 chose Netlify (7%) and 124 Railway (3%); 2 use both. Among the 860 launched in 2026, Netlify is in 4% and Railway in 8%, against 7% and 2% of those launched in 2024 or earlier. They're different kinds of tool, frontend cloud and paaS, so the counts don't measure the same choice. At our calculator's default usage, Netlify comes to $30 a month and Railway $45, at list prices. On GitHub, 7 public pull requests moved projects from Netlify to Railway, and 0 the other way. Choose Netlify if you built a Next.js or other frontend-heavy app and want preview URLs on every pull request; choose Railway if you have a long-running server, a background worker and a database to deploy together.
Can you use Netlify and Railway together?
2 makers' products we track use both, often one replacing the other or each for a different part of the product: Cleanlist AI, Aviquill.
When should I pick Netlify over Railway?
Pick Netlify if: You built a Next.js or other frontend-heavy app and want preview URLs on every pull request.
When should I pick Railway over Netlify?
Pick Railway if: You have a long-running server, a background worker and a database to deploy together.
Which is cheaper, Netlify or Railway?
At requests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours: Netlify $30/mo (Pro 3,000 credits), Railway $45/mo (Hobby), at list prices.
How do Netlify and Railway compare in cost as you grow?
At 100k requests Netlify costs less ($9.00 vs $40); from about 10M requests Railway does ($50 vs $56). Cheapest usable plan at each scale, at list prices.
Are people switching from Netlify to Railway?
Public GitHub pull requests since 2024-10-02: 7 from Netlify to Railway.

