temporalvsZero to JupyterHub with Kubernetes
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| temporal | Zero to JupyterHub with Kubernetes | |
|---|---|---|
| Score | 83/100 | 64/100 |
| Rank in category | #1 of 1 in Workflow | #4 of 11 in Container Orchestration |
| GitHub stars | 24 049 | 1 725 |
| Stars, last 30 days | +789 | — |
| Stable releases, 12 months | 11 | 9 |
| Latest release | v1.30.8 · 12 Oct 2026 | 4.4.4 · 20 Oct 2026 |
| Setup | Advanced | Advanced |
| Official Docker image | Yes | Yes |
| License | MIT | Other |
| Main language | Go | Python |
Which one should you pick?
temporal scores 83/100 against 64/100 for Zero to JupyterHub with Kubernetes, so it is the safer default.
temporal ships more often: 11 stable releases in the past year, against 9 for Zero to JupyterHub with Kubernetes.
temporal is growing faster right now (+789 stars in 30 days).
temporal details →Zero to JupyterHub with Kubernetes details →
Swap a project
Keep temporal, compare it with
Keep Zero to JupyterHub with Kubernetes, compare it with