← All migration guides
Coming from Northflank
Northflank runs Kubernetes in your own cloud account, priced per vCPU and GB-hour on top of your cloud bill. Railyard runs the same apps on a plain server in your account, at a flat price per team.
Why teams leave Northflank
Northflank is a capable bring-your-own-cloud platform built on Kubernetes. The friction is the Kubernetes tax: per-vCPU and per-GB-hour pricing stacks on top of the cloud bill you already pay, and the underlying cluster adds operational weight most small teams don’t need.
Railyard deploys to a plain server in the same cloud account, with none of the cluster overhead, at a flat price per team.
What comes with you
- Your repo, built from a Dockerfile, buildpacks, or a Procfile.
- Your environment variables and secrets.
- Managed Postgres, MySQL and Redis map directly to Railyard addons.
- Your existing cloud account: Railyard provisions a plain server in it instead of a Kubernetes cluster.
The move
- Attach a server: a new one Railyard provisions in your existing cloud account.
- Add your repo and select the build method that matches your app.
- Bring your config and attach the datastores your app expects.
- Deploy to a temporary URL. Run your release task and verify.
- Migrate data with a dump and restore into the managed addon.
- Move DNS. Northflank keeps serving until the cutover; there is no outage.
What’s different
A flat price per team instead of per-vCPU and per-GB-hour billing on top of your cloud bill, and no Kubernetes cluster to operate.