← All migration guides
Coming from Appliku
Appliku deploys Django apps to servers you own, priced per server. Railyard follows the same own-your-server model without limiting you to a single framework.
Why teams leave Appliku
Appliku is a genuinely good, focused take on the own-your-server model for Django. The friction shows up the moment a team has more than Django in its stack: a Rails API, a Node worker, a Go service — Appliku doesn’t cover them.
Railyard follows the same idea — your servers, your cloud account — across any framework or language that runs in a container.
What comes with you
- Your Django repo, built from a Dockerfile, buildpacks, or a Procfile.
- Your environment variables and secrets.
- Managed Postgres, MySQL and Redis map directly to Railyard addons.
- Your existing servers: attach them over SSH rather than rebuilding the fleet.
The move
- Attach a server: an existing one, or a new one Railyard provisions in your cloud account.
- Add your repo and select the build method that matches how Appliku builds it today.
- Bring your config and attach the datastores your app expects.
- Deploy to a temporary URL. Run your release task and verify.
- Migrate data with a dump and restore into the managed addon.
- Move DNS. Appliku keeps serving until the cutover; there is no outage.
What’s different
The same own-your-server model, but not limited to Django — useful the moment your stack grows beyond one framework.