boringproxyvsmitmproxy
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| boringproxy | mitmproxy | |
|---|---|---|
| Score | 51/100 | 85/100 |
| Rank in category | #14 of 23 in Reverse Proxy | #1 of 47 in Network Monitoring |
| GitHub stars | 1 387 | 47 002 |
| Stars, last 30 days | +1 | +1 533 |
| Stable releases, 12 months | 0 | 5 |
| Latest release | — | v12.3.1 · 25 Oct 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | No | Yes |
| License | MIT | MIT |
| Main language | Go | Python |
Which one should you pick?
mitmproxy scores 85/100 against 51/100 for boringproxy, so it is the safer default.
mitmproxy ships more often: 5 stable releases in the past year, against 0 for boringproxy.
mitmproxy is growing faster right now (+1 533 stars in 30 days).
Key differences
- Language: boringproxy is written mainly in Go, mitmproxy in Python.
- Only mitmproxy ships an official Docker image.
- Platforms only boringproxy lists: Build from Source.
- Platforms only mitmproxy lists: Docker, Linux, macOS, Python and 1 more.
- Features only boringproxy lists: Automatic HTTPS, Client-scoped tokens, IPv6 Support, Proxy headers and 6 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.
boringproxy details →mitmproxy details →