Caddy

Powerful, enterprise-ready, open source web server with automatic HTTPS.

Healthy · 70
70/100
Healthy

Actively maintained with regular releases.

Maintenance 21/40
Releases 21/25
Community 20/20
Momentum 8/15

Commit activity more than 53% of tracked projects; popularity in the top 1%. How this is calculated.

Commits, last 11 months

2025-10: 24 commits 2025-11: 12 commits 2025-12: 19 commits 2026-01: 16 commits 2026-02: 53 commits 2026-03: 36 commits 2026-04: 33 commits 2026-05: 37 commits 2026-06: 26 commits 2026-07: 23 commits 2026-08: 29 commits
2025-10 308 total 2026-08
Stars76k
Latest releasev2.11.4 · 3 Jun 2026
Repo updated26 Sept 2026
LicenceApache-2.0
Built withGo, deb, Docker

Is Caddy actively maintained?

Over the last 11 months the project absorbed 308 commits, of which 78 arrived in the most recent quarter — roughly 26 commits a month.

The most recent tagged release, v2.11.4, is about 4 months old.

Caddy ranks #10 of 19 in Web Servers, placing it mid-table for maintenance activity.

What Caddy actually does

Caddy is an open source web server designed to handle HTTP traffic with built-in, automated TLS certificate management. Written in Go, it can be run as a containerised service or installed via standard package managers like deb. It simplifies the setup and maintenance of web services by automating HTTPS configuration out of the box.

Best fit: It is a strong fit if you want a modern web server that manages TLS certificates automatically without complex external tooling like Certbot.

Worth knowing: Migrating complex routing and security rules from established alternatives like Nginx or Apache may require rewriting configuration syntax to match Caddy's structure.

Deployment notes

You will typically run this via Docker or a deb package, ensuring persistent storage is mounted for your site files and certificate cache.


Caddy as a replacement for


Alternatives to Caddy

Projects in the same categories, ordered by health score.