Railway to Lander in 5 minutes.
Move from Railway's metered shared infrastructure to Lander's per-customer AWS Fargate. Predictable flat pricing, real isolation, WAF on every plan.[why customers switch]Railway's metered billing makes burn rate unpredictable; you want flat monthly pricing
[what stays the same]
- ✓Dockerfile-based deploys (Railway already uses Dockerfiles, so no config changes needed)
- ✓Push-from-GitHub workflow
- ✓Environment variables
[migration steps]
- step 1Free 7-day Pro trial. Hobby ($25/mo) gets you a real Fargate task with custom domains.
Sign up at lander.host
- step 2Most Railway services deploy to Lander unchanged because both use Dockerfiles.
Install GitHub App + import the same repo Railway was using
- step 3Dump from Railway: `pg_dump $DATABASE_URL > dump.sql`. Provision Lander Postgres by setting LANDER_NEEDS_DB=1 in env vars. Restore: `psql $DATABASE_URL < dump.sql` against the new Lander DATABASE_URL.
Migrate Postgres
pg_dump $DATABASE_URL > dump.sql # then in Lander dashboard, copy DATABASE_URL from env vars psql $LANDER_DATABASE_URL < dump.sql - step 4Railway CLI exports them: `railway variables --json`. Paste into Lander dashboard env-vars panel.
Copy env vars
- step 5Verify the Lander URL serves correctly, then update DNS at your registrar.
Push to deploy + flip CNAME
[gotchas · read first]
- !Railway's service-to-service networking (private DNS) doesn't exist on Lander — all Fargate tasks talk via public DNS / ALB.
- !Persistent volumes don't exist on Lander yet. If you used Railway volumes, switch to S3 or RDS.
- !Background workers as separate services need a sidecar Fargate task — open a ticket if you need help.
[other migrations]