# cState vs UUSEC WAF

> Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.

| | cState | UUSEC WAF |
|---|---|---|
| Score | 62/100 ✓ | 59/100 |
| Rank in category | #7 of 51 in Monitoring & observability | #2 of 3 in Web Application Firewall |
| GitHub stars | 2 901 ✓ | 1 718 |
| Stars, last 30 days | +6 | +6 |
| Stable releases, 12 months | 2 | 9 ✓ |
| Latest release | v7-r1 · 17 Oct 2026 ✓ | v7.2.6 · 12 Oct 2026 |
| Setup | Easy ✓ | Moderate |
| Official Docker image | No | No |
| License | MIT | BSD-2-Clause |
| Main language | HTML | Shell |

## Which one should you pick?

cState scores 62/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 2 for cState.

If you want the quickest setup, cState is easier to run; UUSEC WAF needs more configuration.

## Details

- [cState](https://selfhost.directory/project/cstate) (markdown: https://selfhost.directory/project/cstate.md)
- [UUSEC WAF](https://selfhost.directory/project/uusec-waf) (markdown: https://selfhost.directory/project/uusec-waf.md)

---
Source: https://selfhost.directory/compare/cstate-vs-uusec-waf