# mitmproxy vs Warpgate

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

| | mitmproxy | Warpgate |
|---|---|---|
| Score | 86/100 ✓ | 75/100 |
| Rank in category | #1 of 48 in Network Monitoring | #11 of 78 in Security |
| GitHub stars | 46 441 ✓ | 8 158 |
| Stars, last 30 days | +1 306 ✓ | +198 |
| Stable releases, 12 months | 5 | 33 ✓ |
| Latest release | v12.3.1 · 25 Oct 2026 | v0.30.2 · 26 Oct 2026 ✓ |
| Setup | Moderate | Easy ✓ |
| Official Docker image | Yes | Yes |
| License | MIT | Apache-2.0 |
| Main language | Python | Rust |

## Which one should you pick?

mitmproxy scores 86/100 against 75/100 for Warpgate, so it is the safer default.

Warpgate ships more often: 33 stable releases in the past year, against 5 for mitmproxy.

If you want the quickest setup, Warpgate is easier to run; mitmproxy needs more configuration.

mitmproxy is growing faster right now (+1 306 stars in 30 days).

## Details

- [mitmproxy](https://selfhost.directory/project/mitmproxy) (markdown: https://selfhost.directory/project/mitmproxy.md)
- [Warpgate](https://selfhost.directory/project/warpgate) (markdown: https://selfhost.directory/project/warpgate.md)

---
Source: https://selfhost.directory/compare/mitmproxy-vs-warpgate