A · leads
dbeaver
94.0
52,455 stars · Apache-2.0
Databases
dbeaver leads by 4.6 · narrow
A · leads
94.0
52,455 stars · Apache-2.0
B
89.4
32,285 stars · GPL-2.0
dbeaver versus rocksdb 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; rocksdb is written mainly in C++. The composite score is 94.0 for dbeaver and 89.4 for rocksdb.
dbeaver has 52,455 GitHub stars to rocksdb's 32,285, a gap of 20,170 (1.62×). Forks are 4,460 for dbeaver and 7,033 for rocksdb. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 95 versus 100.
Push history: dbeaver was last pushed on 17 November 2026 (0 days ago), and rocksdb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,349 for dbeaver (0.064 per star) and 1,855 for rocksdb (0.057 per star). Issue-health scores are 52 and 52; 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. 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 dbeaver and 64 for rocksdb. This is a procurement signal, not legal advice.
In Databases, both dbeaver (52,455 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: dbeaver is open source, rocksdb is open source.
The lead is split. dbeaver is furthest ahead on license flexibility (96 to 64), while rocksdb is furthest ahead on fork community (100 to 95). Choose the dimension a rollout cannot compromise on.
dbeaver finishes ahead at 94.0 against rocksdb at 89.4, a 4.6 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 | dbeaver | rocksdb |
|---|---|---|
| GitHub stars | 52,455 | 32,285 |
| Forks | 4,460 | 7,033 |
| Open issues | 3,349 | 1,855 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 95 | 100 |
| Issue health | 52 | 52 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 94.0 | 89.4 |
Free universal database tool and SQL client
A library that provides an embeddable, persistent key-value store for fast storage.
dbeaver has more GitHub stars: 52,455 versus 32,285 for rocksdb. The gap is 20,170 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dbeaver and rocksdb as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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.
dbeaver scores 94.0 and rocksdb scores 89.4. This page calls that a narrow lead for dbeaver.