Fabio
github.com
- Free plan
- Windows
- macOS
- Linux
- Self-hosted
What Fabio is
Fabio is a self-hosted HTTP and TCP reverse proxy that uses Consul data to configure routing. Services can announce accepted paths with tags, and Fabio updates its routing table when Consul data changes, without restarting or reloading. Its main role is distributing incoming HTTP(S) and TCP requests from the internet to frontend services; it is not intended to route between frontend and backend services where Consul service discovery already covers that need. Routing tools include route-specific access control, authorization, customizable logs, redirects, compression, header and path changes, WebSockets, server-sent events, and transparent gRPC proxying. Fabio also supports TLS termination, dynamic certificate stores, HTTPS upstreams, raw TCP proxying, and TCP-SNI forwarding without re-encryption. Traffic shaping can direct a percentage of traffic upstream without requiring an instance count. A web UI shows the routing table, and metrics integrations include Graphite, StatsD/DataDog, and Circonus. Fabio is free open-source software, requires Consul for service discovery, and runs on Linux, macOS, and Windows. Deployment options include source, binaries, Docker, and Homebrew.
Who it suits
Fabio suits teams that need a self-hosted proxy for distributing internet traffic to frontend services, with Consul-driven routing. It is not intended for routing between frontend and backend services.
Good to know, and what to watch
- Updates routes as Consul data changes without reloads
- Supports HTTP(S), TCP, WebSockets, and gRPC proxying
- Dynamic certificate stores include Consul and Vault
- Web UI displays the current routing table
- Consul is required for service discovery
- Not intended for frontend-to-backend routing
- Upstream HTTPS certificates without matching SANs are not validated by newer builds
Plans
Every plan and priceFabio (open source)
Open source
The verdict
Fabio combines Consul-based route updates with HTTP and TCP proxy features, including TLS options and traffic shaping. Its intended scope is traffic to frontend services, not service-to-service routing.
What the maker publishes
- Automatic routing
- When a Consul service registers path tags, Fabio updates its routing table as soon as Consul data changes, without restarting or reloading. source
- Deployment
- The project README lists installation from source, prebuilt binaries, Docker, and Homebrew. source
- Integrations
- The features page lists Consul, Vault, Docker, Graphite, StatsD/DataDog, Circonus, Amazon ELB, and Amazon NLB support. source
- Integrations
- The project README says Fabio integrates with Consul, Vault, Amazon ELB, and Amazon API Gateway. source
- Live changes
- Fabio can hot reload its routing table without downtime and wait for requests to finish before shutting down. source
- Maintainer
- The project site says primary maintenance has been the responsibility of ENA and the user community since January 2020. source
- Maintenance
- The project site says primary maintenance has been the responsibility of Education Networks of America and the user community since January 2020. source
- Metrics
- The feature page lists support for Graphite, StatsD/DataDog, and Circonus metrics. source
- Notable limit
- The deployment page says Fabio is currently not used as a frontend-to-backend or backend-to-backend router because Consul service discovery already solves that problem. source
- Operations
- Fabio provides a web UI for examining the current routing table and supports metrics integrations. source
- Primary use
- Fabio is intended to distribute incoming HTTP(S) and TCP requests from the internet to frontend services. source
- Primary use case
- The main use case is distributing incoming HTTP(S) and TCP requests from the internet to frontend services. source
- Product
- Fabio is an HTTP and TCP reverse proxy that configures its routing from Consul data. source
- Proxy features
- Fabio supports transparent gRPC proxying, HTTP compression, header injection, redirects, path prepending and stripping, WebSockets, and server-sent events. source
- Purpose
- Fabio is an HTTP and TCP reverse proxy that configures itself with data from Consul. source
- Routing features
- Features include route specific access control, customizable access logs, authorization mechanisms, and HTTP redirects. source
- Security
- The README says release hashes are signed with a PGP key and describes TLS certificate verification behavior for upstream HTTPS connections. source
- Security detail
- The README says binary release hashes are signed with a PGP key and notes that HTTPS upstream certificates without matching SAN extensions are not validated by newer builds. source
- Service mesh limits
- The documentation says Fabio is currently not used to route traffic among frontend and backend services because Consul service discovery already handles that use case. source
- Service tags
- Registered services use tags such as `urlprefix-/user` to announce the paths they accept. source
- TCP and protocols
- Fabio supports raw TCP proxying, TCP-SNI forwarding without re-encryption, and transparent gRPC proxying. source
- TLS
- Fabio supports dynamic certificate stores using files, HTTP servers, Consul, or Vault, and can forward HTTPS upstream requests. source
- TLS and certificates
- Fabio supports HTTPS upstreams, TCP-SNI proxying, TLS termination, and dynamic certificate stores including filesystem, HTTP server, Consul, and Vault. source
- Traffic handling
- Traffic shaping can forward a percentage of traffic upstream without knowing the number of instances. source
Checked against the maker's pages on 11 Oct 2026.