A · leads
chroma
90.5
29,704 stars · Apache-2.0
Databases
chroma leads by 7.1 · clear
A · leads
90.5
29,704 stars · Apache-2.0
B
83.4
77,588 stars · license n/a
chroma versus redis is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. chroma is written mainly in Rust; redis is written mainly in C. The composite score is 90.5 for chroma and 83.4 for redis.
redis has 77,588 GitHub stars to chroma's 29,704, a gap of 47,884 (2.61×). Forks are 2,609 for chroma and 25,072 for redis. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 78 versus 100.
Push history: chroma was last pushed on 13 November 2026 (3 days ago), and redis was last pushed on 17 November 2026 (0 days ago). Open issues stand at 979 for chroma (0.033 per star) and 3,122 for redis (0.040 per star). Issue-health scores are 70 and 70; activity scores are 100 and 100.
chroma is listed as Apache-2.0, 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 chroma and 30 for redis. This is a procurement signal, not legal advice.
Only chroma is marked self-hostable here (29,704 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: chroma is open source, redis is unpriced in this catalog.
The lead is split. chroma is furthest ahead on license flexibility (96 to 30), while redis is furthest ahead on fork community (100 to 78). Choose the dimension a rollout cannot compromise on.
chroma finishes ahead at 90.5 against redis at 83.4, a 7.1 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 | chroma | redis |
|---|---|---|
| GitHub stars | 29,704 | 77,588 |
| Forks | 2,609 | 25,072 |
| Open issues | 979 | 3,122 |
| Adoption | 92 | 100 |
| Activity | 100 | 100 |
| Community | 78 | 100 |
| Issue health | 70 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 90.5 | 83.4 |
Search infrastructure for AI
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 29,704 for chroma. The gap is 47,884 stars.
redis was pushed more recently: 17 November 2026 versus 13 November 2026 for chroma. That is 3 days apart.
Only chroma is marked self-hostable. redis is not.
chroma is listed as Apache-2.0, 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.
chroma scores 90.5 and redis scores 83.4. This page calls that a clear lead for chroma.