A
cockroach
78.0
32,622 stars · license n/a
Databases
Valkey leads by 16.3 · decisive
A
78.0
32,622 stars · license n/a
B · leads
94.3
27,730 stars · BSD-3-Clause
cockroach versus Valkey is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cockroach is written mainly in Go; Valkey is written mainly in C. The composite score is 78.0 for cockroach and 94.3 for Valkey.
cockroach has 32,622 GitHub stars to Valkey's 27,730, a gap of 4,892 (1.18×). Forks are 4,236 for cockroach 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 88.
Push history: cockroach was last pushed on 11 November 2026 (6 days ago), and Valkey was last pushed on 17 November 2026 (0 days ago). Open issues stand at 8,042 for cockroach (0.247 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 34 and 70; activity scores are 92 and 100.
cockroach 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 cockroach 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). cockroach is not (32,622 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: cockroach is unpriced in this catalog, Valkey is open source.
The lead is split. cockroach is furthest ahead on fork community (100 to 88), while Valkey is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
Valkey finishes ahead at 94.3 against cockroach at 78.0, a 16.3 point decisive 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 | cockroach | Valkey |
|---|---|---|
| GitHub stars | 32,622 | 27,730 |
| Forks | 4,236 | 1,540 |
| Open issues | 8,042 | 1,045 |
| Adoption | 100 | 98 |
| Activity | 92 | 100 |
| Community | 100 | 88 |
| Issue health | 34 | 70 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 78.0 | 94.3 |
CockroachDB — the cloud native, distributed SQL database designed for high availability, effortless scale, and control over data placement.
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.
cockroach has more GitHub stars: 32,622 versus 27,730 for Valkey. The gap is 4,892 stars.
Valkey was pushed more recently: 17 November 2026 versus 11 November 2026 for cockroach. That is 6 days apart.
Only Valkey is marked self-hostable. cockroach is not.
cockroach 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 94.3 and cockroach scores 78.0. This page calls that a decisive lead for Valkey.