← All migration guides
Coming from Laravel Cloud
Laravel Cloud runs your app on the Laravel team's own AWS infrastructure, billed by usage. Railyard runs the same Laravel app on a server in your own cloud account, at a flat price per team.
Why teams leave Laravel Cloud
Laravel Cloud is a well-built, fully managed platform from the people who build Laravel. The friction shows up in ownership and cost: your app runs on their AWS account, not yours, and the bill moves with usage as you scale.
Railyard keeps the same git-push deploy workflow for Laravel but runs it on a server in your own DigitalOcean, Hetzner or Vultr account, at a flat price per team.
What comes with you
- Your Laravel repo, built from a Dockerfile or buildpacks.
- Your environment variables and secrets, previously set in Laravel Cloud’s dashboard.
- Managed Postgres, MySQL and Redis map directly to Railyard addons.
- Laravel Horizon and queue workers run the same way on a Railyard worker process.
The move
- Attach a server: an existing one, or a new one Railyard provisions in your cloud account.
- Add your repo and Railyard detects Laravel automatically.
- Bring your config and attach the datastores your app expects.
- Deploy to a temporary URL. Run
php artisan migrateand verify. - Migrate data with a dump and restore into the managed addon.
- Move DNS. Laravel Cloud keeps serving until the cutover; there is no outage.
What’s different
A flat price per team instead of usage-based billing, and your app runs in your own cloud account instead of Laravel Cloud’s.