Two machines for availability; databases and egress on top.
- Why it fits
- Dockerized apps that want low cost, fine control, or multi-region placement.
- How deploys work
- fly launch builds the image and deploys it; configuration lives in fly.toml and the flyctl CLI.
- The tradeoff
- You operate more of the stack yourself — especially the database.
2 vCPU, 4 GB RAM, 80 GB SSD, 3 TB transfer.
- Why it fits
- Developers who want a cheap server near their users, wherever those users are.
- How deploys work
- You get root on a fresh Linux server; setup and deploys are yours to script.
- The tradeoff
- Fully self-managed, and the hour-based billing model is less forgiving than per-second rivals.
- You install, secure, and back up the database yourself.
2 vCPU, 4 GiB RAM, 4 TB transfer; resize further as needed.
- Why it fits
- Developers comfortable with a Linux server who want predictable pricing and full control.
- How deploys work
- You get root on an Ubuntu server: install your runtime, or start from a 1-click image.
- The tradeoff
- You are the ops team — security updates, backups, and monitoring are on you.
- You install, secure, and back up the database yourself.