beamvsUUSEC WAF
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| beam | UUSEC WAF | |
|---|---|---|
| Score | 61/100 | 59/100 |
| Rank in category | #29 of 125 in AI | #2 of 3 in Web Application Firewall |
| GitHub stars | 1 834 | 1 718 |
| Stars, last 30 days | +47 | +6 |
| Stable releases, 12 months | 364 | 9 |
| Latest release | gateway-0.1.837 · 26 Oct 2026 | v7.2.6 · 12 Oct 2026 |
| Setup | Advanced | Moderate |
| Official Docker image | No | No |
| License | AGPL-3.0 | BSD-2-Clause |
| Main language | Go | Shell |
Which one should you pick?
beam scores 61/100 against 59/100 for UUSEC WAF, so it is the safer default.
beam ships more often: 364 stable releases in the past year, against 9 for UUSEC WAF.
If you want the quickest setup, UUSEC WAF is easier to run; beam needs more configuration.
beam is growing faster right now (+47 stars in 30 days).
beam details →UUSEC WAF details →
Swap a project
Keep beam, compare it with
Keep UUSEC WAF, compare it with