A · leads
influxdb
94.3
31,816 stars · Apache-2.0
Databases
influxdb leads by 2.4 · narrow
A · leads
94.3
31,816 stars · Apache-2.0
B
91.9
25,194 stars · AGPL-3.0
influxdb versus TDengine is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. influxdb is written mainly in Rust; TDengine is written mainly in C. The composite score is 94.3 for influxdb and 91.9 for TDengine.
influxdb has 31,816 GitHub stars to TDengine's 25,194, a gap of 6,622 (1.26×). Forks are 3,826 for influxdb and 5,011 for TDengine. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 97 versus 100.
Push history: influxdb 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 2,175 for influxdb (0.068 per star) and 454 for TDengine (0.018 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
influxdb is listed as Apache-2.0, 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. 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 96 for influxdb and 52 for TDengine. This is a procurement signal, not legal advice.
In Databases, both influxdb (31,816 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: influxdb is open source, TDengine is open source.
The lead is split. influxdb is furthest ahead on license flexibility (96 to 52), while TDengine is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
influxdb finishes ahead at 94.3 against TDengine at 91.9, a 2.4 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 | influxdb | TDengine |
|---|---|---|
| GitHub stars | 31,816 | 25,194 |
| Forks | 3,826 | 5,011 |
| Open issues | 2,175 | 454 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 97 | 100 |
| Issue health | 52 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 94.3 | 91.9 |
Scalable datastore for metrics, events, and real-time analytics
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
influxdb has more GitHub stars: 31,816 versus 25,194 for TDengine. The gap is 6,622 stars.
influxdb was pushed more recently: 17 November 2026 versus 15 November 2026 for TDengine. That is 2 days apart.
Yes. This catalog marks both influxdb and TDengine as self-hostable. Confirm each project's deploy docs before you plan a migration.
influxdb is listed as Apache-2.0, 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. 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.
influxdb scores 94.3 and TDengine scores 91.9. This page calls that a narrow lead for influxdb.