Gitnessvshls-restream-proxy
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Gitness | hls-restream-proxy | |
|---|---|---|
| Score | 80/100 | 46/100 |
| Rank in category | #2 of 14 in Code Hosting | #42 of 54 in Media Streaming |
| GitHub stars | 38 748 | 255 |
| Stars, last 30 days | +321 | — |
| Stable releases, 12 months | 6 | 0 |
| Latest release | v2.28.2 · 20 Apr 2026 | — |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | MIT |
| Main language | Go | Python |
Which one should you pick?
Gitness scores 80/100 against 46/100 for hls-restream-proxy, so it is the safer default.
Gitness ships more often: 6 stable releases in the past year, against 0 for hls-restream-proxy.
If you want the quickest setup, Gitness is easier to run; hls-restream-proxy needs more configuration.
Gitness is growing faster right now (+321 stars in 30 days).
Gitness details →hls-restream-proxy details →