Coming from Elestio
Elestio one-click deploys open-source and custom apps, billed per resource plus a support subscription. Railyard gives you the same deploy workflow with a flat price per team instead. Here's how to move.
Why teams leave Elestio
Elestio is a solid way to get an open-source app or a custom repo running fast, with managed backups and monitoring out of the box. The friction shows up as you grow: pricing is per resource plus a support-tier subscription, so the bill climbs with every service and server you add, and bringing your own cloud account is an option rather than the default path.
Railyard keeps the one-click deploy experience but prices per team, not per resource, and every server lives in your own DigitalOcean, Hetzner or Vultr account from the start.
What comes with you
- Your repo, built from a Dockerfile, buildpacks, or a Procfile.
- Your environment variables and secrets.
- Elestio’s automatic backups map to Railyard’s scheduled, verified database backups.
- Managed Postgres / MySQL / 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 pick the build method that matches how Elestio 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. The Elestio deployment serves until the cutover; there is no outage. Then decommission it.
What’s different
One flat price per team instead of a per-resource bill plus a support subscription, and every server is in your own cloud account from day one, not an optional add-on.