TypesensevsUUSEC WAF
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Typesense | UUSEC WAF | |
|---|---|---|
| Score | 79/100 | 59/100 |
| Rank in category | #6 of 41 in Search Engines | #2 of 3 in Web Application Firewall |
| GitHub stars | 27 062 | 1 718 |
| Stars, last 30 days | +476 | +6 |
| Stable releases, 12 months | 4 | 9 |
| Latest release | v30.2 · 19 Apr 2026 | v7.2.6 · 12 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | No |
| License | GPL-3.0 | BSD-2-Clause |
| Main language | C | Shell |
Which one should you pick?
Typesense scores 79/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 4 for Typesense.
If you want the quickest setup, Typesense is easier to run; UUSEC WAF needs more configuration.
Typesense is growing faster right now (+476 stars in 30 days).
Typesense details →UUSEC WAF details →
Swap a project
Keep Typesense, compare it with
Keep UUSEC WAF, compare it with