Skip to content
DevUtils Online

Databases

dbeaver vs drawdb

dbeaver leads by 3.3 · narrow

A · leads

dbeaver

94.7

52,455 stars · Apache-2.0

B

drawdb

91.4

40,334 stars · AGPL-3.0

dbeaver versus drawdb 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; drawdb is written mainly in JavaScript. The composite score is 94.7 for dbeaver and 91.4 for drawdb.

dbeaver has 52,455 GitHub stars to drawdb's 40,334, a gap of 12,121 (1.30×). Forks are 4,460 for dbeaver and 3,368 for drawdb. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 97.

Push history: dbeaver was last pushed on 17 November 2026 (0 days ago), and drawdb was last pushed on 13 November 2026 (3 days ago). Open issues stand at 3,349 for dbeaver (0.064 per star) and 253 for drawdb (0.006 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. drawdb is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for dbeaver and 52 for drawdb. This is a procurement signal, not legal advice.

In Databases, both dbeaver (52,455 stars) and drawdb (40,334 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, drawdb is open source.

The lead is split. dbeaver is furthest ahead on license flexibility (96 to 52), while drawdb is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.

dbeaver finishes ahead at 94.7 against drawdb at 91.4, a 3.3 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

dbeaver versus drawdb metrics
Signal dbeaver drawdb
GitHub stars 52,455 40,334
Forks 4,460 3,368
Open issues 3,349 253
Adoption 100 98
Activity 100 100
Community 100 97
Issue health 52 84
License 96 52
Self-hosting 100 100
Composite 94.7 91.4

Questions this page answers

Which has more GitHub stars, dbeaver or drawdb?

dbeaver has more GitHub stars: 52,455 versus 40,334 for drawdb. The gap is 12,121 stars.

Which was updated more recently, dbeaver or drawdb?

dbeaver was pushed more recently: 17 November 2026 versus 13 November 2026 for drawdb. That is 3 days apart.

Can I self-host both dbeaver and drawdb?

Yes. This catalog marks both dbeaver and drawdb as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, dbeaver or drawdb?

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. drawdb is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the dbeaver vs drawdb score?

dbeaver scores 94.7 and drawdb scores 91.4. This page calls that a narrow lead for dbeaver.

Related comparisons