Railway vs Render
Render is the closest like-for-like move from Railway: web services, workers, cron and Postgres on one dashboard. The real difference is the bill: Render charges a fixed price per instance, Railway meters usage per second.
Pick Render if you want a fixed monthly price per service, five regions including Ohio and Frankfurt, and an official Railway migration guide. Stay on Railway if your services idle most of the day, you move a lot of egress, or you want a longer Postgres recovery window.
Side by side
Railway vs Render at a glance
| Railway | Render | |
|---|---|---|
| Billing | Plan + per-second usage | Workspace plan ($0 Hobby, $25/mo Pro) + fixed price per instance, prorated per second |
| Cheapest always-on service | Hobby $5/mo, includes $5 of usage | Starter $7/mo (512 MB) |
| Free option | 30-day trial ($5 credit), then $1/mo of usage | Free web services sleep after 15 min; free Postgres expires after 30 days |
| 1 CPU, 2 GB RAM | About $40/mo if fully used, less when idle | Standard $25/mo, flat |
| Postgres | One-click template on a volume; backups, PITR (about 4 weeks) and HA available | From $6/mo (256 MB); PITR 3 days on Hobby, 7 days on Pro; HA from $40/mo of compute |
| Persistent storage | Yes: $0.15/GB-month | Disks $0.25/GB-month; a service with a disk cannot scale past one instance |
| Egress | $0.05/GB | 5 GB (Hobby) or 25 GB (Pro) included, then $0.15/GB |
| Regions | 4: California, Virginia, Amsterdam, Singapore | 5: Oregon, Ohio, Virginia, Frankfurt, Singapore |
| Preview environments | Yes: an environment per pull request | Single-service previews on Hobby; full-stack on Pro and up |
| Infrastructure as code | .railway/railway.ts (railway.toml stops working Dec 1, 2026) | render.yaml Blueprints, all plans |
| Autoscaling | Replicas, set per service | Pro workspace and up |
Sources: Render pricing · Render free tier · Render Postgres backups · Render disks · Render bandwidth · Railway pricing · Railway plans · Railway backups · Railway regions. Checked October 22, 2026.
Where Render wins
A bill you can read in advance
A 1 CPU, 2 GB service is $25 a month on Render whatever it does. The same size on Railway costs about $40 if it runs flat out ($20 per vCPU plus $10 per GB of RAM), less if it mostly idles. Busy, steady services are cheaper on Render.
More regions in the US and Europe
Five regions against Railway's four, and the extra two are Ohio and Frankfurt, which matter for latency to US Midwest and Central European users.
A migration path built for Railway users
Render's pricing page links a Railway migration guide and advertises up to $10K in migration credits. Treat the credit as a vendor offer and read the terms.
Where Railway still wins
Idle and spiky services
Railway bills what a service actually uses, so a staging app or an internal tool that sits idle costs cents. On Render the instance price is the same at 0% and 100% CPU.
Egress, disks and recovery window
Railway egress is $0.05/GB against Render's $0.15/GB after the included allowance, volumes are $0.15/GB against $0.25/GB, and Railway's Postgres point-in-time recovery reaches back about four weeks against Render's 7 days on Pro.
Moving from Railway to Render
- Rotate first: copy no secret from Railway as-is. Issue new database passwords and API keys and put only the new values on the new host.
- Recreate each service on Render with a
render.yamlBlueprint, so the setup is in the repo from day one. - Create a paid Render Postgres (free databases expire after 30 days and have no recovery), then
pg_dumpfrom Railway andpg_restoreinto it during a short write freeze. - Point DNS at Render, watch for a day, then delete the Railway services and volumes.
Common questions
Railway vs Render: common questions
Is Render cheaper than Railway?
It depends on load. A 1 CPU, 2 GB service is $25 a month on Render. On Railway the same size costs about $40 a month if it runs at full use and less if it idles, because Railway bills per second of actual usage. Steady, busy services usually come out cheaper on Render; idle ones on Railway.
Does Render have managed Postgres like Railway?
Yes. Paid Render Postgres starts at $6 a month with point-in-time recovery (3 days on Hobby, 7 days on Pro) and optional high availability from $40 a month of compute. Free Render databases expire after 30 days and have no recovery.
Can I move from Railway to Render without downtime?
Close to it. Run both side by side, restore the database into Render with pg_dump and pg_restore during a short write freeze, then switch DNS. Plan a few minutes of read-only time for the database cutover.