temporalvsUptime-Kuma-Web-API
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| temporal | Uptime-Kuma-Web-API | |
|---|---|---|
| Score | 82/100 | 39/100 |
| Rank in category | #1 of 1 in Workflow | #12 of 13 in API |
| GitHub stars | 24 064 | 282 |
| Stars, last 30 days | +786 | +0 |
| Stable releases, 12 months | 11 | 0 |
| Latest release | v1.30.8 · 12 Oct 2026 | — |
| Setup | Advanced | Moderate |
| Official Docker image | Yes | Yes |
| License | MIT | — |
| Main language | Go | Python |
Which one should you pick?
temporal scores 82/100 against 39/100 for Uptime-Kuma-Web-API, so it is the safer default.
temporal ships more often: 11 stable releases in the past year, against 0 for Uptime-Kuma-Web-API.
If you want the quickest setup, Uptime-Kuma-Web-API is easier to run; temporal needs more configuration.
temporal is growing faster right now (+786 stars in 30 days).
temporal details →Uptime-Kuma-Web-API details →
Swap a project
Keep temporal, compare it with
Keep Uptime-Kuma-Web-API, compare it with