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