# exo vs mitmproxy

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

| | exo | mitmproxy |
|---|---|---|
| Score | 76/100 | 86/100 ✓ |
| Rank in category | #6 of 25 in LLM Inference | #1 of 48 in Network Monitoring |
| GitHub stars | 48 082 ✓ | 46 471 |
| Stars, last 30 days | +447 | +1 327 ✓ |
| Stable releases, 12 months | 7 ✓ | 5 |
| Latest release | v1.0.71 · 23 Apr 2026 | v12.3.1 · 25 Oct 2026 ✓ |
| Setup | Easy ✓ | Moderate |
| Official Docker image | No | Yes ✓ |
| License | Apache-2.0 | MIT |
| Main language | Python | Python |

## Which one should you pick?

mitmproxy scores 86/100 against 76/100 for exo, so it is the safer default.

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

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

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

## Details

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

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