Two 1 GB machines for availability (~$14/month in Amsterdam); 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.
From-price with commitment. 8 shared vCores, 24 GB RAM, 200 GB NVMe, unlimited traffic at 3 Gbps.
- Why it fits
- Traffic-heavy European projects that want unmetered bandwidth and an included IPv4 at rock-bottom prices.
- How deploys work
- You get root on a bare server: pick a distro or an app image (Docker, WordPress, cPanel) and set everything up yourself.
- The tradeoff
- Entirely self-managed, headline prices need a commitment, and support below premium tiers is slow.
- You install, secure, and back up the database yourself.
