selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

ReconnervsZed Attack Proxy (ZAP)

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

ReconnerZed Attack Proxy (ZAP)
Score47/10080/100
Rank in category#53 of 78 in Security#3 of 78 in Security
GitHub stars13416 201
Stars, last 30 days+3+276
Stable releases, 12 months1234
Latest releasev4.8.0 · 26 Oct 2026w2026-11-11 · 11 Nov 2026
SetupModerateEasy
Official Docker imageYesYes
LicenseMITApache-2.0
Main languageGoJava

Which one should you pick?

Zed Attack Proxy (ZAP) scores 80/100 against 47/100 for Reconner, so it is the safer default.

Zed Attack Proxy (ZAP) ships more often: 34 stable releases in the past year, against 12 for Reconner.

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

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

Key differences

  • License: Reconner is MIT, Zed Attack Proxy (ZAP) is Apache-2.0.
  • Language: Reconner is written mainly in Go, Zed Attack Proxy (ZAP) in Java.
  • Features only Reconner lists: Attack surface discovery, Continuous operations, Custom wordlists and payloads, Evidence and reporting and 9 more.
  • Features only Zed Attack Proxy (ZAP) lists: Active scanning, Add-on marketplace / plugin architecture, API scanning, Authenticated scans and 10 more.

Swap a project

Keep Reconner, compare it with
Keep Zed Attack Proxy (ZAP), compare it with