Railway vs Render: which is cheaper in 2026?

TL;DR: The same app, a web service, a background worker, Postgres and Redis, costs about $20 a month on Railway and $38 on Render when it's small, $104 against $197 at medium size, and $344 against $806 when it's busy. Railway is roughly half the price at every size. One rented Hetzner server runs the same four services for $7, $19 and $36, with Ployz free on top.

• Pick Railway if your services are mostly idle, you serve a lot of traffic, or you want replicas in more than one region.
• Pick Render if you want the same bill every month, your workers or database use their full plan, or you want Postgres point-in-time recovery with no setup.
• Pick Render's free tier if you need a free web service for a demo.
• Pick your own server with Ployz, which I build, if your stack is past the smallest size and you'd rather pay $19 than $104 or $197.

Railway and Render are both platforms as a service: you push code, they build and run it. The difference is the bill. Railway charges for the CPU and memory your services use, minute by minute. Render charges a fixed price for the size of box each service gets, whether you use it or not.

Most "Railway vs Render" pages stop at the starting prices, $5 against $7. That number tells you nothing, because the two platforms bill for different things. I paid Railway $500+ a month at one point, most of it for a busy database, so I've felt how usage billing grows. Today one €80 dedicated server runs more than I ever ran there.

What Railway and Render cost

Each app is a web service, a worker, Postgres and Redis; the presets below spell out each size. Pick the one closest to yours, or press "Customize" and set your own. Railway bills the CPU and memory a service uses on average, so the calculator assumes an average for each size and shows it above the totals.

Railway is only cheaper because real apps sit well below the size of box they'd need on Render. A service that runs flat out all month costs about the same on both, and a large Postgres can be cheaper on Render. How they bill shows where that line is.

Railway, Render or your own server: the decision

Start with how your services behave, then check the price. This is the whole decision on one screen; the sections below show the maths behind each row.

Railway suits a typical web app. Set a usage alert, because the bill follows your growth.

Render suits a team that wants a predictable bill. A team of any size pays the same $25 workspace fee.

Your own server suits a stack past the smallest size, or a database of more than a few gigabytes.

How do Railway and Render bill differently?

Railway is usage billing: $20 per vCPU and $10 per GB of RAM per month, metered per second, plus $0.05 per GB of egress and $0.15 per GB-month of volume storage. The $5 Hobby or $20 Pro plan fee is credit: you pay the larger of the fee and your usage. Render is fixed billing: a workspace fee ($0, $25 or $499) plus a flat monthly price for each service's plan, prorated by the second.

Railway's rates are on its pricing page and pricing docs: "If your total resource usage at the end of your billing period is $5 or less, you will not be charged for resource usage." Railway is also clear that idle isn't free: "you pay for allocated resources, not traffic," and "a server running idle still uses memory to stay loaded" (understanding your bill).

Render's pricing FAQ says it charges for "your workspace plan (flat subscription), metered features like bandwidth (usage-based), and compute for your applications." Compute plans are per service, so spare memory in your worker can't be lent to your database.

Here's what each Render plan would cost on Railway if the service used all of it, all month:

A Render CPU and a Railway vCPU aren't guaranteed to be the same thing, so read this as a guide. Two things stand out:

• Small Render plans are cheaper if you keep them busy. That's rare for a web app but normal for a worker that chews through a queue.
• A large Postgres that fills its memory is cheaper on Render. Postgres does that on purpose. That was exactly my Railway problem: a database that grew and used every gigabyte it could.

The shape of the bill differs too. Render's bill is the same every month until you change a plan or pass your included bandwidth. Railway's grows with your app, with no ceiling unless you set one. Railway lets you set a hard limit (minimum $10), but at that limit "all your workloads will be taken offline" (usage limits).

What does the same app cost on each, line by line?

On Railway, memory is the biggest line every time. On Render, compute is the biggest line. On the large app, bandwidth comes second: 2 TB costs $296 on Render and $100 on Railway.

The three stacks, all in one region:

