A
redis
83.4
77,588 stars · license n/a
Databases
TDengine leads by 3.6 · narrow
A
83.4
77,588 stars · license n/a
B · leads
87.0
25,194 stars · AGPL-3.0
redis versus TDengine 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 83.4 for redis and 87.0 for TDengine.
redis has 77,588 GitHub stars to TDengine's 25,194, a gap of 52,394 (3.08×). Forks are 25,072 for redis and 5,011 for TDengine. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 84.
Push history: redis 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 3,122 for redis (0.040 per star) and 454 for TDengine (0.018 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
redis is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for redis and 52 for TDengine. This is a procurement signal, not legal advice.
Only TDengine is marked self-hostable here (25,194 stars, deploy score 100). redis is not (77,588 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: redis is unpriced in this catalog, TDengine is open source.
The lead is split. redis is furthest ahead on fork community (100 to 84), while TDengine is furthest ahead on self-hosting (100 to 35). Choose the dimension a rollout cannot compromise on.
TDengine finishes ahead at 87.0 against redis at 83.4, a 3.6 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 | redis | TDengine |
|---|---|---|
| GitHub stars | 77,588 | 25,194 |
| Forks | 25,072 | 5,011 |
| Open issues | 3,122 | 454 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 100 | 84 |
| Issue health | 70 | 84 |
| License | 30 | 52 |
| Self-hosting | 35 | 100 |
| Composite | 83.4 | 87.0 |
For developers, who are building real-time data-driven applications, Redis is the preferred, fastest, and most feature-rich cache, data structure server, and document and vector query engine.
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
redis has more GitHub stars: 77,588 versus 25,194 for TDengine. The gap is 52,394 stars.
redis was pushed more recently: 17 November 2026 versus 15 November 2026 for TDengine. That is 2 days apart.
Only TDengine is marked self-hostable. redis is not.
redis is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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.
TDengine scores 87.0 and redis scores 83.4. This page calls that a narrow lead for TDengine.