A · leads
postgrest
97.5
27,763 stars · MIT
Databases
postgrest leads by 3.1 · narrow
A · leads
97.5
27,763 stars · MIT
B
94.4
25,279 stars · MIT
postgrest versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. postgrest is written mainly in Haskell; turso is written mainly in Rust. The composite score is 97.5 for postgrest and 94.4 for turso.
postgrest has 27,763 GitHub stars to turso's 25,279, a gap of 2,484 (1.10×). Forks are 1,238 for postgrest and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 97 versus 100.
Push history: postgrest 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 407 for postgrest (0.015 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
Both postgrest and turso 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 postgrest (27,763 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: postgrest is open source, turso is open source.
The lead is split. postgrest is furthest ahead on issue health (84 to 52), while turso is furthest ahead on fork community (100 to 97). Choose the dimension a rollout cannot compromise on.
postgrest finishes ahead at 97.5 against turso at 94.4, a 3.1 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 | postgrest | turso |
|---|---|---|
| GitHub stars | 27,763 | 25,279 |
| Forks | 1,238 | 1,553 |
| Open issues | 407 | 1,714 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 97 | 100 |
| Issue health | 84 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.5 | 94.4 |
REST API for any Postgres database
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
postgrest has more GitHub stars: 27,763 versus 25,279 for turso. The gap is 2,484 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both postgrest and turso as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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.
postgrest scores 97.5 and turso scores 94.4. This page calls that a narrow lead for postgrest.