A · leads
dbeaver
94.7
52,455 stars · Apache-2.0
Databases
dbeaver leads by 1.7 · narrow
A · leads
94.7
52,455 stars · Apache-2.0
B
93.0
17,956 stars · MIT
dbeaver versus rqlite 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; rqlite is written mainly in Go. The composite score is 94.7 for dbeaver and 93.0 for rqlite.
dbeaver has 52,455 GitHub stars to rqlite's 17,956, a gap of 34,499 (2.92×). Forks are 4,460 for dbeaver and 827 for rqlite. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 80.
Push history: dbeaver was last pushed on 17 November 2026 (0 days ago), and rqlite was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,349 for dbeaver (0.064 per star) and 69 for rqlite (0.004 per star). Issue-health scores are 52 and 96; 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. rqlite 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 rqlite. This is a procurement signal, not legal advice.
In Databases, both dbeaver (52,455 stars) and rqlite (17,956 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, rqlite is open source.
The lead is split. dbeaver is furthest ahead on fork community (100 to 80), while rqlite is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
dbeaver finishes ahead at 94.7 against rqlite at 93.0, a 1.7 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 | rqlite |
|---|---|---|
| GitHub stars | 52,455 | 17,956 |
| Forks | 4,460 | 827 |
| Open issues | 3,349 | 69 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 100 | 80 |
| Issue health | 52 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 93.0 |
Free universal database tool and SQL client
The lightweight, fault-tolerant database built on SQLite. Designed to keep your data highly available with minimal effort.
dbeaver has more GitHub stars: 52,455 versus 17,956 for rqlite. The gap is 34,499 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dbeaver and rqlite 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. rqlite 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 rqlite scores 93.0. This page calls that a narrow lead for dbeaver.