Render vs Railway: The Same Small App, Step by Step
The Helm7 team · Published 29 September 2026 · Checked 30 September 2026 · 8 min read
Render vs Railway is a comparison people make from feature lists, and the lists agree: both deploy from Git, both run a database next to your app. The difference shows up when you actually build something and read the bill. So we took one small Next.js app with Postgres and walked it through both, step by step, on paper, with each vendor's prices as read on 30 September 2026.
In short
- Render bills a flat workspace plan plus compute you size in advance. Railway bills the CPU and memory you use.
- For one developer and one small app, Render vs Railway is close: about $13.75 against $15.15 in our worked example.
- Add two more developers and Render needs a $25 Pro workspace, while Railway stays at its $20 minimum.
- In Render vs Railway, regions differ: Render has five and cannot move a service between them, and Railway has four and can.
- Free tiers on both are for testing: Render Free Postgres expires after 30 days.
Render vs Railway: the app and the rules
One developer. One Next.js app that talks to Postgres, with 1 GB of data and about 10 GB of outbound traffic a month. It has to run all month, have a custom domain and be rebuilt on every push.
A note on honesty. We did not deploy this twice and time it. The steps below follow each platform's documentation, and the bill is arithmetic on published prices with usage figures we chose and label as assumptions. Redo the sums with your own numbers before you trust ours.
Render vs Railway, step 1: what do you pay before you deploy?
Render charges a plan fee for the workspace, and then compute on top. A Hobby workspace is $0 a month and allows up to 25 services. A Pro workspace is $25 a month with unlimited seats and services, and 25 GB of bandwidth instead of 5. Railway has a Hobby plan at $5 minimum usage and a Pro plan at $20 minimum usage, each including the same amount of credit.
“Render charges for three things: your workspace plan (flat subscription), metered features like bandwidth (usage-based), and compute for your applications (usage-based).”
The difference is what you choose in advance. On Render you pick an instance size and pay for it whether it is busy or idle, prorated to the second, so a staging copy you switch off after two days costs two days. On Railway you pick nothing and it meters the CPU and memory your services really use, at about $20 per vCPU-month and $10 per GB-month. Neither idea is better in general. Fixed sizes are easy to budget, and metering rewards an app that spends most of its day doing very little.
Render vs Railway, step 2: how does the app get built?
- 1Connect the repoBoth link a Git provider and rebuild on each push.
- 2Render: choose the settingsYou give it a language, a build command, a start command and a compute plan. The app must listen on 0.0.0.0, and Render passes the port in a PORT variable, 10000 by default.
- 3Railway: accept the defaultsIt builds with Railpack, or Nixpacks, with no configuration. Its Next.js guide asks for standalone output and a start script that runs node .next/standalone/server.js.
- 4Pick the sizeRender's Starter is $7 a month for 512 MB and 0.5 CPU, and Standard is $25 for 2 GB and 1 CPU. On Railway there is no size to pick.
In the Render vs Railway build test, Railway is the quicker start. Render asks more questions and, in return, tells you what the bill will be before the first build finishes.
Step 3: how does each one run Postgres?
Render Postgres is a managed database with its own plans. The smallest paid plan is $6 a month for 256 MB of RAM and 100 connections, and the next is $19 for 1 GB. Each includes 1 GB of storage, and extra storage is $0.30 per GB. Point-in-time recovery reaches back 3 days on a Hobby workspace and 7 days on Pro.
On Railway you add a Postgres service to the project. It runs Railway's SSL-enabled image, built on the official Postgres image. It is private by default, gives you a DATABASE_URL, and is billed as ordinary CPU, memory and volume. Volumes are $0.15 per GB a month. Railway has a Backups feature, but you set it up.
Render's database is the more finished product, with plan tiers, a recovery window and a fixed price. Railway's is the simpler one, which is one more service that behaves like the rest.
Step 4: what happens when you write it down as code?
Render calls its files Blueprints. One YAML file in the repository describes services and databases, and pushing a change redeploys what it affects. Infrastructure as code is listed on the pricing page among the workspace features.
“Config as Code is deprecated. Prefer Infrastructure as Code. Existing files keep working for legacy services until 2026-12-01; migrate with the guide in Infrastructure as Code.”
Railway's older config file could set build and deploy options for one deployment, but it could not create services. It is now on its way out, so if you want your setup in a file on Railway, read the newer infrastructure guide first. Render's Blueprints are the more settled answer today.
Render vs Railway, step 5: where can it run?
Render offers five regions: Oregon, Ohio, Virginia, Frankfurt and Singapore. Railway offers four: California, Virginia, Amsterdam and Singapore. Frankfurt and Amsterdam are the two European choices, and each vendor has exactly one.
The rules for moving differ. Render says it does not currently support changing the region of an existing service or database, so a move means building a second one and migrating. Railway says a service's region can be changed at any time, with no downtime unless a volume is attached.
What does each free tier really give you?
- Render Free web services get 750 instance hours a month, spin down after 15 minutes without traffic, and take about a minute to wake. Their local files vanish on every restart.
- Render Free Postgres expires 30 days after creation. It is for trying things, not for keeping data.
- Railway offers a 30-day trial with $5 of credit, then a Free plan with $1 a month, up to 1 vCPU and 0.5 GB of RAM per service.
Neither is a place for a real app. Use them to check that the build works, then move to a paid plan before anyone depends on it, because a sleeping web service and a database with an expiry date are both fine for a demo and both bad for a customer.
The bill: what the same app costs on each
Assumptions for the worked example. The web service averages 0.25 vCPU and 0.5 GB of memory over the month. The database averages 0.1 vCPU and 0.25 GB, with a 1 GB volume. Outbound traffic is 10 GB. Railway usage is then 0.25 x $20 + 0.5 x $10 + 0.1 x $20 + 0.25 x $10 + 1 x $0.15 + 10 x $0.05 = $5.00 + $5.00 + $2.00 + $2.50 + $0.15 + $0.50 = $15.15.
| Scenario | Render | Railway |
|---|---|---|
| A. One developer, the app above | $13.75: Starter $7, 256 MB database $6, 5 GB extra traffic at $0.15 | $15.15: usage above the $5 Hobby credit |
| B. The app needs 1.5 GB of memory on average | $31.75: Standard $25, database $6, traffic $0.75 | $25.15: memory adds 1 x $10 |
| C. Three developers share the account | $38.00: Pro workspace $25, Starter $7, database $6 | $20.00: Pro minimum, usage $15.15 inside its $20 credit |
In scenario A, Render is $1.40 cheaper. A 512 MB instance is a tight fit for a Next.js app that averages 0.5 GB, so treat that number as optimistic, and the real comparison may be scenario B. Scenario C is the plan-fee effect. Render's Pro workspace is where unlimited seats begin, and it adds $25. On Railway the same three people cost nothing extra, because its Pro plan includes unlimited workspace seats. The lesson from this Render vs Railway sum is that team size moves the bill as much as the app does.
Render vs Railway: which one for this app?
- Choose Render if you want a fixed price, a managed database with a recovery window, and Blueprints you can trust in a repository. It is also the calmer choice for a solo developer.
- Choose Railway if your usage is uneven, you have several people, or you want one project with services of different kinds and a quick start.
- Look wider if your users are in Europe and you want app and database on one bill. Helm7 runs in Falkenstein and Helsinki only, has no US region, and is newer than both.
For the wider field, see our Railway comparison, our Render comparison, and how to host a Next.js app if you are still choosing a shape. If you are weighing Railway against Vercel as well, Vercel vs Railway covers seats and duration limits.
Common questions
Is Render cheaper than Railway in a Render vs Railway comparison?
For one developer with a steady small app it can be, because Render's Starter instance and smallest database total $13 a month. With several developers or a bigger app the answer changes, so run the sums for your own usage.
What are Render Blueprints?
Blueprints are Render's infrastructure as code. A YAML file in your repository describes services and databases, and Render redeploys the affected ones when you push a change.
Does Railway have a free plan?
It offers a 30-day trial with $5 of credit, then a Free plan with $1 a month of credit and up to 1 vCPU and 0.5 GB of RAM per service.
Which is better for Postgres, Render or Railway?
Render sells Postgres as a managed product with plans and a recovery window of 3 to 7 days. Railway runs it as another service in your project. Render is the more finished option, and Railway is simpler.
Can I move a Render service to another region?
Not in place. Render says it does not currently support changing the region of an existing service or database, so you create a new one and migrate. Railway lets you change a service's region at any time.