# Metabase vs Zed Attack Proxy (ZAP)

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

| | Metabase | Zed Attack Proxy (ZAP) |
|---|---|---|
| Score | 83/100 ✓ | 80/100 |
| Rank in category | #2 of 15 in Business Intelligence | #4 of 78 in Security |
| GitHub stars | 49 911 ✓ | 16 061 |
| Stars, last 30 days | +513 ✓ | +246 |
| Stable releases, 12 months | 30 | 31 ✓ |
| Latest release | v0.64.1 · 6 Oct 2026 | w2026-10-23 · 23 Oct 2026 ✓ |
| Setup | Moderate | Easy ✓ |
| Official Docker image | Yes | Yes |
| License | Other | Apache-2.0 |
| Main language | Clojure | Java |

## Which one should you pick?

Metabase scores 83/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 30 for Metabase.

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

Metabase is growing faster right now (+513 stars in 30 days).

## Details

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