Railway Pricing 2026: Hobby vs Pro and What Usage Really Costs

Railway costs $5/mo on Hobby and $20/mo per workspace on Pro in 2026, and each fee is a minimum that already includes the same amount of usage. The Free plan is $0 with $1 of monthly usage, and Enterprise is a custom contract. Past the included amount you pay for memory, CPU, storage and egress by the second, so the plan you pick matters less than what your services actually run.

Every figure on this page was read on Railway's pricing page and its plans documentation on October 18, 2026. Our view: most solo developers belong on Hobby, and any team whose usage passes the Pro minimum should move to Pro, because at that point the upgrade costs nothing extra. The product itself is covered in the Railway review; this page is the bill.

Plan	Monthly fee	Usage included	Members per project	Best for
Free Trial	$0, no card	$5 one-time credit for 30 days	3	Trying a deploy before you commit
Free	$0	$1 a month	1	A tiny always-on service or a sleeping demo
Hobby	$5/mo	The full fee	3	Side projects and one-person products
Pro	$20/mo per workspace	The full fee	Unlimited	Teams shipping to production
Enterprise	Custom	Negotiated	Unlimited	Contractual SLAs, SSO, HIPAA, procurement

Toolradar data: the hosting and deployment ranking evaluated 317 tools as of October 2026, and 140 of the 198 it ranks have a free plan, so a free entry point like Railway's is the norm in this category, not a perk. Railway's directory record is Railway on Toolradar.

How does Railway billing work?

Railway is a usage-based host with a subscription floor. You pay the plan fee, the fee counts as usage credit, and anything beyond it is billed at the meter rates. The plans doc puts it in one line: if usage passes the included amount, "you will be charged the delta." So a Hobby month with $7 of usage costs $7, and a Hobby month with $3 of usage still costs the full Hobby fee.

Included usage does not roll over. Railway's pricing FAQ says it resets at the end of every billing cycle and does not accumulate, so a quiet month cannot bank credit for a busy launch.

The meters are the same on every plan. These are the container rates Railway lists, with its own 30-day approximations:

Meter	Railway's rate	About per month
Memory	$0.00000386 per GB per second	$10 per GB
CPU	$0.00000772 per vCPU per second	$20 per vCPU
Volume storage	$0.00000006 per GB per second	$0.15 per GB
Network egress	$0.05 per GB	Billed per GB sent
Object storage	$0.015 per GB-month	Egress from buckets is free

Service builds cost nothing, which matters for teams that push many times a day. The plans doc says Railway does not bill build CPU, memory, base-image downloads, image exports or image storage, so a busy CI habit does not show up on the invoice the way build minutes do on other hosts.

The catch is that memory is billed whether or not the service is busy. A service holding 1 GB of RAM all month pays the full monthly memory rate even at zero requests, while CPU is billed on what the process actually uses. That is why an idle app on Railway costs mostly memory, and a busy one costs mostly CPU.

What the Free plan and the trial actually cover

The trial is a one-time credit that lasts 30 days, with no credit card. During it you get up to 2 vCPU and 1 GB of RAM per service, 2 replicas, 500 MB volumes and 3 concurrent builds. Railway's pricing page says any balance left when you upgrade carries over to the new plan, so upgrading on day 10 does not burn the rest of the grant.

After the trial, the Free plan gives $1 of usage a month, with 1 vCPU and 0.5 GB of RAM per service, one replica, 500 MB volumes, 3 days of logs and one member. At the memory rate above, that credit buys about 0.1 GB of RAM for a full 30-day month before any CPU. That is enough for a tiny bot, not for a web app with a database.

Serverless is how that credit stretches. The Serverless doc says a service with it enabled is put to sleep once it stops sending outbound traffic for about 5 minutes, and the cost-control docs say this reduces what the service costs to run. The trade-off is the wake-up: the first request to a sleeping service can take a moment and may return a 502. Fine for a demo, wrong for anything a customer hits.

Hobby or Pro: where the upgrade becomes free

The two paid plans differ in limits, not in meter rates. Here is what the pricing page and plans doc list per service:

Limit	Hobby	Pro	Enterprise
Max per service	48 vCPU, 48 GB RAM	1,000 vCPU, 1 TB RAM	2,400 vCPU, 2.4 TB RAM
Replicas	6	42	50
Max volume	5 GB	1 TB	5 TB
Log history	7 days	30 days	Longer with committed spend
Concurrent builds	3	10	Not listed
Members per project	3	Unlimited	Unlimited

