Railway vs Render
Of the 3,549 makers' products we know the hosting of, 137 chose Render (4%) and 124 Railway (3%); 1 uses both. Among the 860 launched in 2026, Railway is in 8% and Render in 3%, against 2% and 5% of those launched in 2024 or earlier. Railway is the more common pick among Next.js products (42 vs 34). At our calculator's default usage, Railway comes to $45 a month and Render $39, at list prices. On GitHub, 57 public pull requests moved projects from Railway to Render, and 35 the other way.
Two paaS options for hosting. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
Which fits you
- 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.
- You have a long-running server, a background worker and a database to deploy together
Use it whenYou want a managed server, cron jobs and Postgres with a flat per-instance price.
Trade-offFree instances sleep when idle and wake slowly; paid instances are billed whether busy or not.
At a glance
| Used by | 124 makers' products | 137 makers' products |
|---|---|---|
| Cost at default usagerequests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours | $45/mo Hobby | $39/mo Hobby |
| Moved to it on GitHubpull requests since Oct 2024 | 35 from Render | 57 from Railway |
| Downloads | ||
| Pricing | Usage-based with a small monthly minimum. · paid from $5/mo minimum usage | Free tier for static sites and small services; paid per instance. · paid from $7/mo per instance |
| Free tier | No | Yes |
| Open source | No | No |
| Incidents, 90 daysfrom its status page | no public status feed | 13 (6 major) |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for hosting.
| Framework | |||
|---|---|---|---|
| 42 | 34 | All 1312 Next.js products' picks → | |
| 0 | 12 | All 147 React products' picks → | |
| 4 | 2 | All 112 Astro products' picks → | |
| 1 | 2 | All 15 FastAPI products' picks → | |
| 1 | 2 | All 14 Nuxt 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 | 1% 1 | 5% 6 | 118 |
| 2023 | 2% 2 | 1% 1 | 89 |
| 2024 | 2% 11 | 6% 33 | 582 |
| 2025 | 4% 24 | 4% 28 | 629 |
| 2026 | 8% 68 | 3% 28 | 860 |
Cost as you grow
At 100k requests Render costs less ($25 vs $40); from about 10M requests Railway does ($50 vs $54).
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Railway to Render" or the reverse — real code changes, by developers in general rather than makers only.
- contrib: Render to Railway migration patches (#497, #498, #500, #502)Vellar-Wallet/vellar-sdk · 2026-09-30
- TAGit NEXT: move the site and pipelines from Render to Railwaytufeeq/ai · 2026-09-28
- chore(deploy): move hosting from Render to Railway + NeonNae-chan/bizsplit · 2026-09-26
- Revise deploy plan: switch host from Render to Railwayabidayn/fetch · 2026-09-22
- Migrate production ingress from Render to Railwayw129/hashcod-codespace · 2026-09-21
- Switch backend deployment from Render to Railwaydasigconnect-dev/DASIGConnect · 2026-09-20
- infra: migrate backend hosting from Render to Railwaykayibabe/qwantej · 2026-09-19
- fix(mcp): move deploy controls from Render to Railwayannetbg-wq/aicorn-ai-studio · 2026-08-29
- update render to railwaycfabioramos/gerenciadordeaulas_app · 2026-08-28
- Add render-tool skill to integrate Railway render queue (create/check/list/cancel)agteo/hermes-agent-template · 2026-08-24
- Switch the frontend's /api rewrite from Railway to RenderRodolphe27/student-manager · 2026-09-29
- Move the backend from Railway to RenderSpyro007-06/musify · 2026-09-28
- worker: migrate repo_map worker from Railway to Renderallocsys/madmcp · 2026-09-27
- chore: migrate hosting from Railway to RenderSanad-Manga/CareerLink · 2026-09-07
- chore: migrate hosting from Railway to RenderSanad-Manga/CareerLink · 2026-09-07
- chore: migrate API deployment from Railway to Renderjgfurlan/nexus-wallet · 2026-08-31
- Migrate backend + detection engine hosting from Railway to Renderpaulmaloba/garby · 2026-08-29
- Move MCP server deployment from Railway to Render free tierShivratnaK/InvestmentResearchAssistant-MCP · 2026-08-29
- [DEPLOY] Migrate temporary preview deployment from Railway to Rendersage125-ai-scientist-team/SAGE125-AI-Scientist · 2026-08-05
- feat(deploy): migrate from Railway to Render with Docker supportk1nz/splendor · 2026-07-27
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.
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.
Render is stable, easy to use, and get started with - ideally for a startup. We considered Railway but we had some issues with it and didn't have the time to work through them.
Render made hosting and deployment ridiculously simple. It’s honestly so smooth that we dont use Azure and AWS, even though we still have a bunch of credits sitting there.
I love using Plausible for analytics, LogSnag for event tracking, NewRelic for application monitoring, MailGun for emails, Render for hosting, Stripe for billing.
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
Railway or Render: which do makers choose?
Of the 3,549 makers' products we know the hosting of, 137 chose Render (4%) and 124 Railway (3%); 1 uses both. Among the 860 launched in 2026, Railway is in 8% and Render in 3%, against 2% and 5% of those launched in 2024 or earlier. Railway is the more common pick among Next.js products (42 vs 34). At our calculator's default usage, Railway comes to $45 a month and Render $39, at list prices. On GitHub, 57 public pull requests moved projects from Railway to Render, and 35 the other way. Choose Railway if you have a long-running server, a background worker and a database to deploy together; choose Render if you have a long-running server, a background worker and a database to deploy together.
When should I pick Railway over Render?
Pick Railway if: You have a long-running server, a background worker and a database to deploy together.
When should I pick Render over Railway?
Pick Render if: You have a long-running server, a background worker and a database to deploy together.
Which is cheaper, Railway or Render?
At requests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours: Railway $45/mo (Hobby), Render $39/mo (Hobby), at list prices.
How do Railway and Render compare in cost as you grow?
At 100k requests Render costs less ($25 vs $40); from about 10M requests Railway does ($50 vs $54). Cheapest usable plan at each scale, at list prices.
Are people switching from Railway to Render?
Public GitHub pull requests since 2024-10-02: 57 from Railway to Render, 35 from Render to Railway.

