A · leads
postgrest
94.7
27,763 stars · MIT
Databases
postgrest leads by 3.8 · narrow
A · leads
94.7
27,763 stars · MIT
B
90.9
32,285 stars · GPL-2.0
postgrest versus rocksdb 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; rocksdb is written mainly in C++. The composite score is 94.7 for postgrest and 90.9 for rocksdb.
rocksdb has 32,285 GitHub stars to postgrest's 27,763, a gap of 4,522 (1.16×). Forks are 1,238 for postgrest and 7,033 for rocksdb. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 80 versus 100.
Push history: postgrest was last pushed on 17 November 2026 (0 days ago), and rocksdb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 407 for postgrest (0.015 per star) and 1,855 for rocksdb (0.057 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
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. rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 96 for postgrest and 64 for rocksdb. This is a procurement signal, not legal advice.
In Databases, both postgrest (27,763 stars) and rocksdb (32,285 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, rocksdb is open source.
The lead is split. postgrest is furthest ahead on issue health (84 to 52), while rocksdb is furthest ahead on fork community (100 to 80). Choose the dimension a rollout cannot compromise on.
postgrest finishes ahead at 94.7 against rocksdb at 90.9, a 3.8 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 | rocksdb |
|---|---|---|
| GitHub stars | 27,763 | 32,285 |
| Forks | 1,238 | 7,033 |
| Open issues | 407 | 1,855 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 80 | 100 |
| Issue health | 84 | 52 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 90.9 |
REST API for any Postgres database
A library that provides an embeddable, persistent key-value store for fast storage.
rocksdb has more GitHub stars: 32,285 versus 27,763 for postgrest. The gap is 4,522 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both postgrest and rocksdb 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. rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
postgrest scores 94.7 and rocksdb scores 90.9. This page calls that a narrow lead for postgrest.