A
dragonfly
84.5
31,878 stars · license n/a
Databases
Valkey leads by 11.6 · clear
A
84.5
31,878 stars · license n/a
B · leads
96.1
27,730 stars · BSD-3-Clause
dragonfly versus Valkey is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dragonfly is written mainly in C++; Valkey is written mainly in C. The composite score is 84.5 for dragonfly and 96.1 for Valkey.
dragonfly has 31,878 GitHub stars to Valkey's 27,730, a gap of 4,148 (1.15×). Forks are 1,294 for dragonfly and 1,540 for Valkey. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 98 versus 100.
Push history: dragonfly 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 209 for dragonfly (0.007 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
dragonfly 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. 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 30 for dragonfly and 96 for Valkey. This is a procurement signal, not legal advice.
Only Valkey is marked self-hostable here (27,730 stars, deploy score 100). dragonfly is not (31,878 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: dragonfly is unpriced in this catalog, Valkey is open source.
The lead is split. dragonfly is furthest ahead on issue health (84 to 70), while Valkey is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
Valkey finishes ahead at 96.1 against dragonfly at 84.5, a 11.6 point clear 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 | dragonfly | Valkey |
|---|---|---|
| GitHub stars | 31,878 | 27,730 |
| Forks | 1,294 | 1,540 |
| Open issues | 209 | 1,045 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 98 | 100 |
| Issue health | 84 | 70 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 84.5 | 96.1 |
A modern replacement for Redis and Memcached
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.
dragonfly has more GitHub stars: 31,878 versus 27,730 for Valkey. The gap is 4,148 stars.
Both were last pushed on 17 November 2026.
Only Valkey is marked self-hostable. dragonfly is not.
dragonfly 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. 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 96.1 and dragonfly scores 84.5. This page calls that a clear lead for Valkey.