Migrate
Migrate to Railyard.
Every migration works the same way: deploy next to your current platform, test it on a temporary URL, then switch DNS. Your app stays online the whole time. Pick your starting point.
From Heroku
The dyno bill climbs with every process and add-on, the free tier is gone, and none of it is yours.
Read the guide →From Hatchbox.io
Same bet, your servers, push to deploy, but a thinner layer, and a one-person project with an uncertain future.
Read the guide →From Cloud 66
The same BYO-server model, but closed, heavier, and priced for bigger teams.
Read the guide →From Render
Lovely DX, but it's Render's infrastructure, Render's regions, and Render's bill.
Read the guide →From Fly.io
Great machines, but Fly's regions, Fly's bill, and Postgres you end up running yourself anyway.
Read the guide →From Railway
Great for getting started; usage-based pricing gets unpredictable, and there's no "run it on my own box" path.
Read the guide →From Anywhere else
Fly, App Platform, Coolify, Dokku, a hand-rolled VPS. The shape of the move is the same.
Read the guide →Steps
Every migration follows the same six steps.
- 01 Add a server: one you have, or one Railyard creates in your cloud account.
- 02 Add your repo. Dockerfile, buildpacks or Procfile are read as they are.
- 03 Bring your environment variables. Attach Postgres, MySQL or Redis with the connection strings set for you.
- 04 Deploy to a temporary URL and test it.
- 05 Restore your database dump into the managed addon.
- 06 Switch DNS. The old platform serves until the record changes, then you cancel it.
Don't delete the old app until real traffic is reaching Railyard. Keep the old platform for a week, then cancel it.
Deploy next to your current platform, then switch.
Start on the Free plan or a 14-day Pro trial, no card. Nothing moves until you point DNS at it.
Free plan, no card, and 14 days of Pro for every new team. One flat price per team.