← All migration guides
Coming from Anywhere else
Fly, DigitalOcean App Platform, Coolify, Dokku, a hand-rolled VPS — if it builds from a Dockerfile, buildpacks or a Procfile, it moves.
The move is the same shape everywhere
Railyard does not need a special adapter for your current host. If your app builds from a Dockerfile, Cloud Native Buildpacks, Nixpacks, or a Procfile, and it talks to Postgres, MySQL or Redis, it moves.
What comes with you
- Your repo and its build definition, unchanged.
- Your process types —
web,worker,release, whatever you run. - Your environment variables.
- Your databases, as managed addons with injected connection strings.
- Your custom domains, with automatic TLS.
The move
- Point Railyard at a server — one you already have, attached over SSH, or a new one provisioned in your cloud account.
- Add your repo and choose the build method that matches how it builds today.
- Bring your config and attach the datastores your app expects.
- Deploy to a temporary URL and put the app through its paces.
- Move your data with a standard dump and restore into the managed addon.
- Cut DNS over. Your current host keeps serving until the record flips. There is no window where nothing is up. Then shut the old deployment down.
The one rule that makes it safe
Never delete the old thing until DNS has moved and you have watched real traffic land on Railyard. Keep the old platform paid up for a week. Then cancel it.