Knock-KnockvsPostgREST
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Knock-Knock | PostgREST | |
|---|---|---|
| Score | 48/100 | 79/100 |
| Rank in category | #49 of 78 in Security | #2 of 13 in API |
| GitHub stars | 214 | 27 734 |
| Stars, last 30 days | +0 | +57 |
| Stable releases, 12 months | 5 | 20 |
| Latest release | v3.0.0 · 26 Jul 2026 | v16.5 · 18 Oct 2026 |
| Setup | Advanced | Easy |
| Official Docker image | Yes | Yes |
| License | MIT | MIT |
| Main language | Python | Haskell |
Which one should you pick?
PostgREST scores 79/100 against 48/100 for Knock-Knock, so it is the safer default.
PostgREST ships more often: 20 stable releases in the past year, against 5 for Knock-Knock.
If you want the quickest setup, PostgREST is easier to run; Knock-Knock needs more configuration.
PostgREST is growing faster right now (+57 stars in 30 days).
Knock-Knock details →PostgREST details →
Swap a project
Keep Knock-Knock, compare it with
Keep PostgREST, compare it with