Payload CMSvsZero to JupyterHub with Kubernetes
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Payload CMS | Zero to JupyterHub with Kubernetes | |
|---|---|---|
| Score | 83/100 | 64/100 |
| Rank in category | #2 of 13 in Headless CMS | #4 of 11 in Container Orchestration |
| GitHub stars | 45 559 | 1 725 |
| Stars, last 30 days | +647 | — |
| Stable releases, 12 months | 20 | 9 |
| Latest release | v3.92.1 · 27 Oct 2026 | 4.4.4 · 20 Oct 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | No | Yes |
| License | MIT | Other |
| Main language | Typescript | Python |
Which one should you pick?
Payload CMS scores 83/100 against 64/100 for Zero to JupyterHub with Kubernetes, so it is the safer default.
Payload CMS ships more often: 20 stable releases in the past year, against 9 for Zero to JupyterHub with Kubernetes.
If you want the quickest setup, Payload CMS is easier to run; Zero to JupyterHub with Kubernetes needs more configuration.
Payload CMS is growing faster right now (+647 stars in 30 days).
Payload CMS details →Zero to JupyterHub with Kubernetes details →