← All migration guides
Coming from CapRover
CapRover is a free, open-source PaaS you self-host on one server. Railyard keeps the one-click app feel and adds managed backups and multi-server failover.
Why teams leave CapRover
CapRover is a solid, free, self-hosted PaaS with a one-click app marketplace on top of Docker Swarm. The friction shows up on day two: no managed database backups, no point-in-time restore, and you’re the one keeping the underlying server patched and monitored.
Railyard keeps the one-click deploy feel and adds backups, verified restores and a second server without rebuilding anything.
What comes with you
- Your repo, built from a Dockerfile, buildpacks, or a Procfile.
- Your environment variables and secrets.
- CapRover’s one-click Postgres, MySQL or MongoDB apps map to Railyard’s managed addons, with scheduled backups added.
- Your existing server: attach it over SSH rather than rebuilding it.
The move
- Attach your server: the one already running CapRover, or a new one Railyard provisions in your cloud account.
- Add your repo and select the build method that matches how CapRover 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. CapRover keeps serving until the cutover; there is no outage.
What’s different
Verified backups and point-in-time restore that CapRover doesn’t provide on its own, without losing the simple one-click deploy feel.