← All migration guides
Coming from Zeabur
Zeabur deploys from a template marketplace on Zeabur's own cloud, billed by usage. Railyard gives you the same template-driven deploy workflow on servers in your own cloud account, at a flat price per team.
Why teams leave Zeabur
Zeabur is a fast way to deploy from a template marketplace with usage-based pricing. The friction shows up as you scale: usage billing gets harder to predict, and the default path runs on Zeabur’s own cloud rather than an account you control.
Railyard keeps the one-click deploy feel and runs it on a server in your own DigitalOcean, Hetzner or Vultr account, 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 servers: attach them over SSH rather than rebuilding the fleet.
The move
- Attach a server: an existing one, or a new one Railyard provisions in your cloud account.
- Add your repo and select the build method that matches how Zeabur builds it today.
- 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. Zeabur keeps serving until the cutover; there is no outage.
What’s different
A flat price per team instead of usage billing, and every server lives in your own cloud account from day one.