Envoy Proxy vs Fabio

Envoy Proxy is a free, open-source proxy for edge traffic and service-to-service communication in cloud-native and AI-native applications. It runs as a self-contained process outside the application and can serve software written in different languages. Envoy handles HTTP/1.1, HTTP/2, gRPC, and HTTP/3, with HTTP/3 documented as alpha. Traffic features include routing, retries, circuit breaking, rate limiting, request shadowing, and outlier detection. It exposes subsystem statistics, an administration interface, and distributed tracing through third-party providers. Security features include TLS, JWT, role-based access control, and OAuth-related authorization and authentication. Operators must configure protections such as watermarks, overload management, and circuit breakers for availability resilience. Installation options include Docker images for amd64 and arm64, macOS Homebrew, and static binaries. Its API is compatible with Envoy Gateway and Istio.

Fabio is a self-hosted HTTP and TCP reverse proxy that builds its routing from Consul service data. Services can announce accepted paths with tags such as `urlprefix-/user`; Fabio then refreshes its routing table when Consul changes, without restarting or reloading. Its main role is distributing incoming HTTP(S) and TCP traffic from the internet to frontend services. It is not intended for frontend-to-backend or backend-to-backend routing, where Consul service discovery is used instead. Fabio provides route-specific access control, authorization, customizable logs, redirects, compression, header injection, path changes, WebSockets, server-sent events, and transparent gRPC proxying. It supports TLS termination, dynamic certificate stores, HTTPS upstreams, raw TCP, TCP-SNI forwarding, and traffic shaping by percentage. A web UI shows the active routes, with metrics integrations. Fabio is free, open-source software for Linux, macOS, and Windows, and requires Consul for service discovery.