Leaving Railway

Usage-based billing means the bill decides itself

Railway meters compute by the vCPU-hour and GB-hour, bills egress by the GB, and charges $20/seat on Pro. None of those numbers are ones you approve in advance. Here is a six-service account under real traffic.

A typical Railway bill

$980/mo

Service compute (6 always-on services)$520

Pro seats ×8$160

Egress (~1.5TB)$150

Plugin compute + storage (Postgres, Redis)$150

Modeled from usage meters and published rates.

The same workload on Hetzner + Neon + Upstash

$111/mo

Sized from the workload above, not a marketing tier. Saves $869/mo.

1× CCX13 (2 vCPU / 8GB, dedicated)$14

Load balancer$7

Neon Postgres (1 CU + storage)$80

Upstash Redis (250MB fixed)$10

Egress (~1.5TB) — 20TB+ included$0

A fixed number you can put in a budget. The bill stops moving with traffic and starts moving with decisions you make.

The migration is the product

infralift builds the new environment in parallel with your live site, delivers everything as Terraform you own, then cuts over at the edge, which is reversible in seconds for as long as the old stack stays warm. Moving the database needs a short write pause, minutes long and sized from your data. The assessment is free and reads your account with a scoped token; the migration is a fixed fee quoted up front, so the price in the report is the price you pay.

How we handle secrets, data sync, and the cutover itself: the migration process.

Run the free assessment