A · leads
netdata
94.1
81,443 stars · GPL-3.0
Databases
netdata leads by 5.5 · narrow
A · leads
94.1
81,443 stars · GPL-3.0
B
88.6
25,194 stars · AGPL-3.0
netdata versus TDengine is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. netdata is written mainly in Go; TDengine is written mainly in C. The composite score is 94.1 for netdata and 88.6 for TDengine.
netdata has 81,443 GitHub stars to TDengine's 25,194, a gap of 56,249 (3.23×). Forks are 6,738 for netdata and 5,011 for TDengine. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 97.
Push history: netdata was last pushed on 17 November 2026 (0 days ago), and TDengine was last pushed on 15 November 2026 (2 days ago). Open issues stand at 458 for netdata (0.006 per star) and 454 for TDengine (0.018 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
netdata is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. TDengine is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 64 for netdata and 52 for TDengine. This is a procurement signal, not legal advice.
In Databases, both netdata (81,443 stars) and TDengine (25,194 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: netdata is open source, TDengine is open source.
netdata is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 12 points (64 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
netdata finishes ahead at 94.1 against TDengine at 88.6, a 5.5 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | netdata | TDengine |
|---|---|---|
| GitHub stars | 81,443 | 25,194 |
| Forks | 6,738 | 5,011 |
| Open issues | 458 | 454 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 100 | 97 |
| Issue health | 84 | 84 |
| License | 64 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 94.1 | 88.6 |
Full-stack observability · Metrics · Logs · Traces · Flows · Topology · Infrastructure · APM · NPM · DBM · RUM · Synthetics · Cloud · AI · OpenTelemetry · SNMP · NetFlow/IPFIX/sFlow · IPMI · Redfish · 800+ integrations
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
netdata has more GitHub stars: 81,443 versus 25,194 for TDengine. The gap is 56,249 stars.
netdata was pushed more recently: 17 November 2026 versus 15 November 2026 for TDengine. That is 2 days apart.
Yes. This catalog marks both netdata and TDengine as self-hostable. Confirm each project's deploy docs before you plan a migration.
netdata is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. TDengine is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
netdata scores 94.1 and TDengine scores 88.6. This page calls that a narrow lead for netdata.