A · level
influxdb
93.1
31,816 stars · Apache-2.0
Databases
Too close to call · 93.1 to 92.9
A · level
93.1
31,816 stars · Apache-2.0
B · level
92.9
40,739 stars · Apache-2.0
influxdb versus tidb 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; tidb is written mainly in Go. The composite score is 93.1 for influxdb and 92.9 for tidb.
tidb has 40,739 GitHub stars to influxdb's 31,816, a gap of 8,923 (1.28×). Forks are 3,826 for influxdb and 6,297 for tidb. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 94 versus 100.
Push history: influxdb was last pushed on 17 November 2026 (0 days ago), and tidb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,175 for influxdb (0.068 per star) and 7,730 for tidb (0.190 per star). Issue-health scores are 52 and 34; activity scores are 100 and 100.
Both influxdb and tidb are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Databases, both influxdb (31,816 stars) and tidb (40,739 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, tidb is open source.
The lead is split. influxdb is furthest ahead on issue health (52 to 34), while tidb is furthest ahead on fork community (100 to 94). Choose the dimension a rollout cannot compromise on.
Composite score: influxdb 93.1, tidb 92.9. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | tidb |
|---|---|---|
| GitHub stars | 31,816 | 40,739 |
| Forks | 3,826 | 6,297 |
| Open issues | 2,175 | 7,730 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 94 | 100 |
| Issue health | 52 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.1 | 92.9 |
Scalable datastore for metrics, events, and real-time analytics
TiDB is built for agentic workloads that grow unpredictably, with ACID guarantees and native support for transactions, analytics, and vector search. No data silos. No noisy neighbors. No infrastructure ceiling.
tidb has more GitHub stars: 40,739 versus 31,816 for influxdb. The gap is 8,923 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both influxdb and tidb 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. tidb 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. influxdb scores 93.1 and tidb scores 92.9.