A · level
influxdb
94.7
31,816 stars · Apache-2.0
Databases
Too close to call · 94.7 to 94.5
A · level
94.7
31,816 stars · Apache-2.0
B · level
94.5
27,730 stars · BSD-3-Clause
influxdb versus Valkey 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; Valkey is written mainly in C. The composite score is 94.7 for influxdb and 94.5 for Valkey.
influxdb has 31,816 GitHub stars to Valkey's 27,730, a gap of 4,086 (1.15×). Forks are 3,826 for influxdb and 1,540 for Valkey. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 100 versus 89.
Push history: influxdb was last pushed on 17 November 2026 (0 days ago), and Valkey was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,175 for influxdb (0.068 per star) and 1,045 for Valkey (0.038 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. 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 96 for influxdb and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both influxdb (31,816 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: influxdb is open source, Valkey is open source.
The lead is split. influxdb is furthest ahead on fork community (100 to 89), while Valkey is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
Composite score: influxdb 94.7, Valkey 94.5. 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 | Valkey |
|---|---|---|
| GitHub stars | 31,816 | 27,730 |
| Forks | 3,826 | 1,540 |
| Open issues | 2,175 | 1,045 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 100 | 89 |
| Issue health | 52 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 94.5 |
Scalable datastore for metrics, events, and real-time analytics
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.
influxdb has more GitHub stars: 31,816 versus 27,730 for Valkey. The gap is 4,086 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both influxdb and Valkey 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. 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.
Neither tool clears a one-point margin. influxdb scores 94.7 and Valkey scores 94.5.