Migrate from Railway

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

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

Get a migration estimateSee Varity pricing

Your bill today. Your bill on Varity.

The same production app. Two very different billing structures.

Your Railway bill today

  • +Plan subscription fee
  • +Compute metered per vCPU-minute
  • +Memory metered per GB-minute
  • +Network egress metered per GB
  • +Volume storage metered per GB
  • +Each database is its own billed service

Result

Unpredictable

The invoice is computed after the traffic happens.

Your Varity bill

One priceshown before you deploy
  • All-in. No plan subscription on top.
  • No vCPU-second meter.
  • No GB-second memory meter.
  • No egress meter.
  • Postgres, Redis, Mongo, MySQL attach as managed services.

Result

Predictable.

Side by side, line by line.

Structural differences, side by side. For current Railway dollar figures, see the official sources below.

Feature
Railway
Varity
Pricing model
Plan subscription plus usage on compute, memory, egress, and storage[1]
One fixed monthly price for the resources you reserve, shown before you deploy
CPU compute
Metered per vCPU-minute, continuously while running[1]
Included in the reserved resource profile. No per-second meter.
Memory
Metered per GB-minute of allocated RAM[1]
Included in the reserved resource profile. No per-second meter.
Network egress
Metered per GB[1]
No ingress or egress fees.
Free tier
Trial credit on the unpaid tier[1]
Free static tier: up to 3 active sites and 1 GB pinned assets for verified accounts, no card required.
Auto-sleep
Services can be configured to sleep, but billing meters while awake.
Reserved resources do not sleep and do not meter when idle.
Databases
Each database is its own billed service with its own usage meter.
Postgres + pgvector, Redis, MongoDB, MySQL attach as managed services, each with a preset price shown before you deploy.
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 when traffic spikes
Compute, memory, and egress meters scale the bill with traffic.[1]
For an unchanged resource profile, the price doesn't move with traffic.

A governed numeric cost comparison with matched assumptions and dated evidence is coming. Until then, see current Railway pricing at the official sources and Varity pricing at varity.so/pricing.

Sources

  1. [1]Current Railway pricing: docs.railway.com/reference/pricing/plans
  2. [2]Current Railway pricing: railway.com/pricing
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 a Varity Postgres service (its own reserved deployment with its own preset price).

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 Varity Postgres service. Same Postgres on both sides, so schema and data move cleanly. Varity attaches Postgres (with pgvector), Redis, MongoDB, and MySQL as managed services in the same cloud, each with its own preset price shown before you deploy.

What happens at 10x traffic?+

For an unchanged resource profile, your Varity price doesn't move with traffic. 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 fixed monthly price. The meters do not exist.

Get a migration estimateSee Varity pricing