A · leads
DuckDB
96.5
43,126 stars · MIT
Databases
DuckDB leads by 2.0 · narrow
A · leads
96.5
43,126 stars · MIT
B
94.5
27,763 stars · MIT
DuckDB versus postgrest is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. DuckDB is written mainly in C++; postgrest is written mainly in Haskell. The composite score is 96.5 for DuckDB and 94.5 for postgrest.
DuckDB has 43,126 GitHub stars to postgrest's 27,763, a gap of 15,363 (1.55×). Forks are 4,214 for DuckDB and 1,238 for postgrest. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 85.
Push history: DuckDB 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 1,261 for DuckDB (0.029 per star) and 407 for postgrest (0.015 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
Both DuckDB and postgrest are listed as MIT. 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 DuckDB (43,126 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: DuckDB is open source, postgrest is open source.
The lead is split. DuckDB is furthest ahead on fork community (100 to 85), while postgrest is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
DuckDB finishes ahead at 96.5 against postgrest at 94.5, a 2.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 | DuckDB | postgrest |
|---|---|---|
| GitHub stars | 43,126 | 27,763 |
| Forks | 4,214 | 1,238 |
| Open issues | 1,261 | 407 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 100 | 85 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 94.5 |
DuckDB is an in-process analytical database, often described as SQLite for OLAP. It runs inside the application process and queries local files such as Parquet.
REST API for any Postgres database
DuckDB has more GitHub stars: 43,126 versus 27,763 for postgrest. The gap is 15,363 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both DuckDB and postgrest as self-hostable. Confirm each project's deploy docs before you plan a migration.
DuckDB 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. 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.
DuckDB scores 96.5 and postgrest scores 94.5. This page calls that a narrow lead for DuckDB.