← All migration guides
Coming from Cloudflare Pages
Cloudflare Pages deploys static sites and edge functions on Cloudflare's network. If your app needs a traditional server-based backend, here's how to run it on a server you own.
Why teams leave Cloudflare Pages
Cloudflare Pages and its edge functions are fast for a static site or lightweight edge logic. The friction shows up when your app needs a real backend process: a worker, a long job, or a framework that expects a normal server rather than the edge runtime’s constraints.
Railyard runs that backend as a long-lived process on a server you own.
What comes with you
- Your repo, built from a Dockerfile, buildpacks, or a Procfile.
- Your environment variables and secrets.
- A static frontend can stay on Cloudflare Pages; 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.