Amazon Web Services vs Railway
Of the 3,549 makers' products we know the hosting of, 460 chose Amazon Web Services (13%) and 124 Railway (3%); 7 use both. Among the 860 launched in 2026, Amazon Web Services is in 9% and Railway in 8%, against 12% and 2% of those launched in 2024 or earlier. They're different kinds of tool, hyperscaler cloud and paaS, so the counts don't measure the same choice. At our calculator's default usage, Amazon Web Services comes to $17 a month and Railway $45, at list prices. On GitHub, 9 public pull requests moved projects from Amazon Web Services to Railway, and 5 the other way.
Two sides of the hosting decision: hyperscaler 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
- The widest catalog of building blocks — Lambda, containers, managed databases, queues — to assemble your own infrastructure.
Use it whenYou need a specific AWS service, enterprise customers ask for it, or you have credits to spend.
Trade-offYou wire up networking, permissions and deploys yourself; billing is per service and hard to predict.
- 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 | 460 makers' products · 18 open-source projects | 124 makers' products |
|---|---|---|
| Cost at default usagerequests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours | $17/mo Pay as you go (Lambda + EC2 t4g.small) | $45/mo Hobby |
| Moved to it on GitHubpull requests since Oct 2024 | 5 from Railway | 9 from Amazon Web Services |
| Downloads | 4.2M/wk−40% vs npm | |
| Pricing | Pay-as-you-go per service; new accounts get up to $200 in Free Tier credits over 6 months. · paid from Pay as you go | Usage-based with a small monthly minimum. · paid from $5/mo minimum usage |
| Free tier | Yes | No |
| Open source | No | No |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for hosting.
| Framework | |||
|---|---|---|---|
| 161 | 42 | All 1312 Next.js products' picks → | |
| 45 | 0 | All 147 React products' picks → | |
| 10 | 4 | All 112 Astro products' picks → | |
| 9 | 0 | All 31 Laravel products' picks → | |
| 5 | 1 | All 15 FastAPI products' picks → | |
| 4 | 0 | All 17 Django 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 | 19% 22 | 1% 1 | 118 |
| 2023 | 16% 14 | 2% 2 | 89 |
| 2024 | 10% 59 | 2% 11 | 582 |
| 2025 | 14% 89 | 4% 24 | 629 |
| 2026 | 9% 80 | 8% 68 | 860 |
Cost as you grow
At 100k requests Amazon Web Services costs less ($16 vs $40); from about 50M requests Railway does ($90 vs $160). They're different kinds of tool — hyperscaler cloud and paaS — so the prices don't buy the same thing.
The numbers, plan by plan
| Requests per month | Amazon Web Services | Railway |
|---|---|---|
| 0.1 | $16 Pay as you go (Lambda + EC2 t4g.small) | $40 Hobby |
| 0.5 | $16 Pay as you go (Lambda + EC2 t4g.small) | $41 Hobby |
| 1 | $16 Pay as you go (Lambda + EC2 t4g.small) | $41 Hobby |
| 5 | $17 Pay as you go (Lambda + EC2 t4g.small) | $45 Hobby |
| 10 | $32 Pay as you go (Lambda + EC2 t4g.small) | $50 Hobby |
| 50 | $160 Pay as you go (Lambda + EC2 t4g.small) | $90 Hobby |
| 100 | $320 Pay as you go (Lambda + EC2 t4g.small) | $140 Hobby |
| 500 | $1,600 Pay as you go (Lambda + EC2 t4g.small) | $540 Hobby |
From each vendor's pricing page: Amazon Web Services, Railway.
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Amazon Web Services to Railway" or the reverse — real code changes, by developers in general rather than makers only.
- deploy(data-collector): migrate from Railway to AWS Montrealbillybrichards/novakash · 2026-04-11
- deploy(macro-observer): migrate from Railway to AWS Montrealbillybrichards/novakash · 2026-04-11
- [synthmind-bot] Railway Secures $100 Million to Challenge AWS with AI-Native Cloud Infrastructure — 2026-03-27administrakt0r/AIautonomousBlogMY · 2026-03-27
- Update railway Database to RDS AWSPraneeth3717/expense-tracker · 2026-03-13
- Switch deployment from Railway to AWSpshrote-afk/JavaProjects-webapp · 2025-12-13
- Point CI at AWS and stop it deploying to the retired Railway backendCodeUche/finventory · 2026-09-06
- Remove Kyndryl branding + move deployment from AWS to Railwaysmithdouglas404/strategic-narrative-builder · 2026-08-30
- chore: migrate hosting from AWS ECS to Railway + VercelruchirV/StockTracker · 2026-04-25
- Switch backend deployment from AWS ECS to Railwaysikakente/sikasem · 2026-04-06
- Remove AWS dependencies and switch email backend to SendGrid for Railwaycarlosarturoleon/portfolio-site · 2026-03-26
- chore: migrate database from AWS to Railwaytrgcghai/Goat-JobHunter-Be · 2026-03-18
- feat: migrate infrastructure from AWS to Railwayotomatty/zedi · 2026-02-27
- Railway Migration: AWS to Railway Infrastructurehongsw/serverless-openclaw · 2026-02-15
- feat: migrate from AWS to Railway deployment with automated workflowsondatra-ai/awesome-claude-mcp · 2025-09-17
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.
We are so excited to integrate with AWS Lambda. Look for our upcoming co-authored blog about how Fleak and AWS Lambda bring goodness to data teams and help them win their time back!
AWS provides the global infrastructure we need to deliver low-latency voice translation to users worldwide. Their reliable services ensure our calls connect seamlessly across regions.
…m - for customer support, knowledge base, and live chat support Webflow - for our website AWS - for our cloud hosting needs Figma - for all our design collaboration Microsoft Clarity…
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
Amazon Web Services or Railway: which do makers choose?
Of the 3,549 makers' products we know the hosting of, 460 chose Amazon Web Services (13%) and 124 Railway (3%); 7 use both. Among the 860 launched in 2026, Amazon Web Services is in 9% and Railway in 8%, against 12% and 2% of those launched in 2024 or earlier. They're different kinds of tool, hyperscaler cloud and paaS, so the counts don't measure the same choice. At our calculator's default usage, Amazon Web Services comes to $17 a month and Railway $45, at list prices. On GitHub, 9 public pull requests moved projects from Amazon Web Services to Railway, and 5 the other way. Choose Amazon Web Services if the widest catalog of building blocks — Lambda, containers, managed databases, queues — to assemble your own infrastructure; choose Railway if you have a long-running server, a background worker and a database to deploy together.
Can you use Amazon Web Services and Railway together?
7 makers' products we track use both, often one replacing the other or each for a different part of the product: Notte, Symvol Video AI for Education, Blink.new, Reloop, BetterClaw and others.
When should I pick Railway over Amazon Web Services?
Pick Railway if: You have a long-running server, a background worker and a database to deploy together.
Which is cheaper, Amazon Web Services or Railway?
At requests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours: Amazon Web Services $17/mo (Pay as you go (Lambda + EC2 t4g.small)), Railway $45/mo (Hobby), at list prices.
How do Amazon Web Services and Railway compare in cost as you grow?
At 100k requests Amazon Web Services costs less ($16 vs $40); from about 50M requests Railway does ($90 vs $160). Cheapest usable plan at each scale, at list prices.
Are people switching from Amazon Web Services to Railway?
Public GitHub pull requests since 2024-10-02: 9 from Amazon Web Services to Railway, 5 from Railway to Amazon Web Services.

