lead · github

Caddy: The Web Server That Handles HTTPS So You Don't Have To

Automatic certificate management and HTTP/3 built in. Deploy faster, manage less.

Caddy is a web server—the software that sits between your app and the internet, handling requests. Unlike older servers (nginx, Apache), Caddy automates the painful part: getting and renewing SSL certificates so your site runs over HTTPS. It also speaks HTTP/3, the newest protocol that's faster on mobile networks. You configure it with a human-readable text file instead of cryptic syntax. For solo founders or small teams shipping production apps, this cuts weeks of TLS debugging and certificate renewal headaches. You still need to manage it yourself (it's not fully managed like Vercel), but if you're running your own infra, Caddy removes a whole class of DevOps friction.

Share kit

Email subject

Caddy: HTTPS automation for builders who run their own servers

Email blurb

Web server with automatic certificate management and HTTP/3. Cuts deployment complexity; solid for teams shipping on their own infra. Mature, reliable, worth evaluating if you're currently managing certificates manually.

Caddy automates the TLS nightmare: certificates renew themselves, HTTP/3 works out-of-box, config is readable. If you're shipping production and managing your own servers, this saves you weeks of ops debt. Not novel anymore—it's table-stakes infra.

Infrastructure that doesn't require a dedicated ops person to stay sane. Caddy handles automatic HTTPS renewal and HTTP/3 natively—remove one class of production friction entirely. Built for teams shipping fast.

Just deployed a service behind Caddy and forgot about certificate renewal. That's the bar now—your web server handles HTTPS so automatically you stop thinking about it. Caddy's been doing this since ~2015, but it's worth saying: if you're still manually managing TLS or wiring Let's Encrypt plumbing yourself, you're solving a solved problem. HTTP/3 ships enabled. Reverse proxy, load balancer, static file server—all one binary, all one config format. The math: one Caddyfile beats three config files and a deployment script. Built it for this exact reason. https://github.com/caddyserver/caddy

if you're still manually renewing SSL certs in 2024 you're making your own life harder Caddy handles HTTPS renewal + HTTP/3 + reverse proxy in one config file one binary. one Caddyfile. done. https://github.com/caddyserver/caddy