A · leads
chroma
96.5
29,704 stars · Apache-2.0
Databases
chroma leads by 1.2 · narrow
A · leads
96.5
29,704 stars · Apache-2.0
B
95.3
27,730 stars · BSD-3-Clause
chroma versus Valkey 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; Valkey is written mainly in C. The composite score is 96.5 for chroma and 95.3 for Valkey.
chroma has 29,704 GitHub stars to Valkey's 27,730, a gap of 1,974 (1.07×). Forks are 2,609 for chroma and 1,540 for Valkey. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 100 versus 93.
Push history: chroma was last pushed on 13 November 2026 (3 days ago), and Valkey was last pushed on 17 November 2026 (0 days ago). Open issues stand at 979 for chroma (0.033 per star) and 1,045 for Valkey (0.038 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. 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 96 for chroma and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both chroma (29,704 stars) and Valkey (27,730 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: chroma is open source, Valkey is open source.
chroma is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 7 points (100 vs 93), and the tightest is self-hosting at 0 points (100 vs 100).
chroma finishes ahead at 96.5 against Valkey at 95.3, a 1.2 point narrow 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 | Valkey |
|---|---|---|
| GitHub stars | 29,704 | 27,730 |
| Forks | 2,609 | 1,540 |
| Open issues | 979 | 1,045 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 100 | 93 |
| Issue health | 70 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 95.3 |
Search infrastructure for AI
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.
chroma has more GitHub stars: 29,704 versus 27,730 for Valkey. The gap is 1,974 stars.
Valkey was pushed more recently: 17 November 2026 versus 13 November 2026 for chroma. That is 3 days apart.
Yes. This catalog marks both chroma and Valkey as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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.
chroma scores 96.5 and Valkey scores 95.3. This page calls that a narrow lead for chroma.