Render vs Railway in 2026: a 512 MB app costs $7.75 against $7.50

One web service, 512 MB of RAM, modest traffic: that is the shape of most side projects, and pricing it on both platforms produces totals within 25 cents of each other. Render sells a fixed 0.5 CPU / 512 MB instance for $7 a month. Railway sells seconds of memory and CPU against a $5 minimum, which for 512 MB works out to about $5.00 of memory plus whatever CPU the app actually uses. Priced at 10 GB of monthly egress and an assumed 0.1 vCPU average, Render comes to $7.75 and Railway to $7.50.

The same app, both invoices

The 0.1 vCPU figure is an assumption, not a published number, because Railway bills measured CPU and Render does not measure it at all. That single assumption is what decides which platform is cheaper, and it is worth stating plainly rather than hiding inside a total.

What the 25-cent gap actually means

Render's price is a ceiling and Railway's is a forecast. Paying $7 on Render buys 0.5 CPU whether the app uses it or not, which is comfortable for a build step or a burst of image resizing and wasteful for a service that answers four requests an hour. Railway charges for the CPU that actually ran, so a nearly idle app pays close to the $5 memory floor — and a busy one pays more than Render would have charged.

The crossover is easy to locate. Railway's bill is $5.00 of memory plus $20.01 per vCPU-month plus egress, so against Render's $7.75 the CPU budget is $2.25, or about 0.11 vCPU averaged across the month (calculated 2026-10-25). Below that, Railway wins; above it, Render's flat rate is the better deal.

Bandwidth is the asymmetric line. Render includes 5 GB and charges $0.15 per GB after it, while Railway charges $0.05 per GB from the first byte but includes $5 of credit that absorbs 100 GB. At 100 GB of monthly egress the totals are about $12.00 on Railway and $21.25 on Render, which is a 1.8-times gap created entirely by the overage rate (calculated 2026-10-25).

How we measured it

Both pricing pages were fetched on 2026-10-25 and the metered rates were converted to monthly figures by multiplying per-second prices by 2,592,000 seconds. No service was deployed on either platform and no invoice was compared, so the totals here are arithmetic on published rates plus one clearly labelled CPU assumption. Render's flat price and Railway's rates both come straight from the vendors' own tables.

What changes in practice

Render's minimum is per workspace but its compute is per service, so the second 512 MB service adds another $7 rather than fitting inside the first invoice. Railway's minimum is per workspace in a different sense: two 512 MB services bill $10.01 of memory, which already exceeds the $5 floor, so the floor stops protecting you as soon as there are two services.

Storage is where the two diverge quietly. Render's persistent disks cost $0.25 per GB per month, while Railway's volumes bill at $0.00000006 per GB-second, about $0.16 per GB per month. A 20 GB volume is $5.00 on Render and about $3.12 on Railway, which is larger than the compute difference at these sizes (calculated 2026-10-25).

Neither platform charges for a build that nobody triggers, but both charge for the app sitting there. That makes deleting staging environments the highest-leverage cost control on either one, and on Railway it is the only thing standing between a forgotten service and a $5 memory charge every month.

Bottom line

Choose Render at $7.75 if you want a number that does not move and a CPU allowance you never have to watch, or Railway at $7.50 if traffic is heavy or the app is idle most of the day. If the app genuinely idles, the honest budget option is neither: a $4 DigitalOcean Droplet beats both, at the cost of running the server yourself (calculated 2026-10-25).