Migration guides
Every guide below has the same four parts: what the app costs on both sides, the config file before and after, the gotchas that cost people an afternoon, and the cutover steps in the order you should do them. A small app takes about an hour. The DNS flip is the only step your users can see.
Wherever you are coming from, everything lands on European infrastructure, under one Danish company, MICCI, on one EUR invoice, with the GDPR data processing agreement signed at signup.
The five guides
- Migrate from RenderThe closest mapping of the five — render.yaml concepts carry over, and the Postgres dump streams straight across.
- Migrate from HerokuDynos become services, add-ons become managed databases, and the Procfile mostly survives the trip.
- Migrate from RailwaySame zero-config deploys; what changes is a flat monthly price and a region with a name on it.
- Migrate from VercelThe one with real work in it — serverless functions become an always-on Node server you can hold open.
- Migrate from Fly.iofly.toml splits into a hoststack.yaml and two service settings; secrets have to be re-entered, because Fly never shows them back.
Coming from somewhere else? There is nothing special about the five above — a repo HostStack detects, or one with a Dockerfile, deploys without a guide, and getting started is the whole procedure. For your framework’s build, start command and database wiring, see the deploy guides. Still deciding which platform to leave? The comparisons come first. Stuck mid-move, write to us — we answer.