# dify vs Zed Attack Proxy (ZAP)

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

| | dify | Zed Attack Proxy (ZAP) |
|---|---|---|
| Score | 90/100 ✓ | 80/100 |
| Rank in category | #1 of 7 in AI Workflows | #4 of 78 in Security |
| GitHub stars | 159 827 ✓ | 16 058 |
| Stars, last 30 days | +2 817 ✓ | +243 |
| Stable releases, 12 months | 15 | 31 ✓ |
| Latest release | 1.18.0 · 23 Oct 2026 | w2026-10-23 · 23 Oct 2026 |
| Setup | Moderate | Easy ✓ |
| Official Docker image | Yes | Yes |
| License | Other | Apache-2.0 |
| Main language | Python | Java |

## Which one should you pick?

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

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

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

dify is growing faster right now (+2 817 stars in 30 days).

## Details

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