A
convex-backend
76.2
12,804 stars · license n/a
Databases
dbeaver leads by 18.5 · decisive
A
76.2
12,804 stars · license n/a
B · leads
94.7
52,455 stars · Apache-2.0
convex-backend versus dbeaver is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. convex-backend is written mainly in TypeScript; dbeaver is written mainly in Java. The composite score is 76.2 for convex-backend and 94.7 for dbeaver.
dbeaver has 52,455 GitHub stars to convex-backend's 12,804, a gap of 39,651 (4.10×). Forks are 854 for convex-backend and 4,460 for dbeaver. On the log scale used inside this pair, adoption is 87 versus 100, and the fork community is 80 versus 100.
Push history: convex-backend was last pushed on 17 November 2026 (0 days ago), and dbeaver was last pushed on 17 November 2026 (0 days ago). Open issues stand at 277 for convex-backend (0.022 per star) and 3,349 for dbeaver (0.064 per star). Issue-health scores are 70 and 52; activity scores are 100 and 100.
convex-backend is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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. License scores in this pair are 30 for convex-backend and 96 for dbeaver. This is a procurement signal, not legal advice.
Only dbeaver is marked self-hostable here (52,455 stars, deploy score 100). convex-backend is not (12,804 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: convex-backend is unpriced in this catalog, dbeaver is open source.
The lead is split. convex-backend is furthest ahead on issue health (70 to 52), while dbeaver is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
dbeaver finishes ahead at 94.7 against convex-backend at 76.2, a 18.5 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 | convex-backend | dbeaver |
|---|---|---|
| GitHub stars | 12,804 | 52,455 |
| Forks | 854 | 4,460 |
| Open issues | 277 | 3,349 |
| Adoption | 87 | 100 |
| Activity | 100 | 100 |
| Community | 80 | 100 |
| Issue health | 70 | 52 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 76.2 | 94.7 |
The open-source reactive database for app developers
Free universal database tool and SQL client
dbeaver has more GitHub stars: 52,455 versus 12,804 for convex-backend. The gap is 39,651 stars.
Both were last pushed on 17 November 2026.
Only dbeaver is marked self-hostable. convex-backend is not.
convex-backend is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
dbeaver scores 94.7 and convex-backend scores 76.2. This page calls that a decisive lead for dbeaver.