DeCDN Node
deCDN Node is the daemon that runs a deCDN cache node — bond funds, serve cached content, and get paid per megabyte — deployed on Kubernetes via a Helm chart…
Platform availability
Available on 1 of 9 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
53/100 Fair
- Maintained
- 98last commit 1 day ago
- Popular
- 176 GitHub stars
- Easy to install
- 101 install platform
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 6
- Open issues
- 8
- Last commit
- 2026-10-14
- Latest release
- node-collection-v0.3.0
- License
- MIT
- Activity
- rising
Checked today - source: GitHub (decdn/devops)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Node identity setup Start with the node-operator docs in the decdn/devops repo (docs/node-operators.md) to create and bond your node identity; the chart must persist that operator-provisioned identity in its data directory before it will start. source
Fetched today - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What should I use to deploy a deCDN node on Kubernetes?
Use the deCDN Helm chart for Kubernetes. It deploys one release per node, for a cache node or an origin.
What can go wrong when systemd stops a node that has already pulled data from another node?
After a node has completed at least one node-to-node pull, it can stay in router.shutdown() on SIGTERM until systemd sends SIGKILL at the 5-minute stop timeout.
How can I run a node with a self-hosted relay instead of the public relay map?
Set the single [network] relay_url, or the DECDN_RELAY_URL environment variable. When set, it swaps the public n0 relay map for one self-hosted relay.
What bond must a node post to join the deCDN peer mesh?
Nodes post a TOKEN capacity bond to join the peer mesh. It is scaled to declared bandwidth and is never below a global entry floor.
Answers sourced from docs.decdn.org, github.com, github.com, github.com
Community
- decdn-node hangs in router.shutdown () on SIGTERM after any ... - GitHub (forum)
- Namespace: decdn - Galaxy Namespace Requests - Ansible (forum)
Collected today - public community threads