← All migration guides
Coming from Neon
Neon is a serverless Postgres database on its own infrastructure, not a place to run your app. Railyard runs your actual application on a server you own, with managed Postgres alongside it.
Why teams pair Neon with something else
Neon is a strong serverless Postgres with branching and autoscaling. It’s a database, not an application platform — your app still needs somewhere to run, which is where Railyard comes in.
If you’re moving away from Neon’s database itself rather than just your app, Railyard’s managed Postgres addon gives you scheduled backups and point-in-time restore on a server in your own cloud account.
What comes with you
- Your application code, built from a Dockerfile, buildpacks, or a Procfile.
- Your environment variables and secrets.
- Your Postgres schema and data, dumped from Neon and restored into Railyard’s managed Postgres addon.
The move
- Attach a server: an existing one, or a new one Railyard provisions in your cloud account.
- Add your repo and attach a managed Postgres addon.
- Migrate your data with a dump and restore from Neon.
- Deploy to a temporary URL. Run your release task and verify.
- Move DNS. There is no outage; Neon keeps serving until the cutover.
What’s different
Your database and your application both live in your own cloud account, instead of your app running elsewhere and connecting out to Neon’s infrastructure.