• Small: one person. Smallest paid plan for each service, 5 GB of Postgres data, 256 MB Redis, 50 GB of traffic.
• Medium: two people deploying. 1c-2g web and worker, 1c-4g Postgres with 20 GB of data, 1 GB Redis, 300 GB of traffic.
• Large: two 2c-4g web instances, a 2c-4g worker, 2c-8g Postgres with 100 GB of data, 5 GB Redis, 2 TB of traffic.

For Railway I assumed each service averages well under its Render size, as most do. The calculator adds them up in its usage line. For example, I assume 0.5 vCPU and 1 GB for a 1c-2g web service, and 1.2 vCPU and 7 GB for a 2c-8g Postgres. These are assumptions, not measurements. Railway Hobby allows a 5 GB volume and 3 members per project, so past either the bill uses Pro.

Render prices come from its pricing page: web and worker plans from $7, Postgres from $6 plus $0.30 per GB of storage, Key Value at $10 for 256 MB, $20 for 1 GB and $100 for 5 GB. Bandwidth past the included 5 GB (Hobby) or 25 GB (Pro) is $0.15 per GB (outbound bandwidth docs). My Render pricing breakdown and Railway pricing breakdown go deeper on each rate card.

Postgres is the line to watch on Railway. In the large app it's $109 of $344, and it grows as the data grows, because Postgres caches as much as memory allows.

Which free tier is better, Railway or Render?

Render's, for a demo you want to leave running. Neither runs an always-on app with a database for free.

• Render gives you a free web service that spins down after 15 minutes idle, a free Postgres that expires after 30 days, and a free in-memory Key Value.
• Railway gives a one-time $5 credit for 30 days, then $1 of usage a month, which buys about 100 MB of RAM.

Railway's sleep feature puts a service to sleep "somewhere between 5 and 10 minutes after its last outbound traffic," and "the first request sent to a slept service may return a 502 Bad Gateway response" (Serverless docs). An open database connection keeps a service awake, so sleep doesn't help an app with a database. I wrote up the Render side, including the cold starts, in Render's free tier, tested against its limits.

How do previews, regions, private networking and logs compare?

Both platforms have pull-request preview environments, private networking and built-in logs. Railway has one-click MySQL and MongoDB as well as Postgres and Redis; Render's databases are Postgres and Key Value. Railway has four regions and can place replicas in more than one. Render has five regions, but each service lives in one, and its private network stops at the region. Railway keeps logs 30 days on Pro; Render keeps 14. Render's full-stack previews need the $25 Pro workspace.

The regions point is the one people miss. Render's docs say "services in different regions can't communicate directly over a private network." You can't move a service to another region; you create a new one. Railway's own comparison page says replicas "can be placed in different geographical locations" with traffic routed to the nearest region.

That same Railway page also says Render "charges per team member seat." That's out of date. Since 1 August 2026, Render's Pro is $25 flat with unlimited seats, and bandwidth is billed per GB instead of in 100 GB blocks (Render blog). For a team of five, Render's workspace fee is now close to Railway's.

What limits does each plan have?

Railway Hobby allows 50 services, 6 replicas, a 5 GB volume and 2 custom domains. Railway Pro raises that to 100 services, 42 replicas, 1 TB volumes and 20 domains. Render Hobby allows 25 services and 2 custom domains with 1 seat. Render Pro has unlimited services and seats and 15 domains, with extra domains at $0.25 a month each.

Sources: Railway pricing and Render pricing. The 5 GB volume cap is what pushes a growing Railway database to Pro. On Render, Postgres storage grows on any plan at $0.30 per GB.

What about Railway vs Fly.io?

Fly.io sits between the two. Like Railway it's billed by the second, but like Render you pick a fixed Machine size. A shared-cpu-4x Machine with 1 GB is $8.78 a month. Egress in North America and Europe is $0.02 per GB. Fly's Managed Postgres starts at $38 for a shared 1 GB instance. Railway is simpler for a stack of services; Fly is cheaper on traffic.

From Fly's pricing page, Ashburn prices:

