Nginx Proxy Manager vs Traefik vs Caddy: which reverse proxy for your homelab?

Once you’re running more than one or two services, you need a reverse proxy: the single thing that answers on ports 80/443, terminates HTTPS, and routes budget.yourdomain.net to one container and photos.yourdomain.net to another. Three tools dominate the homelab world — Nginx Proxy Manager, Traefik, and Caddy — and they represent three genuinely different philosophies. Here’s how to choose.

Nginx Proxy Manager (NPM): the point-and-click one

NPM wraps nginx in a friendly web UI. You add a “proxy host” through a form — domain, target container, port — click a box for a Let’s Encrypt certificate, and you’re done.

  • Best for: people who want a GUI and don’t want to touch config files. It’s the fastest way to get from “I have a container” to “it’s live at a subdomain with HTTPS.”
  • The trade: the state lives in NPM’s database, not in a file you version — so it’s less “infrastructure as code” and more “click ops.” For a home setup that you tweak occasionally, that’s often exactly right.

If you like clicking a form and seeing a green padlock, this is the gentlest on-ramp, and it’s what a lot of homelabs (this one included) run happily for years.

Traefik: the automatic one

Traefik discovers services automatically. You add a few labels to a container in your Docker Compose file, and Traefik picks it up, routes to it, and provisions a cert — no separate config step at all. Spin up a container, it’s routed; tear it down, the route disappears.

  • Best for: dynamic setups where containers come and go, and people who want their routing defined right alongside the container in Compose.
  • The trade: the learning curve is real. The label syntax and the middleware model take a weekend to click, and when something doesn’t route, debugging labels is less obvious than reading a plain config. Worth it once you’re past the hump.

Caddy: the simple-config one

Caddy is a proxy with automatic HTTPS built into its DNA and a famously readable config file. A working reverse proxy with a valid certificate can be two lines of Caddyfile. No plugin, no labels, no UI — just a tiny, legible text file.

  • Best for: people who like config-as-text but hate boilerplate. The Caddyfile is the most human-readable of the three by a wide margin, and HTTPS “just happens.”
  • The trade: no built-in GUI, and very dynamic Docker discovery needs a plugin. For a mostly-static set of services defined in a file, it’s hard to beat for clarity.

How to choose

  • You want a UI and minimal fuss: Nginx Proxy Manager.
  • Your containers are dynamic and you live in Compose: Traefik.
  • You like a clean text config and want the least boilerplate: Caddy.

There’s no wrong answer — all three give you automatic HTTPS and clean subdomain routing, which is the whole point. Pick the one whose workflow matches yours: clicking (NPM), labels (Traefik), or a tidy file (Caddy). And whichever you choose, put every service behind it on its own subdomain rather than juggling ports — here’s why and how.