A · leads
chroma
94.7
29,704 stars · Apache-2.0
Databases
chroma leads by 3.8 · narrow
A · leads
94.7
29,704 stars · Apache-2.0
B
90.9
32,285 stars · GPL-2.0
chroma versus rocksdb 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; rocksdb is written mainly in C++. The composite score is 94.7 for chroma and 90.9 for rocksdb.
rocksdb has 32,285 GitHub stars to chroma's 29,704, a gap of 2,581 (1.09×). Forks are 2,609 for chroma and 7,033 for rocksdb. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 89 versus 100.
Push history: chroma was last pushed on 13 November 2026 (3 days ago), and rocksdb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 979 for chroma (0.033 per star) and 1,855 for rocksdb (0.057 per star). Issue-health scores are 70 and 52; 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. rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 96 for chroma and 64 for rocksdb. This is a procurement signal, not legal advice.
In Databases, both chroma (29,704 stars) and rocksdb (32,285 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, rocksdb is open source.
The lead is split. chroma is furthest ahead on license flexibility (96 to 64), while rocksdb is furthest ahead on fork community (100 to 89). Choose the dimension a rollout cannot compromise on.
chroma finishes ahead at 94.7 against rocksdb at 90.9, a 3.8 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 | rocksdb |
|---|---|---|
| GitHub stars | 29,704 | 32,285 |
| Forks | 2,609 | 7,033 |
| Open issues | 979 | 1,855 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 89 | 100 |
| Issue health | 70 | 52 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 90.9 |
Search infrastructure for AI
A library that provides an embeddable, persistent key-value store for fast storage.
rocksdb has more GitHub stars: 32,285 versus 29,704 for chroma. The gap is 2,581 stars.
rocksdb 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 rocksdb 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. rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
chroma scores 94.7 and rocksdb scores 90.9. This page calls that a narrow lead for chroma.