Railway Review

Railway fits a backend that sits quiet most of the day, and it is a poor fit when staging is left running. The subscription is a floor on the invoice rather than a ceiling, so a quiet month still costs the plan.

Toolradar data: the hosting and deployment ranking we publish scored 297 products in September 2026. The median cheapest paid plan among the 10 at the top is $5.50/mo, and Railway is outside that ten. The decision is whether a stopped service leaves the invoice.

How we compared: Railway, Render, Fly.io, Northflank, DigitalOcean App Platform, and Heroku, in USD, on September 24, 2026. Nobody paid for a slot. We did not deploy a test app. A frontend with no long-running process belongs on the Vercel review.

Railway is a usage-billed platform for services you deploy from GitHub, a Docker image, the CLI, or a template. Nixpacks can build the image, or you bring a Dockerfile, and build CPU, memory, and image storage are not charged, so a rebuild does not add a line.

The canvas is services rather than dyno types, so Postgres, Redis, MongoDB, and ClickHouse templates are a service plus a volume and the disk line follows that volume. A public URL and a private URL both exist, and only the private one is free to talk to, so the public database hostname is the one that adds a network charge.

Enterprise is a contract, while Hobby and Pro are the self-serve bills you can open without a sales conversation.

You connect a repo and Railway runs a service, and CPU, memory, and disk bill per second while it runs. A stopped service costs nothing, while an idle process that stays up still bills RAM and CPU.

Serverless is the off switch, and it stays off until you enable it, so a quiet app does not sleep on its own. The docs call a service inactive about 5 minutes after the last outbound packet, and sampling means sleep usually lands between 5 and 10 minutes. The toggle hits every replica and starts on the next deploy.

A database pool, Next.js telemetry, NTP, and private-network calls all count as outbound, so any of them keeps the meter running. The metrics graph hides private traffic, so a service can look idle and still stay awake, and the first request after sleep can return a 502. A webhook that does not retry will drop that event.

Five open pull requests can burn the credit five times over, because each preview is another running copy. The private hostname is not egress, and the public database URL is, so database calls belong on the private hostname.

Read the credit before the resource rates, because the Hobby fee and the Pro fee are minimums that wipe the first slice of CPU, memory, disk, and egress. Unused credit dies at the end of the cycle, and a quiet month still costs the subscription, which the plans FAQ states outright, so low usage does not zero the bill.

The pricing page meters resources per second and prints a monthly constant beside each rate, for comparison only. One full gigabyte of RAM for the whole month is the memory row, and that single line spends half the Pro credit before any vCPU time.

A second replica doubles that draw, CPU is its own row, and a full vCPU for the month equals one Pro fee by itself.

Free is a $1 monthly credit, one project, three services, one member, and no custom domain, so it cannot carry a production hostname. The per-service cap is 1 vCPU and the memory on the Free row.

Trial is a one-time credit equal to one Hobby month, with no card, then it expires, and upgrading carries any leftover trial balance onto the paid plan.

Hobby is the solo plan: 50 projects, 50 services, 3 members per project, 2 custom domains, and the volume ceiling in the table. Pro is the team plan: one fee per workspace, a zero seat line, unlimited members, and 20 custom domains.

Logs run 3 days on Free, 7 on Hobby, and 30 on Pro, so a longer history means a higher plan. Rollback of a removed deploy lasts 24 hours on Free, 72 on Hobby, and 120 on Pro.

After you cancel, volume data is deleted in 30 days on Free, 60 on Hobby, and 90 on Pro, so a cancelled volume is not a backup. Invoices under $0.50 are carried forward, and a partial charge can hit mid-cycle. A post-paid card is required, a Hobby fee waiver exists and is automatic, and Railway will not review requests.

SSO and RBAC are tied to committed spend or Enterprise, not to the Pro fee, so the self-serve plan does not include SSO. Business Class Support has no published price, and Enterprise publishes no list price, so neither can be budgeted from the plan fee.

The other hosts in the table sell a size or a region, not a credit. Render's paid instances do not spin down, Fly.io has no workspace fee, and Northflank's sandbox stays awake. App Platform's smallest shared container matches the Hobby sticker, and Heroku's metrics dyno does not add RAM.

Prices below were read on each vendor's pricing page on September 24, 2026.

Railway fits a developer who will turn Serverless on, set a compute cap, and keep databases on the private hostname. Hobby covers a side project under the credit, and Pro is the switch when the volume ceiling or a teammate needs the workspace.

Skip it when the app must stay warm, because a running service bills with no users. Skip it when Postgres should be a named plan: see Postgres hosting, the Neon review, and Supabase if auth ships with the database.

A page-only Next.js app is a closer call on the Vercel review and the serverless platforms roundup. Next.js telemetry is outbound traffic, and it blocks Railway sleep.

For a sized instance, start with the Heroku alternatives and the Heroku review. For a VM you administer, use VPS hosting for developers and the DigitalOcean review.

A box you patch yourself is the self-hosting tools list, a cluster you already operate is the Kubernetes tools decision, and subscribe free for the next credit note.