A
TDengine
92.3
25,194 stars · AGPL-3.0
Databases
Valkey leads by 2.3 · narrow
A
92.3
25,194 stars · AGPL-3.0
B · leads
94.6
27,730 stars · BSD-3-Clause
TDengine versus Valkey 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 C. The composite score is 92.3 for TDengine and 94.6 for Valkey.
Valkey has 27,730 GitHub stars to TDengine's 25,194, a gap of 2,536 (1.10×). Forks are 5,011 for TDengine and 1,540 for Valkey. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 86.
Push history: TDengine was last pushed on 15 November 2026 (2 days ago), and Valkey was last pushed on 17 November 2026 (0 days ago). Open issues stand at 454 for TDengine (0.018 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
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. Valkey is listed as BSD-3-Clause, 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 52 for TDengine and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both TDengine (25,194 stars) and Valkey (27,730 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: TDengine is open source, Valkey is open source.
The lead is split. TDengine is furthest ahead on issue health (84 to 70), while Valkey is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Valkey finishes ahead at 94.6 against TDengine at 92.3, a 2.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 | TDengine | Valkey |
|---|---|---|
| GitHub stars | 25,194 | 27,730 |
| Forks | 5,011 | 1,540 |
| Open issues | 454 | 1,045 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 86 |
| Issue health | 84 | 70 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.3 | 94.6 |
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
Valkey is a Linux Foundation key-value store forked from Redis. It is used as a cache, queue, and ephemeral data store under a permissive license.
Valkey has more GitHub stars: 27,730 versus 25,194 for TDengine. The gap is 2,536 stars.
Valkey was pushed more recently: 17 November 2026 versus 15 November 2026 for TDengine. That is 2 days apart.
Yes. This catalog marks both TDengine and Valkey as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. Valkey is listed as BSD-3-Clause, 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.
Valkey scores 94.6 and TDengine scores 92.3. This page calls that a narrow lead for Valkey.