TL;DR: An always-on web app with Postgres costs about $14 a month on Railway when it's small, $62 when it's medium and $218 when it's busy. Railway bills the RAM and CPU your services hold while they run, so the database drives the bill as it grows.
- The $5 Hobby plan covers about half a gigabyte of RAM running all month, and nothing else.
- Free is a one-time $5 trial, then $1 a month, which isn't enough for an always-on app with a database.
- Pro is $20 per workspace, not per seat. It doesn't lower the rates; it raises the credit and the limits.
- Stay on Railway if your app is small and quiet. Under about $7 of usage it's cheaper than the smallest server.
- Move to your own server with Ployz if your usage is past $7 a month. The same apps cost $7 to $19 on one rented server, and your coding agent runs it.
Railway pricing is usage-based. You pay a monthly plan fee that doubles as usage credit, then $20 per vCPU-month, $10 per GB-month of RAM, $0.05 per GB of egress and $0.15 per GB-month of volume storage for everything past it.
| Plan | Monthly fee | Usage included | Pick it if |
|---|---|---|---|
| Free | $0 | $5 once for 30 days with no card, then $1 a month | You're trying Railway out |
| Hobby | $5 | $5 a month | Small apps, volumes up to 5 GB, up to 3 members |
| Pro | $20 per workspace, unlimited seats | $20 a month | A team, a volume past 5 GB, or usage past $20 anyway |
| Enterprise | Custom | Custom | You need limits set by agreement |
Fees and credits are from Railway's pricing page, checked again on 8 October 2026.
What would your app cost on Railway?
Pick the app closest to yours: small, medium and busy are the three worked bills below, and "Fits in $5" is the Hobby example. For your real numbers, open Railway's Metrics tab, add up the average memory and CPU of every service (each replica, worker and Redis included), and set the totals under Customize.
- RAM
- $10.00
- CPU
- $3.00
- Egress
- $1.00
- Volume
- $0.15
- Railway usage
- $14.15
- Server that fits
- Hetzner CX23 or Netcup VPS 500
- Railway Hobby (Pro past 5 GB of volume)$14/mo
$10/GB-month RAM, $20/vCPU-month, $0.05/GB egress, $0.15/GB-month volume. The plan fee is credit, so you pay the larger of the fee and your usage. Count each replica, worker and Redis in the RAM and CPU totals.
- Railway Pro$20/mo
$20 a month per workspace, any number of seats, with $20 of usage included. Same rates.
- Your own server + Ployz (Hetzner, EU)$7/mo
Smallest Hetzner CX23 to CX53 ($6.49 to $34.99) with room to spare, about $0.60 IPv4 each, 20 TB traffic. Ployz is free on any number of servers. Germany and Finland only.
- Your own server + Ployz (Netcup, US or EU)$9/mo
Smallest Netcup VPS 500 to 8000 (€8.26 to €67.11 incl. VAT, 12-month term, at about $1.13 a euro), traffic included. Ployz is free on any number of servers.
Staging and PR environments surprise people. Each one copies every service, database included, and bills for as long as it runs, so that slider multiplies RAM, CPU and the volume. Replicas do the same to one service: each is a separate running copy holding its own memory.
How does Railway pricing work?
Railway charges a monthly plan fee, and that fee is also your usage credit. Hobby is $5 a month and includes $5 of usage; Pro is $20 and includes $20. If your usage stays under the credit, you pay the fee. If it goes over, you pay the usage.
The docs give the example: "If your resource usage is $7, your total bill for the cycle will be $7 ($5 subscription fee + $2 of usage)" (pricing docs). The credit "is reset at the end of every billing cycle and does not accumulate over time." The same credit also pays for Railway Agent, Railway's built-in AI assistant, at Anthropic's token prices (pricing overview).
The plans differ more in their limits than in their prices:
| Limit | Free | Hobby | Pro |
|---|---|---|---|
| Per-service CPU and RAM | 1 vCPU, 0.5 GB | 48 vCPU, 48 GB | 1,000 vCPU, 1 TB |
| Replicas per service | 1 | 6 | 42 |
| Largest volume | 0.5 GB | 5 GB | 1 TB |
| Custom domains | 0 | 2 | 20 |
| Members | 1 | 3 | Unlimited |
| Log history | 3 days | 7 days | 30 days |
All limits are from Railway's pricing page and plan docs.
The one thing to understand is that Railway bills a service while it runs, not while it serves traffic. In Railway's words, "you pay for allocated resources, not traffic," and "a server running idle still uses memory to stay loaded" (understanding your bill). An app with no visitors at 3 a.m. costs the same RAM as at noon.
What does Railway charge per vCPU, GB of RAM and egress?
$20 per vCPU per month, $10 per GB of RAM per month, $0.05 per GB of public egress and $0.15 per GB of volume storage per month. A service that averages 0.1 vCPU and 0.5 GB of RAM for a month costs $2 plus $5. The rates are the same on Hobby and Pro.
| Resource | Rate | Per month, running all month | Source |
|---|---|---|---|
| CPU | $0.00000772 per vCPU-second | $20 per vCPU | Railway pricing |
| RAM | $0.00000386 per GB-second | $10 per GB | Railway pricing |
| Public egress | $0.05 per GB | Railway pricing | |
| Volume storage | $0.00000006 per GB-second | $0.15 per GB | Railway pricing |
| Object storage (buckets) | $0.015 per GB-month, free egress | Railway pricing | |
| Sandboxes (CPU and RAM) | $50 per vCPU, $50 per GB | Railway pricing |
The pricing page quotes rates per second. The plan docs quote the same rates per minute and say compute is "billed by the minute." The monthly totals are the same either way. Sandboxes are a separate product with their own rate (the docs call it the VM rate); an app service pays the rates above.
RAM is the line that adds up. A vCPU costs twice as much as a gigabyte, but most web apps and databases use a small fraction of a vCPU while holding their memory all month. In all three worked bills below, RAM is the biggest line.
What does the $5 Hobby plan really run?
$5 of usage buys about 0.5 GB of RAM running all month and nothing else, or a quarter of a vCPU and nothing else. In practice that's one small, quiet app and a small Postgres, each idling at a few hundred megabytes. Anything with steady traffic or a database holding real data in memory goes past $5.
Here's a mix that fits, using assumed averages for a quiet app:
| Line | Usage | Cost |
|---|---|---|
| Node app RAM | 0.2 GB average | $2.00 |
| Postgres RAM | 0.15 GB average | $1.50 |
| CPU, both services | 0.03 vCPU average | $0.60 |
| Public egress | 5 GB | $0.25 |
| Postgres volume | 0.5 GB | $0.08 |
| Usage | $4.43 | |
| Hobby bill | $5.00 |
Double either service's memory and you're past the credit. Hobby volumes are capped at 5 GB, and the docs say "Pro users and above can self-serve to increase their volume."
Railway "waives the monthly Hobby plan subscription fee for a small set of active builders on the platform," decided automatically (pricing docs). You can't count on it.
Is Railway free to use?
Only for a short trial or a very small service. New accounts get a one-time $5 credit for 30 days with no credit card. After that, the Free plan gives $1 of usage a month, which buys about 100 MB of RAM for a month, so an always-on app plus Postgres doesn't fit.
If you upgrade before the trial ends, the pricing page says the remaining trial credit carries over. If you pay with credits and the balance reaches zero, the plan docs say "your subscription will be cancelled." There's no slow-down mode.
Railway's Serverless puts a service to sleep "somewhere between 5 and 10 minutes after its last outbound traffic" (Serverless docs), which can stretch a free credit for a side project. But outbound traffic includes "telemetry, database connections, NTP," so an app holding a database connection stays awake, and "the first request sent to a slept service may return a 502 Bad Gateway response." It's for demos, not for an app with a database behind it.
What does an always-on web app + Postgres cost on Railway?
With my assumptions, a small app and Postgres cost $14.15 a month on Hobby, a medium one $61.50 on Pro and a busy one $217.50 on Pro. RAM is the biggest line every time, and Postgres is more than half the busy bill. Once usage passes $20, Hobby and Pro cost the same, because the plan fee is only credit.
| Line | Small | Medium | Busy |
|---|---|---|---|
| App CPU | $2.00 | $10.00 | $20.00 |
| App RAM | $5.00 | $10.00 | $20.00 |
| Postgres CPU | $1.00 | $10.00 | $40.00 |
| Postgres RAM | $5.00 | $20.00 | $80.00 |
| Public egress | $1.00 | $10.00 | $50.00 |
| Postgres volume | $0.15 | $1.50 | $7.50 |
| Usage | $14.15 | $61.50 | $217.50 |
| Plan | Hobby | Pro (volume over 5 GB) | Pro |
| Monthly bill | $14.15 | $61.50 | $217.50 |
The three sizes, as average usage over a 30-day month:
- Small: a side project with some users. App 0.1 vCPU and 0.5 GB; Postgres 0.05 vCPU and 0.5 GB; 20 GB egress; 1 GB volume.
- Medium: a small business app. App 0.5 vCPU and 1 GB; Postgres 0.5 vCPU and 2 GB; 200 GB egress; 10 GB volume.
- Busy: a SaaS with a database that works all day. App 1 vCPU and 2 GB; Postgres 2 vCPU and 8 GB; 1 TB egress; 50 GB volume.
These are assumptions, not measurements. Postgres is 43% of the small bill, 51% of the medium one and 59% of the busy one.
The database half has its own breakdown, including backups and high availability, in Railway Postgres pricing.
Why is my Railway bill higher than expected?
Usually because something is running that you forgot is billed. Railway charges every service in every environment for every minute it runs, so the bill grows with the number of copies, not with your traffic.
Take the small app above and add a background worker with Redis (0.05 vCPU and 0.5 GB between them) and two pull requests left open all month with PR environments on. The bill goes from $14.15 to $58.45 (in the calculator: Small, then 1.5 GB of RAM, 0.2 vCPU and 2 environments), and $38.30 of that is the two PR environments, because each one runs its own app and its own Postgres. Railway's docs say it plainly: PR environments "run real services that consume real resources" (understanding your bill).
The usual causes, in the order I'd check them:
- Environments. Every staging or PR environment copies your services, databases included.
- Replicas. Three replicas of a 1 GB app hold 3 GB of RAM all month, which is $30.
- A worker, Redis or cron service. Each is another always-on line.
- Public database URLs. App-to-database traffic over the public URL counts as egress; the private
DATABASE_URLdoesn't. - Memory that only grows. A Node heap or Postgres cache that never shrinks keeps billing at its high-water mark.
Why does the database drive the Railway bill?
Because a database's job is to hold data in memory all the time, and memory is the meter Railway charges most for in practice. Postgres caching a 16 GB working set costs $160 a month in RAM alone on Railway, before any CPU, storage or app. That's 8.7 times the price of a Hetzner CX43 with 8 vCPU and 16 GB of RAM ($18.49, Hetzner price list).
That's what happened to me. I paid Railway $500+ a month at one point, and the bill went up every month. My app wasn't the problem. The database was hit hard, it grew, and Postgres used more memory to keep up. I never changed a plan. Today one dedicated server at €80 a month runs more than I ever ran on Railway.
Usage billing is fair in the sense that you pay for what you use. It also means a successful database gets more expensive every month, with no ceiling except the one you set.
Is Railway cheaper than Vercel?
For a full-stack app, usually yes. Railway runs your database and workers on the same bill, while Vercel only runs the frontend and functions, so you'd pay someone else for Postgres. For a mostly static frontend with heavy traffic, Vercel's flat CDN tiers can win, because Railway's egress alone is $50 a terabyte.
From my Vercel pricing breakdown: a Next.js app at 100 GB of traffic costs $21 to $40 on Vercel Pro, and $120 at 1 TB on Flat Rate CDN. On Railway, a small always-on Next.js server at 0.25 vCPU and 0.5 GB costs $10 in compute, plus $5 of egress at 100 GB or $50 at 1 TB, so about $15 and $60. Add Postgres next to Vercel and you're paying a second provider, like Supabase.
The shape matters more than the totals. Vercel charges per request and per seat; Railway charges per minute of RAM. A quiet app with a big database is cheap on Vercel and expensive on Railway, and a busy frontend with a tiny backend is the other way round. Render's pricing works out differently again, because it sells fixed instance sizes.
Is Railway cheaper than your own server?
No, unless your app fits in the $5 Hobby credit. The small app costs $14 on Railway and $7 on a Hetzner CX23 with Ployz, custom domains included. The medium app is $62 against $11 on a CX33, and the busy app is $218 against $19 on a CX43.
| Server | Specs | Monthly price | Source |
|---|---|---|---|
| Hetzner CX23 | 2 vCPU, 4 GB RAM, 40 GB NVMe, 20 TB traffic | $6.49 | Price list, plans |
| Hetzner CX33 | 4 vCPU, 8 GB RAM, 80 GB NVMe, 20 TB traffic | $9.99 | Same |
| Hetzner CX43 | 8 vCPU, 16 GB RAM, 160 GB NVMe, 20 TB traffic | $18.49 | Same |
| Primary IPv4 | about $0.60 (€0.50) | Hetzner docs | |
| Netcup VPS 500 | 2 vCPU, 4 GB RAM, 64 GB SSD, traffic included | €8.26 incl. VAT on a 12-month term | netcup VPS |
| Netcup VPS 1000 | 4 vCPU, 8 GB RAM, 128 GB SSD, traffic included | €14.50 incl. VAT on a 12-month term | Same |
| Netcup VPS 2000 | 8 vCPU, 16 GB RAM, 256 GB SSD, traffic included | €26.92 incl. VAT on a 12-month term | Same |
Hetzner prices are after its 15 June 2026 adjustment, before VAT, and the CX line is only in Germany and Finland. For US users, Netcup has a datacenter in Manassas, Virginia, for about €1 more a month than the prices above.
| Small | Medium | Busy | |
|---|---|---|---|
| Railway | $14.15 (Hobby) | $61.50 (Pro) | $217.50 (Pro) |
| Hetzner server + Ployz | $7.09 (CX23) | $10.59 (CX33) | $19.09 (CX43) |
| Netcup server + Ployz, incl. VAT | about $9 (VPS 500) | about $16 (VPS 1000) | about $30 (VPS 2000) |
The Netcup row converts euros at about $1.13. I picked servers with room to spare: the busy app uses 10 GB of 16 and 3 vCPU of 8. A shared vCPU on a cheap server isn't the same as a Railway vCPU, so don't read the CPU columns one to one. And 1 TB of egress is a twentieth of Hetzner's included 20 TB, so it isn't a line on the server bill at all.
Each of these apps fits on one server, and Ployz is free on any number of servers.
How do you stop a Railway bill from climbing?
Set a hard usage limit, keep database traffic on the private network, and watch RAM, not requests. A hard limit stops the bill but takes every workload offline when it's reached, so set a soft limit email well below it.
- Usage limits. Every plan can set an email alert and a hard limit of at least $10. At the hard limit, "all your workloads will be taken offline" (usage limits docs). That protects your card, not your users.
- Private networking. Railway lists "not using private networking for databases" as a common cause of high bills (understanding your bill). Use the private
DATABASE_URLso app-to-database traffic isn't public egress. - Right-size memory. A Node process with a large heap or a Postgres with generous
shared_buffersholds that memory all month, at $10 per GB. - Delete idle environments. Every preview or staging copy with its own database is billed while it runs.
For every other fee hosting platforms add (seats, egress, per-service minimums), see the hidden costs of PaaS pricing.
Railway or your own server?
Stay on Railway if your app is small and quiet enough to stay near the $5 credit, you want a database next to your app without touching a server, or your services can sleep most of the time. Under about $7 a month of usage it's cheaper than the smallest server, and the setup is very good.
Pick your own server if your database holds more than a gigabyte or two in memory, your usage is past $7 a month, or you want a bill that doesn't grow with your success. An $11 to $19 server covers what costs $62 to $218 on Railway. If you'd rather stay on a platform, Railway alternatives prices six of them for the same app.
Where Ployz fits
I built Ployz after that Railway bill, to keep the workflow and drop the meter. It turns the servers you rent into a platform your coding agent runs. Paste one line into Claude Code, Codex or Cursor and it adds your server, ships the repo and sets up Postgres.
ployz up --server root@your-server
Every pull request gets a preview on the server you already pay for. Every deploy, restart or delete your agent asks for waits for you to approve. Ployz is free on any number of servers. Deploy to your own server.
FAQ
How much does Railway cost per month?
$5 a month on Hobby or $20 on Pro, and that fee is also usage credit. A real always-on app with Postgres costs about $14 small, $62 medium and $218 busy, because usage past the credit is billed.
How much does Railway Pro cost?
$20 a month per workspace, with $20 of usage included and any number of seats. Railway's pricing page says "the fee is per workspace, not per seat," so a team of ten pays the same $20 as one person. Some third-party guides still say per seat.
Is Railway completely free?
No. New accounts get a one-time $5 credit for 30 days, then the Free plan gives $1 of usage a month, which runs about 100 MB of RAM. An always-on app with a database needs Hobby at least.
Is the $5 Hobby plan a spending cap?
No, it's a minimum. Usage past the $5 credit is billed at the same rates, with no ceiling unless you set a hard usage limit, which takes your services offline when it's reached.
Why is my Railway bill higher than $5?
Because something holds more memory than $5 buys, which is about 0.5 GB for a month. The usual causes are a database caching data, replicas, PR or staging environments with their own databases, and a worker or Redis running all month.
Is Railway's Hobby plan enough?
For one small, quiet app and a small Postgres, yes. $5 buys about 0.5 GB of RAM running all month, so steady traffic or a growing database goes past it.
Does Railway charge when my app is idle?
Yes. Railway bills the memory a running service holds, not its traffic, so an idle app costs the same RAM as a busy one. Serverless sleep can stop that, but an open database connection keeps a service awake.
Is Railway Pro cheaper than Hobby?
No. Pro has the same usage rates and a $20 credit instead of $5. Once your usage passes $20, both plans cost the same; Pro adds bigger volumes, more replicas, more custom domains and unlimited members.
Is Railway expensive?
For a small, quiet app, no, because it often fits in the $5 credit. For an always-on app with a busy database, yes, because RAM costs $10 per GB a month and a database holds memory all the time. The medium app above costs $62 on Railway and about $11 on a rented server.
Which is better, Render or Railway?
Railway is cheaper for small apps that use little memory, because it bills usage. Render sells fixed instance sizes, which are easier to predict and can be cheaper once an app holds its memory all day. Render's 1 CPU, 2 GB instance is $25 a month; on Railway, an app averaging 2 GB and half a vCPU costs $30. I compare them service by service in Railway vs Render, and Render's plans are in my Render pricing breakdown.
How I checked
Prices were checked on 5 October 2026 on Railway's pricing page, pricing overview and plan docs, and on Hetzner's and Netcup's own pages, all linked next to each number. Hetzner's IPv4 price was last checked on 1 October 2026. Railway bills in USD, and the euro conversion for Netcup is approximate. The app sizes, the worker and the PR environments are assumptions, not measurements from my account.
Run your Railway app on your own server with Ployz, free: get started.