A · level
dbeaver
94.7
52,455 stars · Apache-2.0
Databases
Too close to call · 94.7 to 93.8
A · level
94.7
52,455 stars · Apache-2.0
B · level
93.8
27,763 stars · MIT
dbeaver versus postgrest 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; postgrest is written mainly in Haskell. The composite score is 94.7 for dbeaver and 93.8 for postgrest.
dbeaver has 52,455 GitHub stars to postgrest's 27,763, a gap of 24,692 (1.89×). Forks are 4,460 for dbeaver and 1,238 for postgrest. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 85.
Push history: dbeaver was last pushed on 17 November 2026 (0 days ago), and postgrest was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,349 for dbeaver (0.064 per star) and 407 for postgrest (0.015 per star). Issue-health scores are 52 and 84; 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. postgrest 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 postgrest. This is a procurement signal, not legal advice.
In Databases, both dbeaver (52,455 stars) and postgrest (27,763 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, postgrest is open source.
The lead is split. dbeaver is furthest ahead on fork community (100 to 85), while postgrest is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
Composite score: dbeaver 94.7, postgrest 93.8. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | postgrest |
|---|---|---|
| GitHub stars | 52,455 | 27,763 |
| Forks | 4,460 | 1,238 |
| Open issues | 3,349 | 407 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 85 |
| Issue health | 52 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 93.8 |
Free universal database tool and SQL client
REST API for any Postgres database
dbeaver has more GitHub stars: 52,455 versus 27,763 for postgrest. The gap is 24,692 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dbeaver and postgrest 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. postgrest 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.
Neither tool clears a one-point margin. dbeaver scores 94.7 and postgrest scores 93.8.