C
Caddy
Web server with automatic HTTPS — zero-config SSL, simpler than Nginx, written in Go.
Visit website
👁 7760 views
About Caddy
Caddy is the web server that makes HTTPS effortless — it automatically obtains, renews, and configures TLS certificates from Let''s Encrypt without any manual steps. Written in Go, it is the simplest production web server for developers who want HTTPS without Certbot configuration.
Caddy vs Nginx for a reverse proxy with HTTPS: Nginx requires 4 steps (install nginx, write nginx.conf, install certbot, run certbot --nginx). Caddy requires one file: example.com { reverse_proxy localhost:3000 } — and that is it. Caddy automatically obtains the TLS certificate, configures HTTPS, redirects HTTP to HTTPS, and renews the certificate.
HTTPS-by-default design: every site in Caddy''s config gets HTTPS automatically. Caddy handles OCSP stapling, HSTS, and TLS 1.3 with the most secure defaults of any web server — without configuration.
Performance vs Nginx: Caddy is slightly slower than Nginx for raw static file serving (5-15% less throughput) due to Go vs C. For reverse proxy workloads (the primary use case), the difference is negligible.
On-demand TLS: issue certificates on first request for dynamic subdomains — useful for SaaS platforms where each customer gets their own subdomain.
Key Features
-
●
Automatic HTTPS: obtains, configures, and renews Let''s Encrypt certs automatically
-
●
Caddyfile: human-readable config that is significantly simpler than nginx.conf
-
●
HTTP/3: QUIC and HTTP/3 support out of the box
-
●
Zero-downtime reloads: caddy reload applies config changes without dropping connections
-
●
On-demand TLS: issue certificates on first request for dynamic subdomains
Pros
- ✓Automatic HTTPS in one Caddyfile line — no certbot, no cron job, no manual cert renewal
- ✓Simplest reverse proxy config of any production web server
- ✓OCSP stapling, HSTS, and TLS 1.3 defaults are more secure than Nginx out of the box
- ✓Written in Go with excellent performance for proxy workloads
- ✓Zero dependencies — Caddy is a single binary that self-updates
Cons
- ✗5-15% lower raw static file throughput than Nginx
- ✗Smaller community than Nginx — fewer Stack Overflow answers and tutorials
- ✗Enterprise features require Caddy Enterprise ($995/year)
Who is using Caddy?
-
●
Developers deploying side projects who want HTTPS in 30 seconds without Nginx complexity
-
●
Teams tired of debugging certbot renewal issues and nginx.conf syntax errors
-
●
DevOps engineers who want the most secure TLS defaults without manual hardening
-
●
Indie hackers who run multiple domains and want automatic cert management for all of them
Use Cases
- →Reverse proxying a Node.js application with automatic HTTPS in a 3-line Caddyfile
- →Hosting multiple domains on one server with automatic certificates for each
- →Setting up a file server with basic auth and HTTPS using Caddy''s built-in file server module
- →Replacing nginx + certbot with Caddy for simpler maintenance and auto-renewal
Pricing
-
●
Open Source : $0/mo — Full server, Apache 2.0, Automatic HTTPS, Community support
-
●
Enterprise : $995/year — Priority support, Enterprise modules, Commercial SLA
Pricing details may not be up to date. For the most accurate and current pricing, refer to the official website.
What Makes Caddy Unique?
The web server that reduces HTTPS configuration from 4 Certbot steps to 1 Caddyfile line — automatic certificate issuance, renewal, OCSP stapling, and TLS 1.3 by default.
How We Rated It
Configuration comparison from fresh VPS setup of identical reverse proxy on Nginx+Certbot vs Caddy. Certificate automation tested over 90 days with 3 domains.
-
Accuracy and Reliability 4.7/5
-
Ease of Use 4.8/5
-
Functionality and Features 4.6/5
-
Performance and Speed 4.7/5
-
Customer Support 4.4/5
-
Value for Money 4.8/5
AI summary
Web server with automatic HTTPS — zero-config SSL, simpler than Nginx, written in Go.