Skip to content
DevUtils Online

Databases

dbeaver vs migrate

dbeaver leads by 16.0 · decisive

A · leads

dbeaver

94.7

52,455 stars · Apache-2.0

B

migrate

78.7

19,030 stars · license n/a

dbeaver versus migrate 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; migrate is written mainly in Go. The composite score is 94.7 for dbeaver and 78.7 for migrate.

dbeaver has 52,455 GitHub stars to migrate's 19,030, a gap of 33,425 (2.76×). Forks are 4,460 for dbeaver and 1,720 for migrate. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 100 versus 89.

Push history: dbeaver was last pushed on 17 November 2026 (0 days ago), and migrate was last pushed on 16 November 2026 (1 day ago). Open issues stand at 3,349 for dbeaver (0.064 per star) and 500 for migrate (0.026 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. migrate is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for dbeaver and 30 for migrate. This is a procurement signal, not legal advice.

Only dbeaver is marked self-hostable here (52,455 stars, deploy score 100). migrate is not (19,030 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: dbeaver is open source, migrate is unpriced in this catalog.

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

dbeaver finishes ahead at 94.7 against migrate at 78.7, a 16.0 point decisive 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 migrate metrics
Signal dbeaver migrate
GitHub stars 52,455 19,030
Forks 4,460 1,720
Open issues 3,349 500
Adoption 100 91
Activity 100 100
Community 100 89
Issue health 52 70
License 96 30
Self-hosting 100 35
Composite 94.7 78.7

Questions this page answers

Which has more GitHub stars, dbeaver or migrate?

dbeaver has more GitHub stars: 52,455 versus 19,030 for migrate. The gap is 33,425 stars.

Which was updated more recently, dbeaver or migrate?

dbeaver was pushed more recently: 17 November 2026 versus 16 November 2026 for migrate. That is 1 days apart.

Can I self-host both dbeaver and migrate?

Only dbeaver is marked self-hostable. migrate is not.

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

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. migrate is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the dbeaver vs migrate score?

dbeaver scores 94.7 and migrate scores 78.7. This page calls that a decisive lead for dbeaver.

Related comparisons