CookCLIvsZero to JupyterHub with Kubernetes
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| CookCLI | Zero to JupyterHub with Kubernetes | |
|---|---|---|
| Score | 61/100 | 64/100 |
| Rank in category | #3 of 18 in Recipe Management | #4 of 11 in Container Orchestration |
| GitHub stars | 1 423 | 1 725 |
| Stars, last 30 days | +32 | +0 |
| Stable releases, 12 months | 21 | 9 |
| Latest release | v0.39.0 · 24 Oct 2026 | 4.4.4 · 20 Oct 2026 |
| Setup | Easy | Advanced |
| Official Docker image | Yes | Yes |
| License | MIT | Other |
| Main language | Rust | Python |
Which one should you pick?
Zero to JupyterHub with Kubernetes scores 64/100 against 61/100 for CookCLI, so it is the safer default.
CookCLI ships more often: 21 stable releases in the past year, against 9 for Zero to JupyterHub with Kubernetes.
If you want the quickest setup, CookCLI is easier to run; Zero to JupyterHub with Kubernetes needs more configuration.
CookCLI is growing faster right now (+32 stars in 30 days).
CookCLI details →Zero to JupyterHub with Kubernetes details →
Swap a project
Keep CookCLI, compare it with
Keep Zero to JupyterHub with Kubernetes, compare it with