Migrate
Moving in is the easy part.
Every move has the same shape: deploy alongside your current platform, prove it on a temporary URL, then flip DNS. Nothing goes dark. Pick your starting point.
The A record flips once. Every request already in flight still lands.
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 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 →Six steps. One of them is "wait and watch."
- 01 Point Railyard at a server — yours, or one it provisions.
- 02 Add your repo. Dockerfile, buildpacks or Procfile, read as-is.
- 03 Bring env vars. Attach Postgres, MySQL or Redis — strings wired in.
- 04 Deploy to a temporary URL. Put it through its paces.
- 05 Restore your database dump into the managed addon.
- 06 Cut DNS. The old platform serves until the record flips — then cancel.
The rule that keeps it safe: never delete the old thing until real traffic has landed on Railyard. Keep the old platform paid up for a week, then cancel.
Deploy next to your current platform, then switch.
Your first server is free while you try it. Nothing moves until you point DNS at it.
Free for one server, forever. No credit card.