Photoprism
AI-powered self-hosted photo management solution with automatic tagging, face recognition, and smart search capabilities for personal photo libraries.
Free SSL on autopilot: Caddy is an Apache-2.0 web server that issues, installs and renews its own trusted certificate for every domain.
Caddy is a free, open source web server and reverse proxy, licensed Apache-2.0, that gets its own SSL certificates. Give it a domain name and it requests a certificate, installs it, serves the site over HTTPS, renews the certificate in the background and redirects HTTP to HTTPS. No separate SSL tool, no renewal cron job.
Caddy activates certificate management when it learns a hostname it is meant to serve, from a site address in a Caddyfile, a host matcher in its JSON config, the --domain flag, or the automate loader. It then obtains a certificate from Let's Encrypt or ZeroSSL, proves domain control over port 80 or 443, and keeps the certificate renewed without being asked.
Two challenges are enabled by default: HTTP-01 on port 80 and TLS-ALPN-01 on port 443. Wildcard certificates need the DNS challenge instead, which requires a plugin and API credentials for your DNS provider.
The server is free, and so are the certificates. Let's Encrypt issues 90 day certificates at no cost, recommends renewing at 60 days, and Caddy handles that renewal on its own. ZeroSSL's free tier covers 3 certificates of 90 days, and its ACME endpoint is Caddy's configured fallback.
What you pay for is the hardware and the domain. A small VPS and a domain name are the only recurring costs, and the SSL layer adds nothing to either. Commercial certificate authorities still sell single domain certificates for real money, which is the bill Caddy removes.
| Item | Detail |
|---|---|
| Licence | Apache-2.0, checked in the repository's LICENSE file |
| Latest release | 2.11.9, published 5 November 2026 |
| GitHub stars | about 79,000, checked November 2026 |
| Platforms | Linux, Windows, macOS, FreeBSD, OpenBSD, NetBSD |
| HTTP versions | 1.1, 2 and 3, all enabled by default |
| Certificate authorities | Let's Encrypt and ZeroSSL, with automatic failover |
| Configuration | Caddyfile, native JSON, or the live HTTP admin API |
| Runtime dependencies | none, not even libc |
A machine you control, a domain whose A or AAAA record points at that machine, and ports 80 and 443 reachable from the internet, either directly or forwarded. Caddy also needs a writable, persistent home directory for certificates and keys. Lose that directory and it reissues everything, which can run into authority rate limits.
If those ports are closed, the DNS challenge still works with a provider plugin.
The certificate handling is the headline, but the rest of the server is what keeps people. A reverse proxy is one directive plus a backend address. Static files are another directive. PHP gets a single php_fastcgi line that builds a full FastCGI stack. Reloads are graceful with no dropped connections, and the running server accepts new config through its HTTP API instead of a restart.
Two instances sharing the same storage coordinate automatically, so a load balanced pair does not request the same certificate twice. localhost and bare IP addresses get a locally trusted certificate from Caddy's own root authority, which removes the mixed content warnings a plain HTTP dev server produces.
Certificates need reachable ports or a DNS plugin, so a locked down firewall is a real obstacle. Extensions are compile time: adding a module means rebuilding with xcaddy, not loading a shared library. There is no .htaccess and no per-directory config, the one Apache feature with no equivalent here. There is no admin interface, only a config file and an API. On-demand TLS, which issues a certificate during the TLS handshake, needs an "ask" endpoint you run yourself so strangers cannot burn your quota. Complex nginx configs do not convert cleanly, so a migration is usually a rewrite.
On Debian or Ubuntu, the official repository installs Caddy plus a systemd unit that starts on boot:
sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https curl
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list
sudo apt update && sudo apt install caddy
Then put your site in /etc/caddy/Caddyfile and reload:
example.com {
reverse_proxy localhost:3000
}
sudo caddy validate --config /etc/caddy/Caddyfile
sudo systemctl reload caddy
Docker users can pull the official caddy image, and Windows users can choco install caddy or scoop install caddy, though both of those packages are community maintained.
Yes, when it comes from a publicly trusted authority. Let's Encrypt and ZeroSSL certificates chain to roots that browsers and operating systems already trust, so visitors see a normal padlock. The old warnings about free certificates came from self-signed certificates, which nobody else trusts, and that is a different thing entirely.
Let's Encrypt issues certificates valid for 90 days by default and recommends renewing at 60. ZeroSSL's free certificates are also 90 days. Short lifetimes are deliberate: a stolen key stops working sooner. The catch is that something has to renew them, which is the job Caddy takes over.
Yes, with the DNS challenge. A wildcard covers every subdomain in one certificate, but Let's Encrypt requires DNS validation for it, so Caddy needs a plugin and credentials for your DNS provider. Without that, Caddy issues individual certificates per hostname instead, which is fine for most sites.
No. Caddy asks for the certificate itself, so there is no separate purchase, no certificate file to download and no renewal date to diarise. The only thing you buy is the server and the domain. A paid certificate authority is optional, not a requirement.
Caddy retries, switches challenge type, then tries its other configured authority, which is ZeroSSL when Let's Encrypt fails. It then backs off exponentially, up to one day between attempts, for up to 30 days. During Let's Encrypt retries it uses their staging endpoint so a broken config does not worsen a rate limit.
No. Caddy is a server you install on a machine you control, so it needs root access or the ability to bind ports 80 and 443. On shared hosting, the host issues and renews the certificate from their panel, and you install nothing.
Caddy also sits in our self-hosted section, next to the tools you would typically put behind it.
AI-powered self-hosted photo management solution with automatic tagging, face recognition, and smart search capabilities for personal photo libraries.
Self-hosted photo and video backup solution with mobile apps, facial recognition, automatic uploads, and Google Photos-like features for complete privacy.
Free open-source design tool with seamless responsive layouts, code inspection, and collaboration features for designers and developers.