A · leads
dbeaver
94.7
52,455 stars · Apache-2.0
Databases
dbeaver leads by 4.0 · narrow
A · leads
94.7
52,455 stars · Apache-2.0
B
90.7
25,279 stars · MIT
dbeaver versus turso 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; turso is written mainly in Rust. The composite score is 94.7 for dbeaver and 90.7 for turso.
dbeaver has 52,455 GitHub stars to turso's 25,279, a gap of 27,176 (2.08×). Forks are 4,460 for dbeaver and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 88.
Push history: dbeaver was last pushed on 17 November 2026 (0 days ago), and turso was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,349 for dbeaver (0.064 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 52 and 52; 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. turso 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 turso. This is a procurement signal, not legal advice.
In Databases, both dbeaver (52,455 stars) and turso (25,279 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, turso is open source.
dbeaver is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 12 points (100 vs 88), and the tightest is self-hosting at 0 points (100 vs 100).
dbeaver finishes ahead at 94.7 against turso at 90.7, a 4.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 | turso |
|---|---|---|
| GitHub stars | 52,455 | 25,279 |
| Forks | 4,460 | 1,553 |
| Open issues | 3,349 | 1,714 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 88 |
| Issue health | 52 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 90.7 |
Free universal database tool and SQL client
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
dbeaver has more GitHub stars: 52,455 versus 25,279 for turso. The gap is 27,176 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dbeaver and turso 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. turso 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 turso scores 90.7. This page calls that a narrow lead for dbeaver.