# open-compute vs Zed Attack Proxy (ZAP)

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

| | open-compute | Zed Attack Proxy (ZAP) |
|---|---|---|
| Score | 55/100 | 80/100 ✓ |
| Rank in category | #3 of 7 in Serverless | #4 of 78 in Security |
| GitHub stars | 2 369 | 16 059 ✓ |
| Stars, last 30 days | — | +244 |
| Stable releases, 12 months | 9 | 31 ✓ |
| Latest release | v0.3.0 · 10 Oct 2026 | w2026-10-23 · 23 Oct 2026 ✓ |
| Setup | Moderate | Easy ✓ |
| Official Docker image | No | Yes ✓ |
| License | Apache-2.0 | Apache-2.0 |
| Main language | Rust | Java |

## Which one should you pick?

Zed Attack Proxy (ZAP) scores 80/100 against 55/100 for open-compute, so it is the safer default.

Zed Attack Proxy (ZAP) ships more often: 31 stable releases in the past year, against 9 for open-compute.

If you want the quickest setup, Zed Attack Proxy (ZAP) is easier to run; open-compute needs more configuration.

Zed Attack Proxy (ZAP) is growing faster right now (+244 stars in 30 days).

## Details

- [open-compute](https://selfhost.directory/project/open-compute) (markdown: https://selfhost.directory/project/open-compute.md)
- [Zed Attack Proxy (ZAP)](https://selfhost.directory/project/zed-attack-proxy-zap) (markdown: https://selfhost.directory/project/zed-attack-proxy-zap.md)

---
Source: https://selfhost.directory/compare/open-compute-vs-zed-attack-proxy-zap