# ChronoFrame vs Zed Attack Proxy (ZAP)

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

| | ChronoFrame | Zed Attack Proxy (ZAP) |
|---|---|---|
| Score | 63/100 | 80/100 ✓ |
| Rank in category | #8 of 41 in Photo Management | #4 of 78 in Security |
| GitHub stars | 1 964 | 16 058 ✓ |
| Stars, last 30 days | +32 | +243 ✓ |
| Stable releases, 12 months | 3 | 31 ✓ |
| Latest release | v1.0.2 · 21 Oct 2026 | w2026-10-23 · 23 Oct 2026 ✓ |
| Setup | Easy ✓ | Easy |
| Official Docker image | Yes | Yes |
| License | AGPL-3.0 | Apache-2.0 |
| Main language | Typescript | Java |

## Which one should you pick?

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

Zed Attack Proxy (ZAP) ships more often: 31 stable releases in the past year, against 3 for ChronoFrame.

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

## Details

- [ChronoFrame](https://selfhost.directory/project/chronoframe) (markdown: https://selfhost.directory/project/chronoframe.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/chronoframe-vs-zed-attack-proxy-zap