# Reactive Resume 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.

| | Reactive Resume | Zero to JupyterHub with Kubernetes |
|---|---|---|
| Score | 87/100 ✓ | 64/100 |
| Rank in category | #1 of 46 in Document Management | #4 of 11 in Container Orchestration |
| GitHub stars | 45 007 ✓ | 1 725 |
| Stars, last 30 days | +1 634 | — |
| Stable releases, 12 months | 34 ✓ | 9 |
| Latest release | v6.0.7 · 26 Oct 2026 ✓ | 4.4.4 · 20 Oct 2026 |
| Setup | Moderate ✓ | Advanced |
| Official Docker image | Yes | Yes |
| License | MIT | Other |
| Main language | Typescript | Python |

## Which one should you pick?

Reactive Resume scores 87/100 against 64/100 for Zero to JupyterHub with Kubernetes, so it is the safer default.

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

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

Reactive Resume is growing faster right now (+1 634 stars in 30 days).

## Details

- [Reactive Resume](https://selfhost.directory/project/reactive-resume) (markdown: https://selfhost.directory/project/reactive-resume.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/reactive-resume-vs-zero-to-jupyterhub-k8s