A
mongo
86.0
28,682 stars · license n/a
Databases
postgrest leads by 9.3 · clear
A
86.0
28,682 stars · license n/a
B · leads
95.3
27,763 stars · MIT
mongo versus postgrest is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. mongo is written mainly in C++; postgrest is written mainly in Haskell. The composite score is 86.0 for mongo and 95.3 for postgrest.
mongo has 28,682 GitHub stars to postgrest's 27,763, a gap of 919 (1.03×). Forks are 5,916 for mongo and 1,238 for postgrest. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 82.
Push history: mongo 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 45 for mongo (0.002 per star) and 407 for postgrest (0.015 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
mongo 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. 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. License scores in this pair are 30 for mongo and 96 for postgrest. This is a procurement signal, not legal advice.
Only postgrest is marked self-hostable here (27,763 stars, deploy score 100). mongo is not (28,682 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: mongo is unpriced in this catalog, postgrest is open source.
The lead is split. mongo is furthest ahead on fork community (100 to 82), while postgrest is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
postgrest finishes ahead at 95.3 against mongo at 86.0, a 9.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 | mongo | postgrest |
|---|---|---|
| GitHub stars | 28,682 | 27,763 |
| Forks | 5,916 | 1,238 |
| Open issues | 45 | 407 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 82 |
| Issue health | 96 | 84 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 86.0 | 95.3 |
The MongoDB Database
REST API for any Postgres database
mongo has more GitHub stars: 28,682 versus 27,763 for postgrest. The gap is 919 stars.
Both were last pushed on 17 November 2026.
Only postgrest is marked self-hostable. mongo is not.
mongo 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. 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.
postgrest scores 95.3 and mongo scores 86.0. This page calls that a clear lead for postgrest.