A · leads
postgrest
90.7
27,763 stars · MIT
Databases
postgrest leads by 7.3 · clear
A · leads
90.7
27,763 stars · MIT
B
83.4
77,588 stars · license n/a
postgrest versus redis 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; redis is written mainly in C. The composite score is 90.7 for postgrest and 83.4 for redis.
redis has 77,588 GitHub stars to postgrest's 27,763, a gap of 49,825 (2.79×). Forks are 1,238 for postgrest and 25,072 for redis. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 70 versus 100.
Push history: postgrest was last pushed on 17 November 2026 (0 days ago), and redis was last pushed on 17 November 2026 (0 days ago). Open issues stand at 407 for postgrest (0.015 per star) and 3,122 for redis (0.040 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. redis is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for postgrest and 30 for redis. This is a procurement signal, not legal advice.
Only postgrest is marked self-hostable here (27,763 stars, deploy score 100). redis is not (77,588 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: postgrest is open source, redis is unpriced in this catalog.
The lead is split. postgrest is furthest ahead on license flexibility (96 to 30), while redis is furthest ahead on fork community (100 to 70). Choose the dimension a rollout cannot compromise on.
postgrest finishes ahead at 90.7 against redis at 83.4, a 7.3 point clear 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 | redis |
|---|---|---|
| GitHub stars | 27,763 | 77,588 |
| Forks | 1,238 | 25,072 |
| Open issues | 407 | 3,122 |
| Adoption | 91 | 100 |
| Activity | 100 | 100 |
| Community | 70 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 90.7 | 83.4 |
REST API for any Postgres database
For developers, who are building real-time data-driven applications, Redis is the preferred, fastest, and most feature-rich cache, data structure server, and document and vector query engine.
redis has more GitHub stars: 77,588 versus 27,763 for postgrest. The gap is 49,825 stars.
Both were last pushed on 17 November 2026.
Only postgrest is marked self-hostable. redis is not.
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. redis is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
postgrest scores 90.7 and redis scores 83.4. This page calls that a clear lead for postgrest.