JellyfinvsSignal TLS Proxy
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Jellyfin | Signal TLS Proxy | |
|---|---|---|
| Score | 88/100 | 49/100 |
| Rank in category | #1 of 118 in Media Server | #16 of 25 in Proxy |
| GitHub stars | 58 754 | 1 284 |
| Stars, last 30 days | +1 311 | — |
| Stable releases, 12 months | 15 | 0 |
| Latest release | v12.4 · 26 Oct 2026 | — |
| Setup | Moderate | Easy |
| Official Docker image | Yes | No |
| License | GPL-2.0 | MIT |
| Main language | C | Shell |
Which one should you pick?
Jellyfin scores 88/100 against 49/100 for Signal TLS Proxy, so it is the safer default.
Jellyfin ships more often: 15 stable releases in the past year, against 0 for Signal TLS Proxy.
If you want the quickest setup, Signal TLS Proxy is easier to run; Jellyfin needs more configuration.
Jellyfin is growing faster right now (+1 311 stars in 30 days).
Jellyfin details →Signal TLS Proxy details →
Swap a project
Keep Jellyfin, compare it with
Keep Signal TLS Proxy, compare it with