n8nvsZero to JupyterHub with Kubernetes
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| n8n | Zero to JupyterHub with Kubernetes | |
|---|---|---|
| Score | 92/100 | 64/100 |
| Rank in category | #1 of 32 in Workflow Automation | #4 of 11 in Container Orchestration |
| GitHub stars | 208 889 | 1 725 |
| Stars, last 30 days | +3 080 | — |
| Stable releases, 12 months | 205 | 9 |
| Latest release | n8n@3.0.1 · 28 Oct 2026 | 4.4.4 · 20 Oct 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | Other | Other |
| Main language | Typescript | Python |
Which one should you pick?
n8n scores 92/100 against 64/100 for Zero to JupyterHub with Kubernetes, so it is the safer default.
n8n ships more often: 205 stable releases in the past year, against 9 for Zero to JupyterHub with Kubernetes.
If you want the quickest setup, n8n is easier to run; Zero to JupyterHub with Kubernetes needs more configuration.
n8n is growing faster right now (+3 080 stars in 30 days).
n8n details →Zero to JupyterHub with Kubernetes details →
Swap a project
Keep n8n, compare it with
Keep Zero to JupyterHub with Kubernetes, compare it with