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