Caddy-Modular
Caddy-Modular builds and runs the latest Caddy web server precompiled with a custom selection of community plugins.
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
86/100 Excellent
- Maintained
- 100last commit 17 days ago
- Popular
- 9878,764 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- 100256 MB minimum RAM
Availability: platform listings confirmed today, links checked 23 days ago
- GitHub stars
- 78,764
- Open issues
- 276
- Last commit
- 2026-11-04
- Latest release
- v2.11.8
- License
- Apache-2.0
- Activity
- rising
Checked 17 days ago - source: GitHub (caddyserver/caddy)
Resources & Compatibility
Minimum requirements: 256 MB RAM.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Start Caddy with port 443 and the Docker socket Use the Docker Compose file or sample docker run command, and make sure port 443 is exposed and the Docker socket is mounted. The socket is how Caddy watches your other containers and creates routes; without it, your apps will not show up. source
- Label each app container with its domain Add Docker labels, which are metadata attached to a container, such as caddy=app.example.com and caddy.reverse_proxy={{upstreams 80}}. They tell Caddy which domain to serve and which container or port to send requests to; without them, the domain will not be set up. source
- Use internal TLS for quick local testing Add caddy.tls=internal to a service when you do not yet have a public domain or certificate ready. This lets Caddy serve HTTPS with a temporary local certificate, so you can test the proxy before connecting a real domain to port 443. source
Fetched 54 days ago - each note links to its source
Variants
Alternatives (7)
- Apache HTTP Server - Open-source HTTP server offering cross-platform support, modular architecture, secure configuration, robust content delivery, and extensive…
- BunkerWeb - BunkerWeb is a self-hosted, open-source web application firewall and NGINX-based web server that protects services with secure-by-default s…
- Microsoft IIS - Internet Information Services (IIS) for Windows® Server is a flexible, secure and easy-to-manage Web server for hosting anything on the Web.
- Træfik Proxy - The Cloud Native Application Proxy Simplify networking complexity while designing, deploying, and operating applications.
- lighttpd - Lighttpd is a secure, lightweight web server that uses memory and CPU more efficiently than comparable servers, with FastCGI, CGI, authenti…
- nginx - Nginx is an HTTP web server, reverse proxy, content cache, load balancer, TCP/UDP proxy, and mail proxy server.
- tsdproxy - TSDProxy is a Tailscale proxy for Docker containers that automatically creates Tailscale machines for labeled containers, providing automat…
Checked 54 days ago - source: AlternativeTo
Common questions
How do I tell Caddy which Docker container to proxy a domain to?
Add Docker labels to each app container, such as caddy=app.example.com and caddy.reverse_proxy={{upstreams 80}}. These labels tell Caddy which domain to serve and which container or port to send requests to.
Can I issue TLS certificates for internal names and IP addresses?
Yes, Caddy can fully manage a local CA for internal names and IPs. This lets it provide HTTPS for internal addresses rather than only public domains.
Can I manage Caddy’s running configuration through an API?
Caddy’s native configuration is a JSON document that can be exported and manipulated through a RESTful config API. This allows the running configuration to be managed online.
Why can’t Caddy bind the ports it wants?
Caddy may try to bind low ports unless your config specifies otherwise. If the OS requires elevated privileges for those ports, you need to give the Caddy binary permission to do so.
Answers sourced from caddyserver.com, github.com, github.com
Community
- NPM vs Caddy : r/selfhosted - Reddit (reddit)
- FAQ - Modular (forum)
- General - CADDY2K.com (forum)
- r/selfhosted on Reddit: Caddy seems to good to be true? I just set it ... (reddit)
Collected 47 days ago - public community threads