# mem0 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.

| | mem0 | Zero to JupyterHub with Kubernetes |
|---|---|---|
| Score | 86/100 ✓ | 64/100 |
| Rank in category | #2 of 166 in Developer Tools | #4 of 11 in Container Orchestration |
| GitHub stars | 68 006 ✓ | 1 725 |
| Stars, last 30 days | +2 093 | — |
| Stable releases, 12 months | 82 ✓ | 9 |
| Latest release | ts-v3.3.1 · 25 Sept 2026 | 4.4.4 · 20 Oct 2026 ✓ |
| Setup | Easy ✓ | Advanced |
| Official Docker image | No | Yes ✓ |
| License | Apache-2.0 | Other |
| Main language | Python | Python |

## Which one should you pick?

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

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

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

mem0 is growing faster right now (+2 093 stars in 30 days).

## Details

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