hettyvsmitmproxy
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| hetty | mitmproxy | |
|---|---|---|
| Score | 64/100 | 85/100 |
| Rank in category | #24 of 78 in Security | #1 of 47 in Network Monitoring |
| GitHub stars | 12 548 | 47 010 |
| Stars, last 30 days | +35 | +1 541 |
| Stable releases, 12 months | 0 | 5 |
| Latest release | — | v12.3.1 · 25 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | MIT | MIT |
| Main language | Go | Python |
Which one should you pick?
mitmproxy scores 85/100 against 64/100 for hetty, so it is the safer default.
mitmproxy ships more often: 5 stable releases in the past year, against 0 for hetty.
If you want the quickest setup, hetty is easier to run; mitmproxy needs more configuration.
mitmproxy is growing faster right now (+1 541 stars in 30 days).
Key differences
- Language: hetty is written mainly in Go, mitmproxy in Python.
- Platforms only mitmproxy lists: Python.
- Features only hetty lists: Advanced search, Chrome Integration, HTTP Client, JSON log output and 5 more.
- Features only mitmproxy lists: Command-line interface (mitmdump), Console interface (mitmproxy), HTTP/1, HTTP/2, HTTP/3, and WebSocket support, Intercept, inspect, modify, and replay traffic and 6 more.
hetty details →mitmproxy details →
Swap a project
Keep hetty, compare it with
Keep mitmproxy, compare it with