Render vs Railway Pricing: Same App, Two Bills

Render vs Railway comes down to one billing difference. Render charges for the size of each instance while it runs. Railway charges for the memory and CPU your services actually use, by the minute. Price the same small SaaS on both and, at the kind of load most early products have, Railway is about a third of the Render bill. Run everything flat out all day and they end up close.

All prices below are from Render’s pricing page and Railway’s plans page, both checked on October 27, 2026.

The app we priced

A hypothetical but very ordinary stack: a Node API, a background worker for emails and webhooks, Postgres with 20 GB of data, a small Redis for queues, 100 GB of traffic a month, and about 600 build minutes. A team of a few people, so the paid plan on both sides.

On Render that is:

Line	Render Pro
Workspace plan	$25.00
Web service, 1 CPU / 2 GB	$25.00
Worker, 0.5 CPU / 512 MB	$7.00
Postgres, 0.5 CPU / 1 GB	$19.00
Postgres storage, 20 GB at $0.30	$6.00
Key Value, 256 MB	$10.00
Bandwidth, 75 GB over the 25 GB included, at $0.15	$11.25
Build minutes (1,000 included)	$0.00
Total	$103.25

On Railway the same services are billed on what they use. We assumed they sit at half their memory and 15% of their CPU on average, which is generous for an app with a few hundred users. That’s 1.875 GB of RAM at $10 per GB-month ($18.75), 0.3 vCPU at $20 per vCPU-month ($6.00), 20 GB of volume at $0.15 ($3.00) and 100 GB of egress at $0.05 ($5.00). Usage comes to $32.75. Railway’s $20 Pro fee counts toward usage, so the bill is $32.75, not $52.75.

Same app. $103.25 against $32.75.

Where the $70 goes

Three things, and only one of them is the billing model.

Idle capacity. The 1 CPU, 2 GB instance costs $25 whether the API uses 2 GB or 600 MB. Render has no smaller size between 512 MB ($7) and 2 GB ($25), so an app that needs 700 MB pays for 2 GB. On Railway that same service would cost about $7 in memory plus whatever CPU it burns.

The workspace fee. Render Pro is $25 a month on top of compute. Railway Pro is $20, but it’s a floor, not an add-on: it’s spent on your usage first.

Bandwidth. Render includes 25 GB on Pro and then charges $0.15 per GB. Railway charges $0.05 per GB from the first byte. At 100 GB the difference is only about $6, but at 1 TB it’s $146 against $50. If your app serves user uploads straight from the web service, that line grows faster than anything else on Render.

When Render comes out ahead

Turn the usage up to 100%, every service pinned at its full size all month, and Railway’s usage rises to $85.50. Render Pro is still $103.25 because of the workspace fee and bandwidth, but on Render’s Hobby workspace (no fee, 5 GB of bandwidth, 500 build minutes) the same stack is $81.75, and that is cheaper than Railway’s $85.50. Steady, heavy workloads that really use their instances are where per-size pricing stops being a penalty.

Predictability matters too. A Render bill for the stack above is $103.25 every month unless you change something. A Railway bill moves with memory. A slow leak that takes the API from 1 GB to 3 GB adds $20 a month by the time it gets there, with no deploy and no warning. More on that in Railway pricing.

There’s also what you get for the database money. Render’s paid Postgres instances include point-in-time recovery (a 3-day window on Hobby, 7 days on Pro), and the storage you add can’t be shrunk later, per Render’s Postgres docs. On Railway, Postgres is a service like any other, running on a volume. Before you treat the two database lines as equal, check what backups you’d actually have.

What we’d do

For an early product with uneven traffic, Railway is cheaper, often by more than half. For a workload that keeps its instances busy, Render’s Hobby workspace is competitive and the bill never surprises you. Either way, the biggest savings on both platforms usually aren’t from switching. They come from an instance two sizes too big, a staging environment that never sleeps, and images served from the app server instead of object storage.

Put your own sizes into the Render pricing calculator. It prices the same stack on Railway next to it, with the utilisation you choose.