← All migration guides
Coming from Scaleway
Scaleway's serverless containers run only on Scaleway's own cloud. Railyard deploys the same containers to a server in any cloud account, including Scaleway's.
Why teams leave Scaleway’s serverless platform
Scaleway’s serverless containers are a reasonable way to run a container without managing a server, within Scaleway’s own cloud. The friction shows up if you want a server you fully control, or the flexibility to use a different provider instead of Scaleway’s.
Railyard deploys the same containers to a server in your own cloud account, on Scaleway or elsewhere.
What comes with you
- Your repo, built from a Dockerfile.
- Your environment variables and secrets.
- Managed Postgres, MySQL and Redis map directly to Railyard addons.
The move
- Attach a server: a new one Railyard provisions in your Scaleway account, or any other provider you choose.
- 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. There is no outage; the old deployment keeps serving until the cutover.
What’s different
A real server you control, with the freedom to stay on Scaleway or move to a different provider without rebuilding your deploy setup.