A · leads
dbeaver
94.7
52,455 stars · Apache-2.0
Databases
dbeaver leads by 20.8 · decisive
A · leads
94.7
52,455 stars · Apache-2.0
B
73.9
11,117 stars · Apache-2.0
dbeaver versus FerretDB 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; FerretDB is written mainly in Go. The composite score is 94.7 for dbeaver and 73.9 for FerretDB.
dbeaver has 52,455 GitHub stars to FerretDB's 11,117, a gap of 41,338 (4.72×). Forks are 4,460 for dbeaver and 496 for FerretDB. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 74.
Push history: dbeaver was last pushed on 17 November 2026 (0 days ago), and FerretDB was last pushed on 05 June 2026 (165 days ago). Open issues stand at 3,349 for dbeaver (0.064 per star) and 452 for FerretDB (0.041 per star). Issue-health scores are 52 and 70; activity scores are 100 and 36.
Both dbeaver and FerretDB 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 dbeaver (52,455 stars) and FerretDB (11,117 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, FerretDB is open source.
The lead is split. dbeaver is furthest ahead on recent activity (100 to 36), while FerretDB is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
dbeaver finishes ahead at 94.7 against FerretDB at 73.9, a 20.8 point decisive 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 | FerretDB |
|---|---|---|
| GitHub stars | 52,455 | 11,117 |
| Forks | 4,460 | 496 |
| Open issues | 3,349 | 452 |
| Adoption | 100 | 86 |
| Activity | 100 | 36 |
| Community | 100 | 74 |
| Issue health | 52 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 73.9 |
Free universal database tool and SQL client
FerretDB is a MongoDB-compatible document database that stores data in PostgreSQL. It is built for teams that want that wire protocol without the SSPL server.
dbeaver has more GitHub stars: 52,455 versus 11,117 for FerretDB. The gap is 41,338 stars.
dbeaver was pushed more recently: 17 November 2026 versus 05 June 2026 for FerretDB. That is 165 days apart.
Yes. This catalog marks both dbeaver and FerretDB 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. FerretDB 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.
dbeaver scores 94.7 and FerretDB scores 73.9. This page calls that a decisive lead for dbeaver.