A · leads
quivr
94.4
39,655 stars · MIT
Databases
quivr leads by 11.0 · clear
A · leads
94.4
39,655 stars · MIT
B
83.4
77,588 stars · license n/a
quivr versus redis is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. quivr is written mainly in Go; redis is written mainly in C. The composite score is 94.4 for quivr and 83.4 for redis.
redis has 77,588 GitHub stars to quivr's 39,655, a gap of 37,933 (1.96×). Forks are 3,730 for quivr and 25,072 for redis. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 81 versus 100.
Push history: quivr was last pushed on 16 November 2026 (1 day ago), and redis was last pushed on 17 November 2026 (0 days ago). Open issues stand at 16 for quivr (0.000 per star) and 3,122 for redis (0.040 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
quivr is listed as MIT, 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. 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 96 for quivr and 30 for redis. This is a procurement signal, not legal advice.
Only quivr is marked self-hostable here (39,655 stars, deploy score 100). redis is not (77,588 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: quivr is open source, redis is unpriced in this catalog.
The lead is split. quivr is furthest ahead on license flexibility (96 to 30), while redis is furthest ahead on fork community (100 to 81). Choose the dimension a rollout cannot compromise on.
quivr finishes ahead at 94.4 against redis at 83.4, a 11.0 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 | quivr | redis |
|---|---|---|
| GitHub stars | 39,655 | 77,588 |
| Forks | 3,730 | 25,072 |
| Open issues | 16 | 3,122 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 81 | 100 |
| Issue health | 96 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 94.4 | 83.4 |
An open-source engine that turns continuous content streams into search and monitoring. Durable ingestion, hybrid search, alerts, and plugins for formats, models and business rules.
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 39,655 for quivr. The gap is 37,933 stars.
redis was pushed more recently: 17 November 2026 versus 16 November 2026 for quivr. That is 1 days apart.
Only quivr is marked self-hostable. redis is not.
quivr is listed as MIT, 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. 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.
quivr scores 94.4 and redis scores 83.4. This page calls that a clear lead for quivr.