Caddy vs Fabio

Caddy is an extensible server platform used as a web server or proxy, and it is self-hosted. By default, it obtains and renews TLS certificates for sites and redirects HTTP to HTTPS. Its reverse proxy supports HTTP, HTTPS, WebSockets, gRPC, and FastCGI, along with load balancing and health checks. Configuration options include JSON through a RESTful API, the Caddyfile, and other adapters. Compile-time plugins extend its static binary. DNS challenge integrations include Cloudflare, DigitalOcean, Route 53, and other providers through libdns. Caddy can run as a command-line process, system service, container, Kubernetes workload, or embedded component. The software is free, with no paywalled features; sponsorship plans add services and support while leaving the license unchanged. Free community help is available through a forum. Caddy says its TLS defaults meet PCI DSS, NIST, and HIPAA compliance requirements, and that dependencies are verified with Go modules and release artifacts are cryptographically signed.

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.