Install first · Control package = console
After install, sign in with a browser and manage nodes, sites, users and plugins. One control plane runs the whole CDN. Prefer the one-liner so you rarely touch package names.
You need two things to run a CDN: the control plane (one console) and nodes (the edge that accelerates traffic). Community edition ships only these two — there is no separate “API node” package. Commercial packages ship separately.
Community edition — no activation · marketplace features open by version
After install, sign in with a browser and manage nodes, sites, users and plugins. One control plane runs the whole CDN. Prefer the one-liner so you rarely touch package names.
Install on machines that carry traffic. After the control plane is up, follow Nodes in the console — or subscribe on the node platform. Registration keys come from your control plane, not this site.
| Artifact | Version | Download |
|---|---|---|
cdnca-control-native.tar | v0.0.0-placeholder | Download · SHA256SUMS · artifacts.json |
Install the control plane → open the console → add nodes there. See the install docs for steps. Install docs
Script install-control.sh · control tarball cdnca-control-native.tar (fetched by the installer; browser direct links may 403) · node package cdnca-edge-agent.tar.gz · get / get-staging are planned aliases and currently unreachable · node install commands are generated in the control plane Nodes page.
The community download area does not ship Plus packages. Community needs only control + node — no third “API node” package.