corednsvsZero to JupyterHub with Kubernetes
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| coredns | Zero to JupyterHub with Kubernetes | |
|---|---|---|
| Score | 76/100 | 64/100 |
| Rank in category | #5 of 41 in DNS | #4 of 11 in Container Orchestration |
| GitHub stars | 14 400 | 1 725 |
| Stars, last 30 days | +60 | — |
| Stable releases, 12 months | 10 | 9 |
| Latest release | v1.15.0 · 21 Oct 2026 | 4.4.4 · 20 Oct 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | Other |
| Main language | Go | Python |
Which one should you pick?
coredns scores 76/100 against 64/100 for Zero to JupyterHub with Kubernetes, so it is the safer default.
coredns ships more often: 10 stable releases in the past year, against 9 for Zero to JupyterHub with Kubernetes.
If you want the quickest setup, coredns is easier to run; Zero to JupyterHub with Kubernetes needs more configuration.
coredns is growing faster right now (+60 stars in 30 days).
coredns details →Zero to JupyterHub with Kubernetes details →
Swap a project
Keep coredns, compare it with
Keep Zero to JupyterHub with Kubernetes, compare it with