A
dicedb
60.8
10,776 stars · license n/a
Databases
redis leads by 22.6 · decisive
A
60.8
10,776 stars · license n/a
B · leads
83.4
77,588 stars · license n/a
dicedb versus redis is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in C. The composite score is 60.8 for dicedb and 83.4 for redis.
redis has 77,588 GitHub stars to dicedb's 10,776, a gap of 66,812 (7.20×). Forks are 1,397 for dicedb and 25,072 for redis. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 72 versus 100.
Push history: dicedb was last pushed on 23 April 2026 (208 days ago), and redis was last pushed on 17 November 2026 (0 days ago). Open issues stand at 132 for dicedb (0.012 per star) and 3,122 for redis (0.040 per star). Issue-health scores are 84 and 70; activity scores are 36 and 100.
dicedb 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. 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 30 for dicedb and 30 for redis. This is a procurement signal, not legal advice.
Neither dicedb nor redis is marked self-hostable in this catalog (10,776 and 77,588 stars). Deploy scores stay at 35 and 35. Treat both as hosted products until their own docs say you can run them. Pricing labels on file: dicedb is unpriced in this catalog, redis is unpriced in this catalog.
The lead is split. dicedb is furthest ahead on issue health (84 to 70), while redis is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
redis finishes ahead at 83.4 against dicedb at 60.8, a 22.6 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 | dicedb | redis |
|---|---|---|
| GitHub stars | 10,776 | 77,588 |
| Forks | 1,397 | 25,072 |
| Open issues | 132 | 3,122 |
| Adoption | 82 | 100 |
| Activity | 36 | 100 |
| Community | 72 | 100 |
| Issue health | 84 | 70 |
| License | 30 | 30 |
| Self-hosting | 35 | 35 |
| Composite | 60.8 | 83.4 |
Open-source, low-latency key/value engine built on Valkey with query subscriptions and hierarchical storage tiers.
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 10,776 for dicedb. The gap is 66,812 stars.
redis was pushed more recently: 17 November 2026 versus 23 April 2026 for dicedb. That is 208 days apart.
Neither dicedb nor redis is marked self-hostable in this catalog.
dicedb 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. 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.
redis scores 83.4 and dicedb scores 60.8. This page calls that a decisive lead for redis.