← All migration guides
Coming from Koyeb
Koyeb autoscales containers on its own global edge network with no option to run on your own servers. Railyard deploys the same containers to a server in your own cloud account.
Why teams leave Koyeb
Koyeb is a capable autoscaling platform for containers at the edge. The friction shows up for teams that want a server they control: Koyeb runs exclusively on its own infrastructure, with no option to deploy into your own AWS, DigitalOcean or Hetzner account.
Railyard deploys the same containers to a server in your own cloud account, with managed databases alongside them.
What comes with you
- Your repo, built from a Dockerfile.
- Your environment variables and secrets.
- Managed Postgres, MySQL and Redis addons replace any managed datastore you were pairing with Koyeb.
The move
- Attach a server: an existing one, or a new one Railyard provisions in your cloud account.
- Add your repo and point Railyard at your Dockerfile.
- Bring your config and attach the datastores your app expects.
- Deploy to a temporary URL. Run your release task and verify.
- Move DNS. Koyeb keeps serving until the cutover; there is no outage.
What’s different
A server you own instead of a platform you can only rent capacity on, with no cloud account of your own to point it at.