beamvsZed Attack Proxy (ZAP)
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| beam | Zed Attack Proxy (ZAP) | |
|---|---|---|
| Score | 61/100 | 80/100 |
| Rank in category | #29 of 125 in AI | #4 of 78 in Security |
| GitHub stars | 1 834 | 16 059 |
| Stars, last 30 days | +47 | +244 |
| Stable releases, 12 months | 364 | 31 |
| Latest release | gateway-0.1.837 · 26 Oct 2026 | w2026-10-23 · 23 Oct 2026 |
| Setup | Advanced | Easy |
| Official Docker image | No | Yes |
| License | AGPL-3.0 | Apache-2.0 |
| Main language | Go | Java |
Which one should you pick?
Zed Attack Proxy (ZAP) scores 80/100 against 61/100 for beam, so it is the safer default.
beam ships more often: 364 stable releases in the past year, against 31 for Zed Attack Proxy (ZAP).
If you want the quickest setup, Zed Attack Proxy (ZAP) is easier to run; beam needs more configuration.
Zed Attack Proxy (ZAP) is growing faster right now (+244 stars in 30 days).
beam details →Zed Attack Proxy (ZAP) details →
Swap a project
Keep beam, compare it with
Keep Zed Attack Proxy (ZAP), compare it with