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