← All migration guides
Coming from Flightcontrol
Flightcontrol deploys to your AWS account over ECS only, with preview environments gated behind its $397-a-month Business plan. Railyard deploys to any cloud account with previews on every plan.
Why teams leave Flightcontrol
Flightcontrol is a solid way to deploy to your own AWS account over ECS. The friction is twofold: it’s AWS-only, and preview environments — a feature most teams want from day one — are gated behind its $397-a-month Business plan.
Railyard deploys to any cloud provider, with preview environments on every plan including Free.
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 AWS account, or a different provider if you’d rather move off AWS entirely.
The move
- Attach a server: a new one Railyard provisions in your AWS account, or any other provider you choose.
- 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. Flightcontrol keeps serving until the cutover; there is no outage.
What’s different
Preview environments on every plan instead of gated behind a $397-a-month tier, and the freedom to deploy outside AWS if you want to.