A · leads
dbeaver
94.7
52,455 stars · Apache-2.0
Databases
dbeaver leads by 13.5 · clear
A · leads
94.7
52,455 stars · Apache-2.0
B
81.2
31,878 stars · license n/a
dbeaver versus dragonfly is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dbeaver is written mainly in Java; dragonfly is written mainly in C++. The composite score is 94.7 for dbeaver and 81.2 for dragonfly.
dbeaver has 52,455 GitHub stars to dragonfly's 31,878, a gap of 20,577 (1.65×). Forks are 4,460 for dbeaver and 1,294 for dragonfly. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 85.
Push history: dbeaver was last pushed on 17 November 2026 (0 days ago), and dragonfly was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,349 for dbeaver (0.064 per star) and 209 for dragonfly (0.007 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
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. 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 dbeaver and 30 for dragonfly. This is a procurement signal, not legal advice.
Only dbeaver is marked self-hostable here (52,455 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: dbeaver is open source, dragonfly is unpriced in this catalog.
The lead is split. dbeaver is furthest ahead on license flexibility (96 to 30), while dragonfly is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
dbeaver finishes ahead at 94.7 against dragonfly at 81.2, a 13.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 | dbeaver | dragonfly |
|---|---|---|
| GitHub stars | 52,455 | 31,878 |
| Forks | 4,460 | 1,294 |
| Open issues | 3,349 | 209 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 100 | 85 |
| Issue health | 52 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 94.7 | 81.2 |
Free universal database tool and SQL client
A modern replacement for Redis and Memcached
dbeaver has more GitHub stars: 52,455 versus 31,878 for dragonfly. The gap is 20,577 stars.
Both were last pushed on 17 November 2026.
Only dbeaver is marked self-hostable. dragonfly is not.
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. 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.
dbeaver scores 94.7 and dragonfly scores 81.2. This page calls that a clear lead for dbeaver.