A · leads
dbeaver
94.7
52,455 stars · Apache-2.0
Databases
dbeaver leads by 17.8 · decisive
A · leads
94.7
52,455 stars · Apache-2.0
B
76.9
17,684 stars · MIT
dbeaver versus tech-interview-for-developer is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Java. The composite score is 94.7 for dbeaver and 76.9 for tech-interview-for-developer.
dbeaver has 52,455 GitHub stars to tech-interview-for-developer's 17,684, a gap of 34,771 (2.97×). Forks are 4,460 for dbeaver and 3,741 for tech-interview-for-developer. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 98.
Push history: dbeaver was last pushed on 17 November 2026 (0 days ago), and tech-interview-for-developer was last pushed on 04 June 2025 (531 days ago). Open issues stand at 3,349 for dbeaver (0.064 per star) and 22 for tech-interview-for-developer (0.001 per star). Issue-health scores are 52 and 96; activity scores are 100 and 16.
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. tech-interview-for-developer 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 tech-interview-for-developer. This is a procurement signal, not legal advice.
In Databases, both dbeaver (52,455 stars) and tech-interview-for-developer (17,684 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, tech-interview-for-developer is open source.
The lead is split. dbeaver is furthest ahead on recent activity (100 to 16), while tech-interview-for-developer is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
dbeaver finishes ahead at 94.7 against tech-interview-for-developer at 76.9, a 17.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 | tech-interview-for-developer |
|---|---|---|
| GitHub stars | 52,455 | 17,684 |
| Forks | 4,460 | 3,741 |
| Open issues | 3,349 | 22 |
| Adoption | 100 | 90 |
| Activity | 100 | 16 |
| Community | 100 | 98 |
| Issue health | 52 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 76.9 |
Free universal database tool and SQL client
👶🏻 신입 개발자 전공 지식 & 기술 면접 백과사전 📖
dbeaver has more GitHub stars: 52,455 versus 17,684 for tech-interview-for-developer. The gap is 34,771 stars.
dbeaver was pushed more recently: 17 November 2026 versus 04 June 2025 for tech-interview-for-developer. That is 531 days apart.
Yes. This catalog marks both dbeaver and tech-interview-for-developer 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. tech-interview-for-developer 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 tech-interview-for-developer scores 76.9. This page calls that a decisive lead for dbeaver.