Disclosure: I’m part of the CDNCA project team, and this post was written with AI assistance (reviewed by me).
CDNCA — CDN nodes, plugin marketplace — one control plane to run your CDN platform. Marketplace features roll out by version.
Why I’m sharing here: many of us use Caddy as a reverse proxy on a handful of edge boxes. Once you have many domains across several machines, keeping certificates, upstreams and cache rules consistent gets painful. CDNCA aims to manage that from a single control plane.
- Community Edition is open source (AGPL-3.0), self-hostable, no activation.
- Nodes: build your own, or later subscribe via the node marketplace (suppliers) as that ships.
- Plugin marketplace features roll out by version — see release notes.
Setup: please follow the site / README Quick Start; I won’t paste install commands in the thread. CE is free and open source; commercial details will be announced separately. CDNCA is an independent project, not affiliated with other CDN panels.
Feedback I’d value: what hurts most when you run your own edge nodes with Caddy — cert sprawl, upstream health, cache purge, or observability?
https://www.cdnca.com · GitHub - CDNCA/cdnca: CDN nodes, plugin marketplace — one control plane to run your CDN platform (open-core). Community Edition: AGPL-3.0. · GitHub