A · leads
postgrest
97.5
27,763 stars · MIT
Databases
postgrest leads by 1.0 · narrow
A · leads
97.5
27,763 stars · MIT
B
96.5
27,730 stars · BSD-3-Clause
postgrest versus Valkey 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; Valkey is written mainly in C. The composite score is 97.5 for postgrest and 96.5 for Valkey.
postgrest has 27,763 GitHub stars to Valkey's 27,730, a gap of 33 (1.00×). Forks are 1,238 for postgrest and 1,540 for Valkey. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 97 versus 100.
Push history: postgrest was last pushed on 17 November 2026 (0 days ago), and Valkey was last pushed on 17 November 2026 (0 days ago). Open issues stand at 407 for postgrest (0.015 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 84 and 70; 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. Valkey is listed as BSD-3-Clause, 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 postgrest and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both postgrest (27,763 stars) and Valkey (27,730 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, Valkey is open source.
The lead is split. postgrest is furthest ahead on issue health (84 to 70), while Valkey is furthest ahead on fork community (100 to 97). Choose the dimension a rollout cannot compromise on.
postgrest finishes ahead at 97.5 against Valkey at 96.5, a 1.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 | postgrest | Valkey |
|---|---|---|
| GitHub stars | 27,763 | 27,730 |
| Forks | 1,238 | 1,540 |
| Open issues | 407 | 1,045 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 97 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.5 | 96.5 |
REST API for any Postgres database
Valkey is a Linux Foundation key-value store forked from Redis. It is used as a cache, queue, and ephemeral data store under a permissive license.
postgrest has more GitHub stars: 27,763 versus 27,730 for Valkey. The gap is 33 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both postgrest and Valkey 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. Valkey is listed as BSD-3-Clause, 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 Valkey scores 96.5. This page calls that a narrow lead for postgrest.