Reverse proxy
front-load app servers with auto-SSL

// screenshot of caddyserver.com ↗
Caddy is a modern HTTP/2 + HTTP/3 web server with automatic HTTPS — Let's Encrypt certificate provisioning + renewal built-in, no manual setup. Simple Caddyfile config (vs nginx's terse syntax), Go-based single binary. Designed for the "set and forget" web server experience.
Caddy is a modern HTTP/2 + HTTP/3 web server with automatic HTTPS — Let's Encrypt certificate provisioning + renewal built-in, no manual setup. Simple Caddyfile config (vs nginx's terse syntax), Go-based single binary. Designed for the "set and forget" web server experience.
For developers who don't want to maintain certbot cron jobs or fight with nginx config files, Caddy is the answer.
Concrete scenarios where teams pick Caddy over the SaaS alternative.
front-load app servers with auto-SSL
serve docs sites, marketing pages, SPAs
Let's Encrypt + ZeroSSL with zero config
modern protocol support out of the box
Caddyfile vhost-style configs
If your team profile matches one of these, Caddy is a strong fit out of the box.
preferring simple config over nginx complexity
hosting their own sites without certbot wrangling
needing reverse proxy with auto-SSL
managing dozens of subdomains without per-cert hassle
wanting HTTPS-everywhere by default
When evaluating self-hosted options for this category, here are the dimensions on which Caddy consistently lands above the alternatives.
The stack you'll plug Caddy into — services, protocols, and adjacent apps in the BluixApps catalog.
caddy:2.8 (release-tagged)/data/caddy (cert storage)Operational guidance from running this in production — what to do before you scale, what to lock down, what surprises people.
/data/caddy holds certs + keys; mount volume so renewals persisthealth_uri directive avoids forwarding to unhealthy upstreamscaddy reload graceful reload; faster than nginx -s reload