# Gitness vs Zero to JupyterHub with Kubernetes

> Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.

| | Gitness | Zero to JupyterHub with Kubernetes |
|---|---|---|
| Score | 80/100 ✓ | 64/100 |
| Rank in category | #2 of 14 in Code Hosting | #4 of 11 in Container Orchestration |
| GitHub stars | 38 746 ✓ | 1 725 |
| Stars, last 30 days | +319 | — |
| Stable releases, 12 months | 6 | 9 ✓ |
| Latest release | v2.28.2 · 20 Apr 2026 | 4.4.4 · 20 Oct 2026 ✓ |
| Setup | Easy ✓ | Advanced |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | Other |
| Main language | Go | Python |

## Which one should you pick?

Gitness scores 80/100 against 64/100 for Zero to JupyterHub with Kubernetes, so it is the safer default.

Zero to JupyterHub with Kubernetes ships more often: 9 stable releases in the past year, against 6 for Gitness.

If you want the quickest setup, Gitness is easier to run; Zero to JupyterHub with Kubernetes needs more configuration.

Gitness is growing faster right now (+319 stars in 30 days).

## Details

- [Gitness](https://selfhost.directory/project/gitness) (markdown: https://selfhost.directory/project/gitness.md)
- [Zero to JupyterHub with Kubernetes](https://selfhost.directory/project/zero-to-jupyterhub-k8s) (markdown: https://selfhost.directory/project/zero-to-jupyterhub-k8s.md)

---
Source: https://selfhost.directory/compare/gitness-vs-zero-to-jupyterhub-k8s