A · leads
redis
83.4
77,588 stars · license n/a
Databases
redis leads by 13.5 · clear
A · leads
83.4
77,588 stars · license n/a
B
69.9
10,666 stars · license n/a
redis versus yugabyte-db 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 83.4 for redis and 69.9 for yugabyte-db.
redis has 77,588 GitHub stars to yugabyte-db's 10,666, a gap of 66,922 (7.27×). Forks are 25,072 for redis and 1,477 for yugabyte-db. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 72.
Push history: redis was last pushed on 17 November 2026 (0 days ago), and yugabyte-db was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,122 for redis (0.040 per star) and 9,707 for yugabyte-db (0.910 per star). Issue-health scores are 70 and 34; activity scores are 100 and 100.
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. yugabyte-db 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 redis and 30 for yugabyte-db. This is a procurement signal, not legal advice.
Neither redis nor yugabyte-db is marked self-hostable in this catalog (77,588 and 10,666 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: redis is unpriced in this catalog, yugabyte-db is unpriced in this catalog.
redis is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 36 points (70 vs 34), and the tightest is self-hosting at 0 points (35 vs 35).
redis finishes ahead at 83.4 against yugabyte-db at 69.9, a 13.5 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 | redis | yugabyte-db |
|---|---|---|
| GitHub stars | 77,588 | 10,666 |
| Forks | 25,072 | 1,477 |
| Open issues | 3,122 | 9,707 |
| Adoption | 100 | 82 |
| Activity | 100 | 100 |
| Community | 100 | 72 |
| Issue health | 70 | 34 |
| License | 30 | 30 |
| Self-hosting | 35 | 35 |
| Composite | 83.4 | 69.9 |
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.
YugabyteDB - the cloud native distributed SQL database for mission-critical applications.
redis has more GitHub stars: 77,588 versus 10,666 for yugabyte-db. The gap is 66,922 stars.
Both were last pushed on 17 November 2026.
Neither redis nor yugabyte-db is marked self-hostable in this catalog.
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. yugabyte-db 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 yugabyte-db scores 69.9. This page calls that a clear lead for redis.