Migrate from Railway

Railway bills by the second.
Varity bills by the month.

One flat monthly cost per app, based on the hardware reserved. No vCPU-seconds, no GB-seconds, no egress meter.

Your bill today. Your bill on Varity.

A 1 vCPU / 2 GB / 50 GB egress production app. Two very different invoices.

Your Railway bill today

  • +$5 / month Hobby plan subscription
  • +$20 / month per vCPU compute
  • +$20 / month for 2 GB memory
  • +$2.50 / month for 50 GB egress
  • +$1.50 / month for 10 GB storage
  • +Each database is its own billed service

Floor

~$49 / month

Heavy traffic: ~$126+ / month before databases.

Your Varity bill

$6/ month
  • All-in. No plan subscription on top.
  • No vCPU-second meter.
  • No GB-second memory meter.
  • No egress meter.
  • Postgres, Redis, Mongo, MySQL sidecars included.

Result

Flat. Forever.

Your bill at scale.

The horizontal teal line is Varity. The rising gray line is what you are paying today.

Varity stays flat at $6 per month from 100 users to 1 million users per month. Railway rises from $5 to $128 per month over the same range.$0$25$50$75$100$150Monthly bill (USD)10010K100K1MMonthly active users$5$35$80$128+/mo$6/mo (flat)Railway$122+/mo gap

Side by side, line by line.

Every dollar amount on the Railway side cites a live source.

Feature
Railway
Varity
Pricing model
Plan subscription + usage on compute, memory, egress, and storage[1]
One flat monthly cost per app, based on the hardware reserved
Base subscription
Hobby $5 / mo (includes $5 usage credit), Pro $20 / mo (includes $20 usage credit)[1]
$6 / mo for a dynamic app, $5 / mo for a static site. No separate plan fee.
CPU compute
$20 per vCPU per month ($0.000463 per vCPU-minute), metered continuously while running[1]
Included in the flat hardware reservation. No per-second meter.
Memory
$10 per GB per month ($0.000231 per GB-minute) of allocated RAM[1]
Included in the flat hardware reservation. No per-second meter.
Network egress
$0.05 per GB[1]
Included. No egress meter.
Volume storage
$0.15 per GB per month[1]
Included in the hardware reservation.
Trial credit
$1 free credit per month on the unpaid trial tier[1]
No permanent free tier. Static sites start at $5 / mo.
Auto-sleep
Services can be configured to sleep, but billing meters while awake.
Reserved hardware does not sleep and does not meter when idle.
Sidecar databases
Each database is its own billed service with its own usage meter.
Postgres + pgvector, Redis, MongoDB, MySQL auto-wired inside the app price.
Migration path
Self-serve
Redeploy your services on Varity, same stack, same env vars. Scripted Railway migration coming soon.
Stacks supported
Node, Python, Go, Rust, Ruby, Elixir, PHP, Java, plus Docker
Node (Next.js, React, Vue, Astro, Qwik, Vite, Express, Fastify, Nest, Koa, Hono), Python (FastAPI, Django, Flask), static HTML
Bill at a single production app (1 vCPU, 2 GB RAM, 50 GB egress, 10 GB storage)
Hobby $5 plan + $20 CPU + $20 memory + $2.50 egress + $1.50 storage = ~$49 / month (Pro plan starts at ~$64 / month with same usage)[1]
$6 / month, flat. Postgres included as sidecar.
Bill at heavy traffic on the same app
Pro $20 + $40 (2 vCPU) + $40 (4 GB RAM) + $25 (500 GB egress) + $1.50 (10 GB storage) = ~$126 / month before adding Postgres, Redis, or workers as separate metered services.[1]
$6 / month, flat. Same app, same bill.
Redeploy on Varity

Same repo. Same env vars. Same stack.

Varity does not have a one-command Railway migrator yet. The path is a clean redeploy.

terminal
$ pipx install varitykit
$ cd your-railway-app
$ varitykit app deploy
 Detected Next.js
 Loaded env vars from .env
 Auto-wired Postgres + Redis sidecars

Live at varity.app/your-app

Your repo

Same code. Same start command.

Your databases

pg_dump to Varity Postgres sidecar. No separate bill.

Your env vars

Copy from Railway dashboard. No code changes.

Common migration questions

The five things builders ask before they migrate.

How long does migration take?+

Most apps move in under an hour. Varity does not have a one-command Railway migrator yet (the varitykit migrate command is Vercel-specific today). The path is: redeploy your repo on Varity, same stack, same env vars. A scripted Railway migration is on the roadmap.

What if I need to roll back?+

Keep your Railway services running until your varity.app URL is verified end-to-end. Migration does not touch your Railway deployment. Point your DNS over only after you have confirmed the Varity URL works. Rollback is a DNS change away.

Will my Railway database migrate?+

Yes, via a standard pg_dump from your Railway Postgres into your auto-wired Varity Postgres sidecar. Same Postgres on both sides, so schema and data move cleanly. Varity auto-wires Postgres (with pgvector), Redis, MongoDB, and MySQL inside the app price. No separate per-database bill.

What happens at 10x traffic?+

Your bill stays $6 per month. The hardware you reserved is the hardware you have. Railway meters compute per vCPU-second, memory per GB-second, network egress per GB, and storage. Three growth axes mean three ways traffic growth becomes bill growth. On Varity, those meters do not exist.

Can I move off Varity later?+

Yes. Varity deploys are standard containers. Lift-and-shift to anywhere that runs containers. There is no Varity-specific runtime and no vendor lock-in baked into your code.

Stop paying by the second.

One app. One flat monthly cost. The meters do not exist.