A · leads
influxdb
89.4
31,816 stars · Apache-2.0
Databases
influxdb leads by 6.0 · narrow
A · leads
89.4
31,816 stars · Apache-2.0
B
83.4
77,588 stars · license n/a
influxdb versus redis 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; redis is written mainly in C. The composite score is 89.4 for influxdb and 83.4 for redis.
redis has 77,588 GitHub stars to influxdb's 31,816, a gap of 45,772 (2.44×). Forks are 3,826 for influxdb and 25,072 for redis. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 81 versus 100.
Push history: influxdb was last pushed on 17 November 2026 (0 days ago), and redis was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,175 for influxdb (0.068 per star) and 3,122 for redis (0.040 per star). Issue-health scores are 52 and 70; 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. 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. License scores in this pair are 96 for influxdb and 30 for redis. This is a procurement signal, not legal advice.
Only influxdb is marked self-hostable here (31,816 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: influxdb is open source, redis is unpriced in this catalog.
The lead is split. influxdb is furthest ahead on license flexibility (96 to 30), while redis is furthest ahead on fork community (100 to 81). Choose the dimension a rollout cannot compromise on.
influxdb finishes ahead at 89.4 against redis at 83.4, a 6.0 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 | redis |
|---|---|---|
| GitHub stars | 31,816 | 77,588 |
| Forks | 3,826 | 25,072 |
| Open issues | 2,175 | 3,122 |
| Adoption | 92 | 100 |
| Activity | 100 | 100 |
| Community | 81 | 100 |
| Issue health | 52 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 89.4 | 83.4 |
Scalable datastore for metrics, events, and real-time analytics
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.
redis has more GitHub stars: 77,588 versus 31,816 for influxdb. The gap is 45,772 stars.
Both were last pushed on 17 November 2026.
Only influxdb is marked self-hostable. redis is not.
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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
influxdb scores 89.4 and redis scores 83.4. This page calls that a narrow lead for influxdb.