A · leads
dbeaver
94.7
52,455 stars · Apache-2.0
Databases
dbeaver leads by 1.9 · narrow
A · leads
94.7
52,455 stars · Apache-2.0
B
92.8
27,730 stars · BSD-3-Clause
dbeaver versus Valkey 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; Valkey is written mainly in C. The composite score is 94.7 for dbeaver and 92.8 for Valkey.
dbeaver has 52,455 GitHub stars to Valkey's 27,730, a gap of 24,725 (1.89×). Forks are 4,460 for dbeaver and 1,540 for Valkey. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 87.
Push history: dbeaver was last pushed on 17 November 2026 (0 days ago), and Valkey was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,349 for dbeaver (0.064 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 52 and 70; 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. Valkey is listed as BSD-3-Clause, 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 96 for dbeaver and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both dbeaver (52,455 stars) and Valkey (27,730 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, Valkey is open source.
The lead is split. dbeaver is furthest ahead on fork community (100 to 87), while Valkey is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
dbeaver finishes ahead at 94.7 against Valkey at 92.8, a 1.9 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 | Valkey |
|---|---|---|
| GitHub stars | 52,455 | 27,730 |
| Forks | 4,460 | 1,540 |
| Open issues | 3,349 | 1,045 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 87 |
| Issue health | 52 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 92.8 |
Free universal database tool and SQL client
Valkey is a Linux Foundation key-value store forked from Redis. It is used as a cache, queue, and ephemeral data store under a permissive license.
dbeaver has more GitHub stars: 52,455 versus 27,730 for Valkey. The gap is 24,725 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dbeaver and Valkey 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. Valkey is listed as BSD-3-Clause, 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.
dbeaver scores 94.7 and Valkey scores 92.8. This page calls that a narrow lead for dbeaver.