← All migration guides
Coming from Qovery
Qovery runs Kubernetes clusters in your own cloud account, priced per seat starting in the hundreds of dollars a month. Railyard deploys to a plain server in the same account, at a flat price per team.
Why teams leave Qovery
Qovery is a genuine bring-your-own-cloud platform built on Kubernetes, aimed at larger teams. The friction is price: team plans commonly start in the hundreds of dollars a month per seat, on top of the cloud bill you already pay, which puts it out of reach for a small team.
Railyard deploys to a plain server in the same cloud account, at a flat price per team regardless of seat count.
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. Qovery keeps serving until the cutover; there is no outage.
What’s different
A flat price per team instead of per-seat billing in the hundreds of dollars a month, and no Kubernetes cluster to operate.