Railway Pricing in 2026: What You Actually Pay

Quick answer (2026): Railway bills usage per second, and the plan fee is a credit pool, not an entry ticket. There are four self-serve tiers: a 30-day Free Trial ($5 in credits, no card), a permanent Free plan at $0/month with $1 of monthly usage credits (capped at 1 vCPU / 0.5 GB RAM per service, 0.5 GB volume, community support), Hobby at $5/month including $5 of credits, and Pro at $20/month per workspace including $20 of credits. Pro is per workspace, not per seat: seats are unlimited and included, which is the single most-repeated error in Railway write-ups. The meters are $20 per vCPU per month, $10 per GB of RAM per month, $0.05 per GB of egress, $0.15 per GB of volume storage, and $0.015 per GB-month for object storage with free egress. Your bill is the greater of your plan fee or your metered usage. Those five meters are the container rate card and not the whole bill: workloads on Railway's VM primitive, which is what sandboxes and cloud agents run on, bill at $50 per vCPU and $50 per GB of RAM per month, and the Railway Agent is passed through as LLM tokens on its own invoice line. In practice: a small always-on bot costs about $5, a web app with Postgres about $22, and a production stack with two services plus Postgres and Redis about $70.

_Updated October 9, 2026. Every plan fee, credit allowance and container meter above was re-verified against Railway's official pricing page{target=blank} on this date and every one of them is unchanged. New this pass: the container meters are not the whole bill. Railway bills workloads on its VM primitive, which is what sandboxes and cloud agents run on, at a separate and higher rate card, and the Railway Agent is billed through as LLM tokens on its own invoice line. Both are covered below. The permanent Free plan at $0/month with $1 of monthly usage credits and the $0.015 per GB-month object storage meter, both added on August 20, 2026, are unchanged too.

Railway pricing in 2026 has one governing rule: you pay for the compute you actually consume, billed by the second, and almost every summary you find gets the plan structure wrong on top of that rule.

Railway runs each service as a container and meters the vCPU and memory it burns, per second, plus the bandwidth and disk it touches. There is no fixed per-app plan and, as of 2026, no per-seat fee. The subscription you pick is a spending floor with usage credit baked in, not a cap. Get those two ideas straight and the bill stops being a mystery.

What Railway actually charges for

Every Railway bill for a normal container service is built from five metered lines. These are the current published rates (railway.com/pricing, read October 2026). Sandboxes, cloud agents and the Railway Agent bill on separate rate cards, covered further down.

The number that trips people up is the CPU rate. "$20 per vCPU per month" is the rate for a full vCPU pinned at 100 percent for the whole month. You are billed for the fraction you actually use per second, so a service that averages a tenth of a vCPU pays about $2, not $20.

Is Railway pricing per seat? No, and most of the web still says otherwise

The single most-repeated error in Railway write-ups is that the Pro plan is "$20 per seat." Several pages ranking for this exact query say it. As of 2026 it is wrong.

Railway's own pricing page states the Pro plan is $20 per month per workspace, seats are unlimited and included. It is a workspace fee, not a headcount fee. That matters for teams: on Vercel, a Pro plan is billed per member (about $20 per user per month plus usage, per Railway's own 2026 comparison), so a five-person team pays roughly $100 in seats before any compute. On Railway that same team pays one $20 workspace fee. If you read "per seat" anywhere for Railway, the source is stale (Railway documents the per-workspace model in its own comparison to Vercel).

The plans: Free Trial, Free, Hobby, Pro

Railway has four self-serve tiers plus Enterprise. The base fee is a credit pool, not an entry ticket you pay on top of usage.

Two things to note, and the first one changed in 2026. Railway now runs two distinct zero-dollar entries: the 30-day Free Trial with $5 of credits, and a permanent Free plan at $0 a month carrying $1 of monthly usage credits. Most write-ups still say Railway has no permanent free tier, and that is now out of date. The catch is that $1 a month buys very little: capped at 1 vCPU and 0.5 GB of RAM per service with 0.5 GB of volume and community-only support, it covers a hobby script that idles almost all month, not a real always-on app. Unlike Render, which still offers a free web service that sleeps when idle, Railway's free lane is a credit allowance rather than a free instance, so anything with steady traffic still lands on Hobby. Budget for a real bill from day one. Second, the per-service resource caps are generous even on Hobby (48 vCPU / 48 GB), so the ceiling is your wallet, not the plan.

How the included credit works

The base fee already contains that much usage. Railway puts it plainly: on the Hobby plan at $5 a month, if you use $3 of resources, you pay the $5 subscription. Use more than the included credit and the overage is added.

So the mental model is: your monthly bill is the greater of the base fee or your metered usage.

• Hobby: pay $5 if usage is under $5, otherwise pay your usage.
• Pro: pay $20 if usage is under $20, otherwise pay your usage.

That is the whole billing engine for container services. The three worked bills below are arithmetic on those five rates. Railway's VM primitive and its Railway Agent bill on their own rate cards, which the next section covers.

VM workloads and the Railway Agent bill separately

The five meters above are the container rate card. Two other things on Railway bill on their own terms, and neither is arithmetic on those rates.