• shared-cpu-1x with 256 MB is $2.19, and extra RAM is $6 per GB a month;
• a performance-1x with 2 GB is $33;
• a dedicated IPv4 is $2 a month;
• Managed Postgres is $38 (shared-2x, 1 GB) or $72 (2 GB), plus $0.28 per GB of storage.

On Railway, a database averaging 1 GB of RAM and a tenth of a vCPU costs about $12. So for a small database, Railway is cheaper. For an app that serves a lot of traffic, Fly's egress at $0.02 per GB is less than half Railway's.

Is either cheaper than your own server?

No. The small stack costs $20 on Railway, $38 on Render and $7 on a Hetzner CX23 with Ployz, so the gap is smallest there. At medium size it's $104 and $197 against $19. At large it's $344 and $806 against $36. Ployz is free, custom domains included, so the server is the whole bill. In exchange you run the machine.

Hetzner prices are after its 15 June 2026 adjustment, Germany and Finland, in USD before VAT. I sized each server to the RAM Render allocates (1.5, 9 and 25 GB), with disk at twice the database size. That's generous to both platforms: on one machine the four services share memory, and the large app's 2 TB of traffic is a tenth of what Hetzner includes. Netcup is the provider I'd look at first. Its VPS 1000 (4 vCPU, 8 GB, 128 GB) is €14.50 incl. VAT, with a US datacenter in Manassas.

What the server price leaves out:

For the wider picture of where platforms add fees, see the real cost of PaaS pricing.

Where Ployz fits

I build Ployz, which runs this stack on a server you rent. Push to GitHub, and it builds on your server and deploys with zero downtime once you set a health check. Every pull request gets a preview environment. Postgres and Redis are one click each, with Railway-style variables like ${{ postgres.DATABASE_URL }}.

ployz up --server root@your-server

That installs Ployz on a Linux server, builds the current directory and gives it an HTTPS address. Your servers talk over encrypted WireGuard, and a service can run up to 50 replicas.

For backups, Ployz mirrors a database's volume onto another of your servers and syncs it when you ask. If the first server dies, restore from the mirror, or move the database there with seconds of downtime.

What it doesn't do yet:

• No team invites yet. One person per organization.

Ployz is free on your own servers, custom domains included. Start free on your own server.

FAQ

Is Railway cheaper than Render?

Usually. For a web service, worker, Postgres and Redis, Railway costs about half of Render: $20 against $38 small, $104 against $197 medium and $344 against $806 busy. Services that run flat out cost about the same on both.

Why is Render more expensive than Railway?

Render charges for the full plan size of each service. Railway charges for average use. Most apps use far less than their plan, and Render's bandwidth is $0.15 per GB against Railway's $0.05.

Does Render still charge per seat?

No. Since 1 August 2026, Render Pro is $25 a month flat with unlimited seats. Railway's comparison page still says otherwise.

Which is better for Postgres, Railway or Render?

Render, for a large database that fills its memory, and for point-in-time recovery that's on without setup. Railway, for a small database that averages well below its size, or for a longer recovery window: its opt-in point-in-time recovery keeps about 4 weeks for Postgres, against Render's 7 days.

Does Render support MySQL or MongoDB?

Not as managed databases. Render's databases are Postgres and Key Value (Redis-compatible). Railway has one-click templates for Postgres, MySQL, Redis and MongoDB.

Which has the better free tier?

Render, for a demo. Its free web service spins down after 15 minutes idle, and its free Postgres expires after 30 days. Railway gives $1 of usage a month after a $5 trial.

How I checked

Prices were checked on 8 October 2026 on railway.com/pricing, Railway's pricing docs, render.com/pricing, fly.io/pricing, Hetzner's price list and netcup's VPS page. All bill in USD before tax. I didn't deploy this stack on both platforms. The bills are built from each official rate card, with the usage assumptions spelled out so you can swap in your own. I build Ployz, which competes with both, so I'm biased; the maths is all here to check.

Run your web service, worker, Postgres and Redis on your own server with Ployz, free: get started.