Install caddy with Homebrew

Project links

• Homepage
• Repository

Commands and aliases

• caddy

Project history

Caddy's README says Matthew Holt began the project in 2014 while studying computer science at Brigham Young University. The project name reflects its role as a helper that carries the mundane work of serving the Web and keeps multiple concerns organized in one place.

The project differentiated itself by turning HTTPS from an operational chore into the default path. Caddy's feature list highlights automatic HTTPS with Let's Encrypt and ZeroSSL, managed local CAs for internal names, multi-issuer fallback, HTTP/1.1, HTTP/2, HTTP/3, and a plugin/module architecture. Caddy 2.0 was released as production-ready on May 4, 2020, after a redesign around a modular core, JSON config, API-driven reloads, and config adapters.

Adoption history

Caddy moved from developer-friendly web server to widely packaged infrastructure component because it solved TLS automation at the binary level. The official README states it has served trillions of requests and managed millions of TLS certificates, and GitHub shows a large contributor and user community.

Its packaging footprint reflects that adoption: the Homebrew input records Caddy across Homebrew, Debian, Ubuntu, Fedora, Arch, Alpine, Nix, MacPorts, Chocolatey, Scoop, winget, and openSUSE.

How it is used

Caddy is commonly used as an HTTPS static file server, reverse proxy, TLS terminator, local development server, and programmable HTTP platform. Users can run it with a Caddyfile, feed JSON through the admin API, adapt other config formats, or build custom binaries with modules using xcaddy.

Why package nerds care

Caddy matters to package nerds because it is a rare web server whose default install changes operational behavior: a plain binary can obtain and renew certificates, manage local trust, expose an API, and replace common nginx-plus-certbot setups with less glue. It also stresses packaging choices around service files, low-port binding, data directories, custom module builds, and reproducible Go binaries.

Timeline

• 2014: Matthew Holt begins developing Caddy.
• 2015: Caddy becomes known for automatic HTTPS by default.
• 2020-05-04: Caddy 2.0.0 is released as production-ready.
• 2020s: Caddy's module architecture, admin API, Caddyfile adapter, and automatic certificate management become its core packaged identity.
• 2026: GitHub README reports v2.11.x releases and continued active development.

Related projects

• Caddy is closely related to CertMagic, Let's Encrypt, ZeroSSL, xcaddy, and the Caddy module ecosystem. It is often compared with nginx, Apache httpd, Traefik, HAProxy, and certbot-based TLS automation stacks.

Sources

• https://caddyserver.com/docs/
• https://caddyserver.com/docs/architecture
• https://github.com/caddyserver/caddy#readme
• https://github.com/caddyserver/caddy/releases/tag/v2.0.0
• source_facts.package-manager