Workloads on Railway's VM primitive cost 2.5x the container rate. Sandboxes and cloud agents do not run as containers. They run on a virtual machine primitive with its own published rates (docs.railway.com/pricing/plans, read October 2026).

The multiple matters more than the rate. Cost an agent sandbox using the $20 and $10 figures from the table further up and you are out by 2.5x on both compute lines. Railway is also explicit that VM memory bills for as long as the machine holds it: memory remains billable while a VM waits for work, along with any background CPU use or outbound traffic. A sandbox parked waiting on a model response is still paying for its RAM at $50 per GB per month. The lever here is destroying the sandbox, or letting the idle timeout destroy it, not right-sizing what it is allocated.

The Railway Agent is billed as LLM tokens on a separate invoice line. Railway passes the model cost through with no markup and routes each request to the smallest model that can handle it, so the charge is per input and output token at the model vendor's own published rate (docs.railway.com/pricing, read October 2026). It draws from the same included credit as compute, so the $5 on Hobby and the $20 on Pro cover combined compute and agent spend before any overage starts.

Neither of these shows up in the three bills below, which are all container workloads.

Three real 30-day Railway bills

Here is what actual workloads cost. Each row assumes always-on services and uses average, not peak, resource consumption, because that is what Railway meters.

The math on the middle row, so you can reproduce it: 0.5 vCPU x $20 = $10.00, plus 1 GB x $10 = $10.00, plus 20 GB egress x $0.05 = $1.00, plus 5 GB volume x $0.15 = $0.75, for $21.75 of usage. That sits above the $5 Hobby credit, so the whole $21.75 is the bill.

The small bot never leaves the $5 Hobby credit, so it costs the $5 base and nothing more. The production stack on Redis and Postgres clears the $20 Pro credit easily and lands near $70. None of these three needs a per-seat upgrade.

Why your Railway bill can surprise you

The most common panic post, and the pos-2 result for this query, is a developer on r/webdev doing a rough calculation: "2 GB RAM and 2 cores means I pay $80 a month?" Let us settle it.

A service allocated 2 vCPU and 2 GB, running flat out 24 hours a day, would cost 2 x $20 plus 2 x $10 = $60 of compute per month. Not $80, and only if it is genuinely pinned at full utilization the entire month. Because Railway bills the per-second fraction you actually use, a typical web service that averages 0.3 vCPU pays about $6 for CPU, not $40. The surprise bills almost always come from one of three places:

• A service that never idles because of a busy loop or a health check hammering it, so average usage approaches the allocation.
• Egress at scale. At $0.05 per GB, a service pushing 1 TB of traffic adds $50 a line item people forget.
• Forgotten replicas or a second environment left running. Every awake container meters independently.

The fix is not a cheaper plan. It is right-sizing what stays awake.

Railway vs Render vs Fly.io vs Vercel, one line each

The pricing model matters more than the sticker. Here is how the four common choices bill in 2026.

• Railway: usage-based, per second, one workspace fee ($5 Hobby or $20 Pro) with usage credit included.
• Render: fixed instance sizes (you pick an instance and pay its flat rate), plus a free web service that sleeps when idle. Predictable, less granular.
• Fly.io: pure per-second pay-as-you-go on Machines, no plan at all. Closest sibling to Railway's model; see our Fly.io pricing teardown for its real bills.
• Vercel: $20 per member per month on Pro, plus usage. Cheapest for a solo front-end, most expensive model for a multi-seat team.

If your workload is spiky and you want to pay only for what runs, Railway and Fly.io win. If you want a flat, predictable number, Render's fixed instances are easier to forecast. Our Northflank pricing breakdown covers a fourth option for teams that outgrow single-container simplicity.

How to cut a Railway bill

Four levers, in order of payoff:

1. Right-size replicas. Drop idle replicas to one. Each awake container meters separately.
2. Kill zombie environments. A forgotten preview or staging service bills the same as production.
3. Watch egress. Cache static assets and images on a CDN so traffic does not leave your Railway service at $0.05 per GB.
4. Trim volumes. Volume storage meters continuously at $0.15 per GB per month whether the service is up or not. Delete disks you no longer read.

None of these requires a plan change. Railway's usage model rewards discipline directly: use less, pay less, the same day.

Math check: a full vCPU costs $20 a month, but you pay only the per-second fraction you use, so a service averaging 0.3 vCPU costs about $6, not $20. The bill is set by what stays awake, not by which plan you pick.

Correction, October 9, 2026: this page previously said "Every Railway bill is built from four metered lines" and "That is the whole billing engine. Everything below is arithmetic on those four rates." Both were wrong on three counts. The rate table on this page already listed five meters once object storage was added on August 20, 2026. Railway separately bills workloads on its VM primitive, which is what sandboxes and cloud agents run on, at $50 per vCPU and $50 per GB of RAM per month rather than $20 and $10. And the Railway Agent is billed through as LLM tokens on its own invoice line. Separately, the excerpt for this page still read "There is no permanent free tier, only a 30-day $5 trial", a claim this page's own quick answer and FAQ had already corrected on August 20, 2026. Every container rate, plan fee and credit allowance on this page was re-verified against railway.com/pricing on October 9, 2026 and none of them changed.