A · leads
chroma
96.3
29,704 stars · Apache-2.0
Databases
chroma leads by 12.7 · clear
A · leads
96.3
29,704 stars · Apache-2.0
B
83.6
31,878 stars · license n/a
chroma versus dragonfly 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; dragonfly is written mainly in C++. The composite score is 96.3 for chroma and 83.6 for dragonfly.
dragonfly has 31,878 GitHub stars to chroma's 29,704, a gap of 2,174 (1.07×). Forks are 2,609 for chroma and 1,294 for dragonfly. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 91.
Push history: chroma was last pushed on 13 November 2026 (3 days ago), and dragonfly was last pushed on 17 November 2026 (0 days ago). Open issues stand at 979 for chroma (0.033 per star) and 209 for dragonfly (0.007 per star). Issue-health scores are 70 and 84; 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. dragonfly 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 dragonfly. This is a procurement signal, not legal advice.
Only chroma is marked self-hostable here (29,704 stars, deploy score 100). dragonfly is not (31,878 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, dragonfly is unpriced in this catalog.
The lead is split. chroma is furthest ahead on license flexibility (96 to 30), while dragonfly is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
chroma finishes ahead at 96.3 against dragonfly at 83.6, a 12.7 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 | dragonfly |
|---|---|---|
| GitHub stars | 29,704 | 31,878 |
| Forks | 2,609 | 1,294 |
| Open issues | 979 | 209 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 91 |
| Issue health | 70 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 96.3 | 83.6 |
Search infrastructure for AI
A modern replacement for Redis and Memcached
dragonfly has more GitHub stars: 31,878 versus 29,704 for chroma. The gap is 2,174 stars.
dragonfly was pushed more recently: 17 November 2026 versus 13 November 2026 for chroma. That is 3 days apart.
Only chroma is marked self-hostable. dragonfly 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. dragonfly 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 96.3 and dragonfly scores 83.6. This page calls that a clear lead for chroma.