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