A · leads
netdata
94.1
81,443 stars · GPL-3.0
Databases
netdata leads by 5.2 · narrow
A · leads
94.1
81,443 stars · GPL-3.0
B
88.9
25,279 stars · MIT
netdata versus turso 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; turso is written mainly in Rust. The composite score is 94.1 for netdata and 88.9 for turso.
netdata has 81,443 GitHub stars to turso's 25,279, a gap of 56,164 (3.22×). Forks are 6,738 for netdata and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 83.
Push history: netdata was last pushed on 17 November 2026 (0 days ago), and turso was last pushed on 17 November 2026 (0 days ago). Open issues stand at 458 for netdata (0.006 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 84 and 52; 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. turso is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 64 for netdata and 96 for turso. This is a procurement signal, not legal advice.
In Databases, both netdata (81,443 stars) and turso (25,279 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, turso is open source.
The lead is split. netdata is furthest ahead on issue health (84 to 52), while turso is furthest ahead on license flexibility (96 to 64). Choose the dimension a rollout cannot compromise on.
netdata finishes ahead at 94.1 against turso at 88.9, a 5.2 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 | turso |
|---|---|---|
| GitHub stars | 81,443 | 25,279 |
| Forks | 6,738 | 1,553 |
| Open issues | 458 | 1,714 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 100 | 83 |
| Issue health | 84 | 52 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.1 | 88.9 |
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
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
netdata has more GitHub stars: 81,443 versus 25,279 for turso. The gap is 56,164 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both netdata and turso 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. turso is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
netdata scores 94.1 and turso scores 88.9. This page calls that a narrow lead for netdata.