Caddy dynamically managing thousands of domains as a reverse proxy?

I’m considering using Caddy as a reverse proxy, to automatically manage the https certificates of thousands of domains. An important part of this is being able to reload the server on the fly also.

I have some questions:

  1. Is this a reasonable, and good use for Caddy?

  2. My plan is to create a docker image that runs node.js. The nodejs application will talk to my server, and get notifications if there are any changes in the domains. It will then automatically generate and replace the Caddyfile, and then call caddy reload. Is there a better way to do this?

  3. How much CPU / Memory does this machine need? This won’t be getting many requests. I imagine it will be in the hundreds of requests per hour.

1 Like

Yes, use On-Demand TLS:


Oh wow, that seems perfect for what I’m looking for.

How powerful of a machine does it require?

1 Like

Not powerful at all. Caddy can run on Raspberry Pi etc.


I run caddy on a VM with the lowest specs I can do… 1 cpu, 1GB ram, and 2.5gb ram. Works great.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.