A · leads
dbeaver
94.7
52,455 stars · Apache-2.0
Databases
dbeaver leads by 5.3 · narrow
A · leads
94.7
52,455 stars · Apache-2.0
B
89.4
9,761 stars · MIT
dbeaver versus tile38 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; tile38 is written mainly in Go. The composite score is 94.7 for dbeaver and 89.4 for tile38.
dbeaver has 52,455 GitHub stars to tile38's 9,761, a gap of 42,694 (5.37×). Forks are 4,460 for dbeaver and 626 for tile38. On the log scale used inside this pair, adoption is 100 versus 84, and the fork community is 100 versus 77.
Push history: dbeaver was last pushed on 17 November 2026 (0 days ago), and tile38 was last pushed on 14 November 2026 (3 days ago). Open issues stand at 3,349 for dbeaver (0.064 per star) and 165 for tile38 (0.017 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. tile38 is listed as MIT, 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 tile38. This is a procurement signal, not legal advice.
In Databases, both dbeaver (52,455 stars) and tile38 (9,761 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, tile38 is open source.
The lead is split. dbeaver is furthest ahead on fork community (100 to 77), while tile38 is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
dbeaver finishes ahead at 94.7 against tile38 at 89.4, a 5.3 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 | tile38 |
|---|---|---|
| GitHub stars | 52,455 | 9,761 |
| Forks | 4,460 | 626 |
| Open issues | 3,349 | 165 |
| Adoption | 100 | 84 |
| Activity | 100 | 100 |
| Community | 100 | 77 |
| Issue health | 52 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 89.4 |
Free universal database tool and SQL client
Real-time Geospatial and Geofencing
dbeaver has more GitHub stars: 52,455 versus 9,761 for tile38. The gap is 42,694 stars.
dbeaver was pushed more recently: 17 November 2026 versus 14 November 2026 for tile38. That is 3 days apart.
Yes. This catalog marks both dbeaver and tile38 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. tile38 is listed as MIT, 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 tile38 scores 89.4. This page calls that a narrow lead for dbeaver.