The break-even is the Pro minimum itself. Below the Pro fee in monthly usage, Hobby is cheaper by the difference: a project using $8 pays $8 on Hobby and the full Pro fee on Pro. At or above that amount, both plans charge exactly the usage, so Pro's unlimited members, 30-day logs, 10 concurrent builds and 1 TB volumes cost nothing extra.

The volume cap is the limit that forces most upgrades. Hobby stops at 5 GB per volume, so a Postgres database that grows past that has to move to Pro whatever the bill says. The member cap is the other: three people per project is a small team, and a fourth collaborator means Pro.

Pro is priced per workspace, not per seat. Ten engineers on one Pro workspace pay the same floor as one, which is the opposite of hosts that bill each deployer; the Vercel pricing breakdown shows how fast per-seat fees add up for a team.

Three Railway bills, priced from the meter rates

We priced three common setups at Railway's monthly rates. The average CPU of each service is our assumption, not a Railway figure, so swap in your own averages from the metrics tab. Memory is what the service holds all month.

1. Solo side project. One web service with 0.5 GB of RAM averaging 0.05 vCPU, plus 5 GB of egress. Memory is $5.00, CPU $1.00 and egress $0.25, for $6.25 a month on Hobby. On Pro the same app would bill the Pro minimum, so it stays on Hobby.

2. Small production app with Postgres. A web service with 1 GB of RAM averaging 0.25 vCPU ($15.00), a Postgres service with 0.5 GB averaging 0.1 vCPU ($7.00), a 5 GB volume ($0.75) and 50 GB of egress ($2.50). Usage is $25.25 a month, and that is the bill on Hobby or Pro. Since Pro costs the same here, take Pro for the logs and the room to grow the volume.

3. Team app. Two web replicas with 2 GB each averaging 0.5 vCPU ($60.00), a worker with 1 GB averaging 0.25 vCPU ($15.00), Postgres with 4 GB averaging 1 vCPU ($60.00), a 50 GB volume ($7.50) and 200 GB of egress ($10.00). Usage is $152.50 a month on Pro, for any number of engineers. Hobby cannot run it: the volume alone is ten times the Hobby cap.

CPU is the line that moves these bills. Each extra vCPU averaged across a month adds the full per-vCPU rate from the meter table, so a team app whose database climbs from 1 to 2 average vCPU goes from $152.50 to about $172.50. Memory moves at half that rate per unit, and egress barely registers until you serve heavy files, so tuning CPU is where the savings are.

How Railway compares with Render, Heroku and Fly.io

Here is scenario 2 priced on three alternatives, each from its own pricing page on October 18, 2026. Fixed-size hosts reserve the whole instance, so we picked the cheapest size with at least the RAM the Railway services hold.

Host	Web service	Postgres	Storage and traffic	Monthly bill
Railway Hobby or Pro	Metered, $15.00	Metered, $7.00	$3.25	$25.25
Fly.io	shared-cpu-4x, 1 GB, $8.78	Managed Postgres Basic, $38	$2.40	$49.18
Render Hobby	1 CPU, 2 GB, $25	0.5 CPU, 1 GB, $19	$7.95	$51.95
Heroku	Standard-2X, 1 GB, $50	Essential-1, 10 GB disk, $9	Not priced here	$59.00

Render adds a $25/mo workspace fee on Pro, which takes this app to $73.95 with Pro's 25 GB of included bandwidth; past it, bandwidth is $0.15 per GB. Its Postgres storage is $0.30 per GB beyond the 1 GB included. On Fly.io, Managed Postgres storage is $0.28 per GB and North America and Europe egress is $0.02 per GB, cheaper per GB than Railway's. Heroku needs Standard-2X to reach 1 GB of RAM, because its Basic dyno at $7 stops at 0.5 GB.

The comparison flips when CPU runs hot all month. Render's 1 CPU web instance stays at its price at 100% load, while Railway would bill the per-vCPU rate for every second of that load, on top of memory. The head-to-head with the break-even math is in Railway vs Render, and the product side is in the Render review, Fly.io review and Heroku review. Directory records: Render, Fly.io and Heroku on Toolradar.

Costs outside the plan card

Sandboxes and cloud agents bill at VM rates, not container rates: $50 per GB of RAM and $50 per vCPU per month on the pricing page. That is five times the container memory rate, so an agent workload left running is the fastest way to surprise yourself on Railway.

Database egress through the TCP proxy is billed. Railway's Postgres doc says connecting to the database from outside the project over the TCP proxy is charged as network egress, so a laptop BI tool pulling large tables pays the $0.05 per GB line.

