A
dbeaver
94.0
52,455 stars · Apache-2.0
Databases
shardingsphere leads by 1.0 · narrow
A
94.0
52,455 stars · Apache-2.0
B · leads
95.0
20,830 stars · Apache-2.0
dbeaver versus shardingsphere 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.0 for dbeaver and 95.0 for shardingsphere.
dbeaver has 52,455 GitHub stars to shardingsphere's 20,830, a gap of 31,625 (2.52×). Forks are 4,460 for dbeaver and 6,910 for shardingsphere. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 95 versus 100.
Push history: dbeaver was last pushed on 17 November 2026 (0 days ago), and shardingsphere was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,349 for dbeaver (0.064 per star) and 267 for shardingsphere (0.013 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
Both dbeaver and shardingsphere 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 shardingsphere (20,830 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, shardingsphere is open source.
The lead is split. dbeaver is furthest ahead on adoption (100 to 92), while shardingsphere is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
shardingsphere finishes ahead at 95.0 against dbeaver at 94.0, a 1.0 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 | shardingsphere |
|---|---|---|
| GitHub stars | 52,455 | 20,830 |
| Forks | 4,460 | 6,910 |
| Open issues | 3,349 | 267 |
| Adoption | 100 | 92 |
| Activity | 100 | 100 |
| Community | 95 | 100 |
| Issue health | 52 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.0 | 95.0 |
Free universal database tool and SQL client
Empowering Data Intelligence with Distributed SQL for Sharding, Scalability, and Security Across All Databases.
dbeaver has more GitHub stars: 52,455 versus 20,830 for shardingsphere. The gap is 31,625 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dbeaver and shardingsphere 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. shardingsphere 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.
shardingsphere scores 95.0 and dbeaver scores 94.0. This page calls that a narrow lead for shardingsphere.