# Railway 94 Hacker News commenters recommended Railway and 159 criticized it, November 2025 to November 2026. It was recommended in 10 of 13 months; owners who said how long report a median of 0.33 years (7 owners). **Verdict:** Easy deploys for backend apps and small sites with cheap usage-based pricing and a clean UI, though critics cite outages, security incidents and weak API key permissions. ## Why people recommend it - Easy deploys and clean UI (4 comments): "They have a nice UI, support deploy any kind of backend-involved apps as long as it can be built into a docker container." ([source](https://news.ycombinator.com/item?id=46977191)) "Having recently migrated my websites off of Vercel and onto Railway, I can confirm, it's pretty straightforward to not touch Vercel." ([source](https://news.ycombinator.com/item?id=47705958)) "Railway has consistently been responsive and actually understands the problem you're describing." ([source](https://news.ycombinator.com/item?id=46979828)) - Low, usage-based pricing (4 comments): "they have one of the best sandbox environments on the market with pay per utilized resources pricing" ([source](https://news.ycombinator.com/item?id=48690344)) "you will only really pay a price during active times and during times with low activity you will pay almost nothing" ([source](https://news.ycombinator.com/item?id=47976383)) "I have predictable pricing, and my sites on railway are fast so much faster" ([source](https://news.ycombinator.com/item?id=46805795)) - Responsive, open communication (3 comments): "I also want to commend you and other Railway staff on your communication. It's been clear and open." ([source](https://news.ycombinator.com/item?id=46986249)) "Railway has consistently been responsive and actually understands the problem you're describing." ([source](https://news.ycombinator.com/item?id=46979828)) "Here, they are taking at least some responsibility. Props to them on improving." ([source](https://news.ycombinator.com/item?id=48212384)) - Reliable for production apps (2 comments): "I have run a production Next.js SaaS on Railway for years with no issues." ([source](https://news.ycombinator.com/item?id=46652550)) "These days Railway is my go-to for hosting "throw-away" projects." ([source](https://news.ycombinator.com/item?id=46762581)) ## What people warn about - Outages and deployment failures (5 comments): "I'm a new customer and have been falling in love with Railway over the last 2 weeks, but this is quite the wake up call." ([source](https://news.ycombinator.com/item?id=48201675)) "As a new customer of about 2 weeks, it was a lovely run with Railway until this afternoon!" ([source](https://news.ycombinator.com/item?id=48201659)) "I am a big fan of Railway but have really struggled with the amount of issues recently." ([source](https://news.ycombinator.com/item?id=46977665)) - Weak API key permission controls (3 comments): "ideally these keys should be scoped, and maybe the UI should give more warnings when creating that type of key" ([source](https://news.ycombinator.com/item?id=47918193)) "criticizing the lack of ability to set more granular permissions is valid" ([source](https://news.ycombinator.com/item?id=47917285)) "making an API key that allows for all operations to happen from a single key without giving clear warnings on privileges" ([source](https://news.ycombinator.com/item?id=47924116)) - Security and secrets incidents (4 comments): "Invisible SIGTERMS to random containers we find out about the hard way seems the exact opposite of sensible handling of supposedly questionable clients." ([source](https://news.ycombinator.com/item?id=46978733)) "Railway should have caught this in staging - the fact that it made it to production suggests they don't have proper testing for permissioning logic" ([source](https://news.ycombinator.com/item?id=47615483)) "Seen multiple folks in the Railway Discord confirming that their secrets stored in Railway have been used by third parties" ([source](https://news.ycombinator.com/item?id=50188398)) - Poor incident response transparency (3 comments): "you cant shut off the alerts, because its apparently deployed SOMEWHERE but good luck finding how to access it" ([source](https://news.ycombinator.com/item?id=48201846)) "Railway's response was evasive, underplayed the incident, and did not reflect the severity of this failure." ([source](https://news.ycombinator.com/item?id=50206664)) "then once you saw people were using it you decided to milk your bug via the most expensive payment plan." ([source](https://news.ycombinator.com/item?id=46971634)) ## Alternatives hackers recommend - [Heroku](https://hackerapproved.com/p/heroku.md): 82 recommend - [Fly.io](https://hackerapproved.com/p/fly-io.md): 72 recommend - [Render](https://hackerapproved.com/p/render.md): 44 recommend - [Google App Engine](https://hackerapproved.com/p/google-app-engine.md): 11 recommend - [DigitalOcean App Platform](https://hackerapproved.com/p/digitalocean-app-platform.md): 11 recommend ## Where to get it - [Visit the official site](https://railway.com/) ## Cite as Hacker Approved, "Railway", https://hackerapproved.com/p/railway/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).