
The Caddy web server obtains and renews HTTPS certificates for your public domain names by default, so there’s no renewal script to schedule and no certificate file to copy around. It’s free software under the Apache-2.0 licence, and it had about 79,000 stars on GitHub when we checked.
If you’ve ever lost an afternoon to an expired certificate, you know why that matters. Below: what Caddy does, how to get it, and where it falls short. This guide is based on the project’s README, its v2.11.9 release notes and the official website. We didn’t run our own tests or benchmarks.
What is the Caddy web server?
Caddy is a web server written in Go. The GitHub description calls it a “fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS.” The README adds that Go offers higher memory-safety guarantees than the languages behind some other servers.
In plain words: you point Caddy at a site, and it serves that site over HTTPS, the encrypted version of web traffic that gives you the padlock in your browser. The certificates behind that padlock are handled for you. The README’s tagline is “Every site on HTTPS.”
It’s also more than a file server. The README says Caddy is most often used as an HTTPS server, but it’s really a platform for running Go programs. Two “apps,” tls and http, ship standard with it.
As of our research, the repository was created on January 13, 2015, the latest release was v2.11.9 (November 5, 2026), and the last recorded activity was November 19, 2026. The repo also shows 288 open issues and about 5,300 forks. That looks like an actively maintained project, not an abandoned one.

Why use Caddy? Real use cases
Here’s where the README and website say Caddy fits.
- A public site without certificate chores. The README says automatic HTTPS uses ZeroSSL and Let’s Encrypt for public names. The website says Caddy obtains and renews certificates for all your sites by default.
- Internal names and IP addresses. For these, the README says Caddy uses a fully managed local certificate authority (CA), the organization or software that vouches for a certificate.
- Several servers working together. The README says Caddy can coordinate with other Caddy instances in a cluster.
- PHP and WordPress sites. The release notes mention FastCGI (the protocol Caddy uses to talk to PHP) and WordPress admin paths like
/wp-admin/, so PHP hosting is clearly a real-world use. - Browsable file listings. The release notes describe a
file_server browsedirective and a newplain_time_formatoption for plain-text directory listings. - In front of other apps. The repo’s topics include
reverse-proxy, which means Caddy can sit in front of an app and forward requests to it.

Key features of Caddy
Four ways to configure it
The Caddyfile is the easy, human-friendly format. Native JSON config is the more powerful one. A JSON API lets you change the config of a running server, and config adapters exist if you’d rather not write JSON.
Automatic HTTPS and modern protocols
Besides the certificate sources above, the README lists multi-issuer fallback (trying another provider if one fails) and Encrypted ClientHello (ECH) support. HTTP/1.1, HTTP/2 and HTTP/3 are all on by default.
Few dependencies, modular design
The README says Caddy runs anywhere with no external dependencies, “not even libc.” Its modular architecture is meant to let Caddy do a lot without bloat.
Production claims, with a grain of salt
The README says Caddy stays up when other servers go down because of TLS or certificate-related problems. It also claims production use after “trillions of requests” and millions of managed certificates. Those are the project’s own statements, not independent measurements.
How to install the Caddy web server
The README calls the simplest cross-platform route downloading Caddy from GitHub Releases and placing the executable in your PATH, the list of folders your system searches for programs. For other methods, it points to the online install documentation.
The README doesn’t list run commands, so we won’t invent any. Its advice for every user, whatever the experience level, is to work through the official Getting Started guide. If you only have a minute, the site also has several quick-start tutorials.
Build Caddy from source
You’ll need Go 1.26.0 or newer. The README’s development steps are:
git clone "https://github.com/caddyserver/caddy.git"
cd caddy/cmd/caddy/
go build
The README warns these steps won’t embed proper version information. For that, or to add plugins, it recommends its builder tool, xcaddy:
xcaddy build
To run the tests in all modules, or in one:
go test ./...
go test ./modules/caddyhttp/tracing/
Low ports on Linux
Caddy may try to bind to low ports unless your config says otherwise. If your OS requires elevated privileges for that, the README gives this Linux command:
sudo setcap cap_net_bind_service=+ep ./caddy
If you prefer go run, which creates temporary binaries, the README uses the included script:
go run -exec ./setcap.sh main.go
The README also says its authors are only qualified to document Caddy, not your computer, so be careful with system-level changes.
Limitations: who should skip Caddy
This section is our take, based on the notes rather than hands-on testing.
- Plugins mean building your own binary. The README adds plugins through xcaddy or a custom Go build. Its manual steps end with
go build -tags=nobadger,nomysql,nopgx. If you want a plugin menu you can click through, that’s a hurdle. - You must keep it updated. The v2.11.9 notes call it a quick follow-up to 2.11.8 that fixed a regression and “a few more security issues, mostly in FastCGI.” That’s good maintenance, but it means patching matters.
- PHP users should check their version. In 2.11.8, a request like
/wp-admin/was matched by the directory instead of itsindex.php, so it usually returned a 404. The upgrade step is simple: be on v2.11.9 or later. The project specifically recommends upgrading if you’re on 2.11.8 and serve PHP. - Migrating has a cost. If your team has years of configs for another server, moving them takes time. The notes don’t promise a drop-in conversion.
- It still has a learning curve. The README asks everyone to read the Getting Started guide, even after a quick-start tutorial.
- Funding comes from sponsors. The README describes Caddy as a ZeroSSL project, and the website says the software relies on sponsorships to survive. That’s common in open source, but worth knowing if your business depends on it.
As for alternatives, the notes don’t name any competing servers, so we won’t compare features here.
Caddy web server FAQ
Is Caddy free?
Yes. The website calls it free software, and the repository lists the Apache-2.0 licence.
Does Caddy support HTTP/3?
Yes. The README says HTTP/1.1, HTTP/2 and HTTP/3 are all supported by default.
Where do Caddy’s certificates come from?
For public names, the README lists ZeroSSL and Let’s Encrypt. For internal names and IPs, Caddy uses a fully managed local CA.
Which platforms does Caddy run on?
The project describes itself as multi-platform, and the README says it runs anywhere with no external dependencies. The notes don’t list specific operating systems, so check the install docs for yours.
Which version is current?
As of our research, v2.11.9, released November 5, 2026. Besides the PHP directory-index fix, it makes path matchers with placeholders like {env.FOO} behave as expected.
Where to start
Download the binary from the releases page, put it in your PATH, and follow the Getting Started guide on a throwaway domain or on localhost before you touch production. If you serve PHP, confirm you’re on v2.11.9 or later.
Links: the GitHub repository, the official website, the documentation and the community forum.
Sources
- caddyserver/caddy on GitHub (github.com)
- Release v2.11.9 (github.com)
- Caddy – The Ultimate Server with Automatic HTTPS (official site) (caddyserver.com)
This article was researched and drafted with AI assistance and reviewed against the linked sources by the Nexonic editorial team.
Join the conversation