go2rtcvsUUSEC WAF
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| go2rtc | UUSEC WAF | |
|---|---|---|
| Score | 74/100 | 59/100 |
| Rank in category | #4 of 54 in Media Streaming | #2 of 3 in Web Application Firewall |
| GitHub stars | 14 518 | 1 718 |
| Stars, last 30 days | +272 | +6 |
| Stable releases, 12 months | 5 | 9 |
| Latest release | v1.9.15 · 25 Oct 2026 | v7.2.6 · 12 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | No |
| License | MIT | BSD-2-Clause |
| Main language | Go | Shell |
Which one should you pick?
go2rtc scores 74/100 against 59/100 for UUSEC WAF, so it is the safer default.
UUSEC WAF ships more often: 9 stable releases in the past year, against 5 for go2rtc.
If you want the quickest setup, go2rtc is easier to run; UUSEC WAF needs more configuration.
go2rtc is growing faster right now (+272 stars in 30 days).
go2rtc details →UUSEC WAF details →
Swap a project
Keep go2rtc, compare it with
Keep UUSEC WAF, compare it with