A · leads
netdata
94.1
81,443 stars · GPL-3.0
Databases
netdata leads by 6.3 · narrow
A · leads
94.1
81,443 stars · GPL-3.0
B
87.8
9,761 stars · MIT
netdata versus tile38 is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Go. The composite score is 94.1 for netdata and 87.8 for tile38.
netdata has 81,443 GitHub stars to tile38's 9,761, a gap of 71,682 (8.34×). Forks are 6,738 for netdata and 626 for tile38. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 73.
Push history: netdata was last pushed on 17 November 2026 (0 days ago), and tile38 was last pushed on 14 November 2026 (3 days ago). Open issues stand at 458 for netdata (0.006 per star) and 165 for tile38 (0.017 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. tile38 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 tile38. This is a procurement signal, not legal advice.
In Databases, both netdata (81,443 stars) and tile38 (9,761 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, tile38 is open source.
The lead is split. netdata is furthest ahead on fork community (100 to 73), while tile38 is furthest ahead on license flexibility (96 to 64). Choose the dimension a rollout cannot compromise on.
netdata finishes ahead at 94.1 against tile38 at 87.8, a 6.3 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 | tile38 |
|---|---|---|
| GitHub stars | 81,443 | 9,761 |
| Forks | 6,738 | 626 |
| Open issues | 458 | 165 |
| Adoption | 100 | 81 |
| Activity | 100 | 100 |
| Community | 100 | 73 |
| Issue health | 84 | 84 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.1 | 87.8 |
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
Real-time Geospatial and Geofencing
netdata has more GitHub stars: 81,443 versus 9,761 for tile38. The gap is 71,682 stars.
netdata was pushed more recently: 17 November 2026 versus 14 November 2026 for tile38. That is 3 days apart.
Yes. This catalog marks both netdata and tile38 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. tile38 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 tile38 scores 87.8. This page calls that a narrow lead for netdata.