Taxes sit on top. Railway's FAQ says it may collect sales tax and VAT based on your billing location, so a taxable invoice is higher than the usage figure.

Enterprise is a contract, not a price. The pricing page lists contractual SLAs, SSO, dedicated support and procurement options, and says enterprise agreements add HIPAA BAAs, dedicated VMs and support SLOs. Annual committed spend unlocks longer log retention, SSO, RBAC and extended audit logs. Railway publishes no figure for any of these, so budget them from a quote.

How to keep a Railway bill from running away

Set a hard limit before the first busy month. The cost-control docs say that when usage hits it, all workloads go offline to stop further charges, with emails at 75%, 90% and 100% of the threshold. The minimum hard limit is $10, and a separate soft limit only sends an alert.

A hard limit trades a surprise bill for a planned outage, so set it above your real peak, not at the plan fee. Replica limits are the second control: capping CPU and memory per replica bounds the worst case, though the docs warn that limits set too low will crash the service.

For object files, a Railway bucket at $0.015 per GB-month holds 100 GB for $1.50, cheaper than a volume at $0.15 per GB and with free egress. The object storage pricing comparison lines it up against S3 and R2.

Dupple data: Devshot reaches 29,000+ developers with a 32% open rate, per the audience file dated October 25, 2026. Hosting bills like this one are a regular topic in the Devshot brief.

Which Railway plan to pick

Start on the trial, then Hobby, for anything one person runs. Move to Pro the month usage passes the Pro minimum, a fourth person joins, or the database needs more than 5 GB, because past that line the plan no longer costs extra. Talk to sales only for SSO, a BAA or a contractual SLA.

If Railway's metering is the wrong shape for your app, the field is in Heroku alternatives and Postgres hosting; moving an existing app is covered in how to migrate from Heroku, and a fixed-price box is in cheap VPS hosting.

How we checked these prices

Louis Corneloup, founder of Dupple and Toolradar, wrote this page from Railway's pricing page, plans doc, pricing FAQ, cost-control doc, Serverless doc and Postgres doc, all read on October 18, 2026. Competitor figures come from the Render, Fly.io and Heroku pricing pages linked above, read the same day. Scenario CPU averages are our inputs; every rate is the vendor's. Devshot runs no test lab, so nothing here is a benchmark. Editorial rules are on the Devshot about page.

FAQ

How much does Railway cost in 2026?

Railway has a $0 Free plan with $1 of monthly usage, Hobby at $5/mo with the same amount of usage included, and Pro at $20/mo per workspace, again with usage equal to the fee. Usage past the included amount is billed at about $10 per GB of RAM a month, plus CPU by the second. Enterprise is a custom contract. Prices were read on Railway's pricing page on October 18, 2026.

Is Railway free?

Partly. New accounts get a one-time trial credit for 30 days with no card, then the Free plan gives a monthly usage credit with 0.5 GB of RAM per service and one member. That credit covers about 0.1 GB of RAM running all month, so a real app needs Hobby. Serverless sleeping stretches it for demos, at the cost of a slow first request.

Is Railway Pro worth it over Hobby?

Yes once usage reaches the Pro minimum, because both plans then bill exactly the usage and Pro adds unlimited members, 30-day logs, 10 concurrent builds and volumes up to 1 TB. Below that, Hobby is cheaper: a project using $8 a month pays $8 on Hobby and the full Pro fee on Pro. A database over 5 GB forces Pro regardless.

Do unused Railway credits roll over?

No. Railway's pricing FAQ says included usage resets at the end of every billing cycle and does not accumulate. The one exception is the trial: a trial balance left when you upgrade carries over to the paid plan.

Is Railway cheaper than Render or Heroku?

For a light app, usually. In our small production scenario with Postgres, Railway came to $25.25 a month, against $49.18 on Fly.io, $51.95 on Render Hobby and $59.00 on Heroku. Railway bills average CPU while those hosts sell fixed sizes, so an app that pegs its CPU all month narrows the gap, since every average vCPU raises Railway's bill while a fixed instance stays flat.

How do I cap my Railway bill?

Set a hard limit in usage settings, minimum $10. When usage reaches it, Railway takes all workloads offline and stops charging, after emails at 75%, 90% and 100%. A soft limit only sends an email. Replica limits on CPU and memory cap each service, but set too low they crash it.

Cite this: Devshot, "Railway Pricing 2026: Hobby vs Pro and What Usage Really Costs", October 2026.

Devshot is the daily brief on the tools and bills developers deal with. Subscribe at devshot.co.

Some offers on this page may be paid placements or contain affiliate links.