Railway Reviews

They chose Railway for its managed setup and infrastructure visualizer at a price close to a VPS, and say it is far cheaper than AWS for them, despite its reliability issues.

Railway is insanely fast to deploy with a nice UI, but security and reliability let them down; switching permanently.

Started on Railway because it was easy and cheap, but two years of outages and the breach handling are pushing them off.

Liked not thinking about infrastructure on Railway, but recent downtime is a blocker and they are looking at self-hosting.

Railway has had flaky uptime in recent months though the developer experience is nice.

Railway is cheap and easy but a couple of major outages took hours to resolve; moving off to AWS.

As a solo dev they find Railway makes deployment and backend previews easy with little setup, and call it a good experience so far despite the outage.

Loved the Railway developer experience over two years but left for a self-hosted VPS because of major outages every two to three months, sometimes six hours or more.

Runs a SaaS on Railway's $5 plan (nginx, FastAPI, Postgres); shipped in days, though RAM-heavy services raise costs.

Uses Railway for a relatively large side project turning into a business, finds it awesome after trying Azure, AWS, Netlify and Vercel, and says it gives more time to build the application.

Has hosted sites on Railway for years and calls it the most cost-effective option with world-class developer experience and amazing support.

Runs frontend, backend, Kafka and SQL on one Railway project for about 3.50 a month with 270k API transactions a day.

Liked Railway but the env-var breach spooked them into moving small projects to EC2.

Railway handles Node and Postgres with zero configuration headache and its built-in cron jobs work flawlessly.

Using Railway on a project for a while with no complaints; simple setup and pay for what you use.

They like Railway's development tooling and use its CLI a lot to trigger deployments on their staging environment.

Using Railway and likes it, but the free hobby tier is gone and $5/month is steep for early stages.

Deploys most of their Next.js apps through Railway, finding it simple and straightforward with auto deploy on git push.

Loves Railway as a backend PaaS: intuitive, low cost, good for North American users.

Self-hosting with Coolify was hard to deploy to, and Railway is showing to be easier.

Used Railway for a backend and found it great, avoiding server upkeep and security worries compared with building a DigitalOcean VPS from scratch.

Has found Railway to be very good for deploying apps.

On Railway they easily created a staging environment duplicating production, which worked great.

Solo founder who uses Railway for all infrastructure with templates for quick deployment.

Hosts a Next.js blog and app with prod and stage Postgres on Railway for about 5 dollars a month, with 7-day logs, templates and cron backups, and calls the developer experience awesome.

Loves Railway because it has none of the edge fussiness or function size limits of Vercel; 5 dollars goes a long way and they do not arbitrarily limit you.

They use Railway for small projects and describe it as one of the simplest infrastructure platforms they have used.

Moved a backend from Heroku to Railway; $5 monthly credit has covered it for 6+ months with responsive Discord support.

Tried DigitalOcean, Vultr, Render and Railway and found Railway noticeably faster to load with the same code and easy to set up.

Hosts both PocketBase and a SvelteKit app on Railway using templates and GitHub auto deploys, calling it super simple to set up and a pleasure to use.

Compared Render, Fly.io and Railway for a CRUD app: Railway had the best developer experience and deployed in minutes, but only a US region.

Found Railway when Heroku ended its free tier and says it is great, easy to use and navigate; most projects run there and they would not switch even now that they pay.

They host a side project and a couple of services on Railway for under $6 and find it pretty easy.

Their team uses Railway and likes the neat UI and the easy deployment of extra services such as databases and Redis.

Switched from Netlify to Railway in under 10 minutes including a custom domain, with no more task timeouts and a buttery smooth experience.

They have been running their app on Railway, which deploys from their chosen GitHub branch and lets them add services like a Python API or Redis cache.

Recommends Railway with Node.js server and databases in one place, usage-based pricing and easy Next.js deploys.

Finds Railway super easy for deploying Next.js and will continue using it.

Railway's $5 credit runs a Strapi backend for a small site and its UX and integrations beat Heroku and DigitalOcean.

Very happy with Railway since leaving Heroku.