Free calculator
Render pricing calculator
Pick the instance sizes you run on Render and get the monthly bill line by line: workspace plan, web services, a worker, Postgres with its storage, Key Value, disks, bandwidth and build minutes. Then see what the same services would cost on Railway, which bills what they use instead of their size.
Estimated monthly Render bill
$0
Render prices from render.com/pricing, checked 2026-10-27: each instance is billed for its size while it runs (prorated by the second), Postgres storage $0.30 per GB, persistent disks $0.25 per GB, bandwidth above the plan's allowance $0.15 per GB, build minutes above the allowance $5 per 1,000. Not included: Workflows, cron job minutes, Scale and Enterprise plans, dedicated IPs, private links, read replicas. Railway prices from docs.railway.com/pricing/plans, checked 2026-10-15 and again 2026-10-27: RAM $10 per GB-month and CPU $20 per vCPU-month of actual use, volumes $0.15 per GB, egress $0.05 per GB, Hobby $5 or Pro $20 counted toward usage. The Railway figure assumes each service uses the share of its Render size you enter above.
Why the instance line grows
Render charges for the box. A web service on the 1 CPU, 2 GB instance costs $25 a month whether it serves a million requests or sits at 300 MB of memory doing nothing. That makes the bill easy to predict and easy to overpay: most small apps are sized for their worst day and billed for it every day.
The jumps are steep, too. Going from 2 GB to 4 GB of memory for a web service is not a small step, it is $25 to $85, because the next size up also doubles the CPU. If memory was all you were short of, you are now paying for a second CPU that may sit idle all month.
Postgres has the same shape, plus storage at $0.30 per GB that only goes one way: Render lets you grow a database's disk, not shrink it. Old logs and events tables are the usual reason it keeps growing.
Bandwidth is the line people forget. Hobby includes 5 GB and Pro 25 GB, then it is $0.15 per GB, three times Railway's egress price. An app that serves its own images and uploads instead of putting them behind a CDN or object storage pays for every byte here.
The Railway column is not a promise. It is what the same services would cost if they used the share of each instance you entered, on Railway's per-minute rates. When your services run near full size all day, the two come out close; when they mostly idle, Railway is usually cheaper. We go through a full worked example in Render vs Railway pricing, and the Railway side on its own in the Railway pricing calculator.
If your Render bill is bigger than this page says it should be, send us the bill. Oversized instances and bandwidth that belongs on a CDN are the first two things we check.