Pros
Why teams pick it
- Dockerfile-based Next.js deployment works well; requires more configuration than Vercel but gains container control.
- Works via standard Postgres connection strings; region alignment matters for latency.
- External Supabase connections work; Fly's built-in Postgres may be preferred for latency-sensitive workloads.
- flyctl integrates cleanly into CI pipelines; official GitHub Actions are well-maintained.