A · level
chroma
93.9
29,704 stars · Apache-2.0
Databases
Too close to call · 93.9 to 94.7
A · level
93.9
29,704 stars · Apache-2.0
B · level
94.7
52,455 stars · Apache-2.0
chroma versus dbeaver 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; dbeaver is written mainly in Java. The composite score is 93.9 for chroma and 94.7 for dbeaver.
dbeaver has 52,455 GitHub stars to chroma's 29,704, a gap of 22,751 (1.77×). Forks are 2,609 for chroma and 4,460 for dbeaver. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 94 versus 100.
Push history: chroma was last pushed on 13 November 2026 (3 days ago), and dbeaver was last pushed on 17 November 2026 (0 days ago). Open issues stand at 979 for chroma (0.033 per star) and 3,349 for dbeaver (0.064 per star). Issue-health scores are 70 and 52; activity scores are 100 and 100.
Both chroma and dbeaver 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 dbeaver (52,455 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, dbeaver is open source.
The lead is split. chroma is furthest ahead on issue health (70 to 52), while dbeaver is furthest ahead on fork community (100 to 94). Choose the dimension a rollout cannot compromise on.
Composite score: chroma 93.9, dbeaver 94.7. 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 | dbeaver |
|---|---|---|
| GitHub stars | 29,704 | 52,455 |
| Forks | 2,609 | 4,460 |
| Open issues | 979 | 3,349 |
| Adoption | 95 | 100 |
| Activity | 100 | 100 |
| Community | 94 | 100 |
| Issue health | 70 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.9 | 94.7 |
Search infrastructure for AI
Free universal database tool and SQL client
dbeaver has more GitHub stars: 52,455 versus 29,704 for chroma. The gap is 22,751 stars.
dbeaver 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 dbeaver 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. dbeaver 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 93.9 and dbeaver scores 94.7.