A · leads
dbeaver
94.7
52,455 stars · Apache-2.0
Databases
dbeaver leads by 4.9 · narrow
A · leads
94.7
52,455 stars · Apache-2.0
B
89.8
13,448 stars · BSD-3-Clause
dbeaver versus pgcli 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; pgcli is written mainly in Python. The composite score is 94.7 for dbeaver and 89.8 for pgcli.
dbeaver has 52,455 GitHub stars to pgcli's 13,448, a gap of 39,007 (3.90×). Forks are 4,460 for dbeaver and 619 for pgcli. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 76.
Push history: dbeaver was last pushed on 17 November 2026 (0 days ago), and pgcli was last pushed on 04 November 2026 (12 days ago). Open issues stand at 3,349 for dbeaver (0.064 per star) and 56 for pgcli (0.004 per star). Issue-health scores are 52 and 96; activity scores are 100 and 92.
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. pgcli 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 pgcli. This is a procurement signal, not legal advice.
In Databases, both dbeaver (52,455 stars) and pgcli (13,448 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, pgcli is open source.
The lead is split. dbeaver is furthest ahead on fork community (100 to 76), while pgcli is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
dbeaver finishes ahead at 94.7 against pgcli at 89.8, a 4.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 | pgcli |
|---|---|---|
| GitHub stars | 52,455 | 13,448 |
| Forks | 4,460 | 619 |
| Open issues | 3,349 | 56 |
| Adoption | 100 | 88 |
| Activity | 100 | 92 |
| Community | 100 | 76 |
| Issue health | 52 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 89.8 |
Free universal database tool and SQL client
Postgres CLI with autocompletion and syntax highlighting
dbeaver has more GitHub stars: 52,455 versus 13,448 for pgcli. The gap is 39,007 stars.
dbeaver was pushed more recently: 17 November 2026 versus 04 November 2026 for pgcli. That is 12 days apart.
Yes. This catalog marks both dbeaver and pgcli 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. pgcli 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 pgcli scores 89.8. This page calls that a narrow lead for dbeaver.