← All migration guides
Coming from Porter
Porter wraps your AWS account in a managed Kubernetes cluster, which carries its own floor cost before your app even runs. Railyard deploys to a plain server in the same account instead.
Why teams leave Porter
Porter is a real bring-your-own-cloud option, wrapping Kubernetes around your own AWS account. The friction is the floor cost: the EKS cluster underneath Porter is commonly cited around $225 a month on its own, before your app’s compute is even counted, plus Porter’s own per-resource fee.
Railyard deploys to a plain server in the same AWS account, with no cluster to pay for underneath it.
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: Railyard provisions a plain EC2 server in it instead of an EKS cluster.
The move
- Attach a server: a new one Railyard provisions in your existing AWS 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. Porter keeps serving until the cutover; there is no outage.
What’s different
No Kubernetes cluster sitting underneath your app racking up a floor cost before you’ve deployed anything, and a flat price per team instead of per-resource billing.