A
chartdb
86.0
23,133 stars · AGPL-3.0
Databases
chroma leads by 10.5 · clear
A
86.0
23,133 stars · AGPL-3.0
B · leads
96.5
29,704 stars · Apache-2.0
chartdb versus chroma is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. chartdb is written mainly in TypeScript; chroma is written mainly in Rust. The composite score is 86.0 for chartdb and 96.5 for chroma.
chroma has 29,704 GitHub stars to chartdb's 23,133, a gap of 6,571 (1.28×). Forks are 1,527 for chartdb and 2,609 for chroma. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 93 versus 100.
Push history: chartdb was last pushed on 01 November 2026 (16 days ago), and chroma was last pushed on 13 November 2026 (3 days ago). Open issues stand at 155 for chartdb (0.007 per star) and 979 for chroma (0.033 per star). Issue-health scores are 84 and 70; activity scores are 78 and 100.
chartdb is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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. License scores in this pair are 52 for chartdb and 96 for chroma. This is a procurement signal, not legal advice.
In Databases, both chartdb (23,133 stars) and chroma (29,704 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: chartdb is open source, chroma is open source.
The lead is split. chartdb is furthest ahead on issue health (84 to 70), while chroma is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
chroma finishes ahead at 96.5 against chartdb at 86.0, a 10.5 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 | chartdb | chroma |
|---|---|---|
| GitHub stars | 23,133 | 29,704 |
| Forks | 1,527 | 2,609 |
| Open issues | 155 | 979 |
| Adoption | 98 | 100 |
| Activity | 78 | 100 |
| Community | 93 | 100 |
| Issue health | 84 | 70 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 86.0 | 96.5 |
Database diagrams editor that allows you to visualize and design your DB with a single query.
Search infrastructure for AI
chroma has more GitHub stars: 29,704 versus 23,133 for chartdb. The gap is 6,571 stars.
chroma was pushed more recently: 13 November 2026 versus 01 November 2026 for chartdb. That is 13 days apart.
Yes. This catalog marks both chartdb and chroma as self-hostable. Confirm each project's deploy docs before you plan a migration.
chartdb is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
chroma scores 96.5 and chartdb scores 86.0. This page calls that a clear lead for chroma.