A · level
chroma
92.9
29,704 stars · Apache-2.0
Databases
Too close to call · 92.9 to 92.9
A · level
92.9
29,704 stars · Apache-2.0
B · level
92.9
50,970 stars · Apache-2.0
chroma versus ClickHouse 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; ClickHouse is written mainly in C++. The composite score is 92.9 for chroma and 92.9 for ClickHouse.
ClickHouse has 50,970 GitHub stars to chroma's 29,704, a gap of 21,266 (1.72×). Forks are 2,609 for chroma and 9,275 for ClickHouse. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 86 versus 100.
Push history: chroma was last pushed on 13 November 2026 (3 days ago), and ClickHouse was last pushed on 17 November 2026 (0 days ago). Open issues stand at 979 for chroma (0.033 per star) and 9,191 for ClickHouse (0.180 per star). Issue-health scores are 70 and 34; activity scores are 100 and 100.
Both chroma and ClickHouse are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Databases, both chroma (29,704 stars) and ClickHouse (50,970 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, ClickHouse is open source.
The lead is split. chroma is furthest ahead on issue health (70 to 34), while ClickHouse is furthest ahead on fork community (100 to 86). Choose the dimension a rollout cannot compromise on.
Composite score: chroma 92.9, ClickHouse 92.9. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | ClickHouse |
|---|---|---|
| GitHub stars | 29,704 | 50,970 |
| Forks | 2,609 | 9,275 |
| Open issues | 979 | 9,191 |
| Adoption | 95 | 100 |
| Activity | 100 | 100 |
| Community | 86 | 100 |
| Issue health | 70 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 92.9 |
Search infrastructure for AI
ClickHouse is a columnar OLAP database built for fast analytical queries on large event tables. It is common as the store behind product analytics and observability.
ClickHouse has more GitHub stars: 50,970 versus 29,704 for chroma. The gap is 21,266 stars.
ClickHouse 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 ClickHouse 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. ClickHouse 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. chroma scores 92.9 and ClickHouse scores 92.9.