Fly Machines vs Envoy Proxy
A detailed comparison to help you choose between Fly Machines and Envoy Proxy.
Quick Verdict
3.9/5
Fly Machines
0 reviews
4.2/5
Envoy Proxy
0 reviews
Envoy Proxy is rated higher (4.2 vs 3.9). Fly Machines are Fly.io's fast-starting virtual machines for containerised workloads. Start in 300ms, stop when idle to save costs. Used for auto-scaling web services and ephemeral compute. Envoy is an open source L7 proxy and service mesh foundation. Used as the data plane in Istio, AWS App Mesh, and Consul Connect. High performance, built for microservices and Kubernetes.
Fly Machines Fast-starting VMs for containerised apps at the edge | Envoy Proxy Cloud-native proxy and service mesh sidecar | |
|---|---|---|
| Overview | ||
| Rating | 3.9 (0 reviews) | 4.2 (0 reviews)✓ |
| Pricing model | usage-based | free |
| Starting price | From $2.19/mo | Free✓ |
| Best for | Developers who want fast-starting containers that scale to zero between requests at the edge, and teams building custom control planes on a VM-per-container API | Platform engineering teams on Kubernetes standardising ingress, mesh and egress traffic management on one open data plane, with the in-house or vendor expertise to own a control plane. |
| Features | ||
| IPv6 | ✓ | |
| DDoS protection | ||
| Automated backups | ||
| Snapshots | ||
| Managed option | ||
| Bare metal | ||
| GPU available | ||
| S3-compatible | ||
| Hourly billing | ✓ | |
| Free tier | ||
| Data-center locations | ||
| Regions | Netherlands, Sweden, France, Germany, UK, US, Canada, Brazil, South Africa, Japan, Singapore, Australia | — |
| Tags | ||
| Tags | free tiermanaged optioneu datacenterus datacenterapac datacenter | free tieropen source |
| Visit Fly Machines → | Visit Envoy Proxy → | |
Fly Machines
Pros
- + ~300ms VM boot with automatic stop when idle — real scale-to-zero economics for request-driven workloads
- + Billed by the second with a fully published rate card; smallest Machine $2.19/30 days running
- + Low-level lifecycle control via REST API: create, start, stop, clone, update, destroy per VM
- + 17 regions on Fly's own hardware with per-Machine region placement
- + Fast restart from stopped state — assembled rootfs stays on the worker host
Cons
- - Fly.io-only API and infrastructure — no orchestration portability
- - Running the raw API means building your own scaling, placement retry and health logic
- - Always-on and idle costs accumulate: stopped rootfs $0.15/GB/month, volumes $0.15/GB/month, dedicated IPv4 $2/month
- - Capacity limits per region and host can make Machine placement fail
- - No free tier — only a 2-VM-hour/7-day trial — and no uptime SLA outside Enterprise plans
Envoy Proxy
Pros
- + Free forever: Apache 2.0, no seats, no per-node licence, no usage metering
- + CNCF graduated with neutral governance and multi-vendor support options
- + xDS APIs are the de facto standard control-plane interface for service meshes and gateways
- + Depth of features: HTTP/3, gRPC-aware load balancing, circuit breaking, external auth, rate limiting, hot cert rotation
- + Documented support window (four minor versions patched) and a decade of production track record
- + Extensive observability hooks: stats, tracing headers, structured access logs
Cons
- - Configuration complexity is high; production-grade setups need a control plane or serious in-house expertise
- - No SLA or commercial support bundled — community support only
- - Sidecar overhead (latency and memory per proxy) is a real cost in large mesh deployments
- - C++ codebase narrows the pool of people who can debug core-level issues
- - Troubleshooting spans both Envoy docs and whatever control plane generates your config
Stay in the loop
Get weekly updates on the best new hosting and infrastructure providers, deals, and comparisons.
No spam. Unsubscribe anytime.