A
rocksdb
90.9
32,285 stars · GPL-2.0
Databases
Valkey leads by 2.7 · narrow
A
90.9
32,285 stars · GPL-2.0
B · leads
93.6
27,730 stars · BSD-3-Clause
rocksdb versus Valkey is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. rocksdb is written mainly in C++; Valkey is written mainly in C. The composite score is 90.9 for rocksdb and 93.6 for Valkey.
rocksdb has 32,285 GitHub stars to Valkey's 27,730, a gap of 4,555 (1.16×). Forks are 7,033 for rocksdb and 1,540 for Valkey. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 83.
Push history: rocksdb 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 1,855 for rocksdb (0.057 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 52 and 70; activity scores are 100 and 100.
rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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 64 for rocksdb and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both rocksdb (32,285 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: rocksdb is open source, Valkey is open source.
The lead is split. rocksdb is furthest ahead on fork community (100 to 83), while Valkey is furthest ahead on license flexibility (96 to 64). Choose the dimension a rollout cannot compromise on.
Valkey finishes ahead at 93.6 against rocksdb at 90.9, a 2.7 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 | rocksdb | Valkey |
|---|---|---|
| GitHub stars | 32,285 | 27,730 |
| Forks | 7,033 | 1,540 |
| Open issues | 1,855 | 1,045 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 100 | 83 |
| Issue health | 52 | 70 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.9 | 93.6 |
A library that provides an embeddable, persistent key-value store for fast storage.
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.
rocksdb has more GitHub stars: 32,285 versus 27,730 for Valkey. The gap is 4,555 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both rocksdb and Valkey as self-hostable. Confirm each project's deploy docs before you plan a migration.
rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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 93.6 and rocksdb scores 90.9. This page calls that a narrow lead for Valkey.