Fly.io to Lander in 5 minutes.
Move from Fly's edge Firecracker VMs to Lander's per-customer AWS Fargate. AWS-native compliance, predictable flat pricing, WAF on every plan.[why customers switch]You need AWS-native compliance posture (SOC 2, HIPAA-ready) and don't need Fly's 30-region edge
[what stays the same]
- ✓Dockerfile-based deploys
- ✓Push-from-GitHub workflow
[migration steps]
- step 1Free 7-day Pro trial. Hobby covers 1 dynamic Fargate site.
Sign up at lander.host
- step 2fly.toml doesn't translate, but your container image does. Just push the same repo to Lander.
Bring your existing Dockerfile
- step 3Fly Postgres -> dump -> restore to Lander RDS. Same pg_dump / psql flow.
Postgres migration
- step 4Switch CNAME from your Fly anycast hostname to <slug>.app.lander.host.
Update DNS
[gotchas · read first]
- !Fly's Anycast IP / 30-region edge isn't matched by Lander (us-west-2 today). Multi-region is Q3 roadmap.
- !LiteFS / replicated SQLite has no Lander equivalent — switch to RDS Postgres.
- !Fly Machines (start/stop on demand) maps roughly to Fargate Spot but with different semantics.
[other migrations]