Coming from Ploi
Ploi is a lighter, cheaper server panel for Laravel, billed separately from the servers it manages. Railyard adds managed addons, zero-downtime releases and team roles on the same model.
Why teams leave Ploi
Ploi is a good, affordable take on the server-panel model: it provisions and manages a server you pay your cloud provider for directly. The friction shows up in what a panel alone doesn’t do: no managed database backups, no verify-then-swap zero-downtime releases, and no built-in team roles.
Railyard keeps the same server-you-own model with managed addons, zero-downtime releases and team roles added.
What comes with you
- Your repo, built from a Dockerfile or buildpacks.
- Your environment variables and secrets.
- Your existing server: attach it over SSH rather than rebuilding it.
- Managed Postgres, MySQL and Redis map directly to Railyard addons, with scheduled backups added.
The move
- Attach your server: the one Ploi already manages, or a new one Railyard provisions in your cloud account.
- Add your repo and select the build method that matches your app.
- 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. Ploi keeps serving until the cutover; there is no outage.
What’s different
Verify-then-swap zero-downtime releases, managed backups and real team roles, on the same server-you-own model Ploi already uses.