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 unless you pay for Managed Postgres.
2 vCPU, 4 GB RAM, 80 GB SSD, 3 TB transfer.
- Free option
- Limited early-access plan: 1 vCPU, 512 MB RAM, and 10 GB disk in Seattle, Frankfurt, or Miami. Confirm access in your account before relying on it.
- 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.
Incl. 19% VAT. 8 shared vCores, 16 GB RAM, 512 GB NVMe, unmetered traffic.
- Why it fits
- European projects that want the most NVMe and RAM per euro and can live with German contract formalities.
- How deploys work
- You get root on a bare server: bring your own setup; the Server Control Panel handles images, snapshots, and a remote console.
- The tradeoff
- Best-in-class specs per euro, but 12-month terms, strict signup checks, and an unforgiving abuse process.
- You install, secure, and back up the database yourself.
