← All migration guides
Coming from Netlify
Netlify is built for static sites and JAMstack frontends on Netlify's own infrastructure. If your app needs a real backend, here's how to run it on a server you own.
Why teams leave Netlify
Netlify is excellent for a static site or a JAMstack frontend with edge functions. The friction shows up the moment your app needs a real backend: a worker, a long-running job, a WebSocket server, or anything that can’t fit inside a short-lived function on Netlify’s infrastructure.
Railyard runs your app as a long-lived process on a server you own, alongside the managed Postgres, MySQL or Redis it needs.
What comes with you
- Your repo, built from a Dockerfile, buildpacks, or a Procfile.
- Your environment variables and secrets.
- Netlify’s deploy previews map to Railyard’s preview environments per pull request.
- A static frontend can stay on Netlify; the backend moves to Railyard behind the same domain.
The move
- Attach a server: an existing one, or a new one Railyard provisions in your cloud account.
- Add your repo and let Railyard detect your framework, or point it at your Dockerfile.
- Bring your config and attach the datastores your app expects.
- Deploy to a temporary URL. Run your release task and verify.
- Move DNS for the backend route or subdomain. There is no outage.
What’s different
A real server for the parts of your app that need one, with HTTPS, zero-downtime releases and managed databases, at a flat price per team instead of per-invocation billing.