# Incus vs mitmproxy

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

| | Incus | mitmproxy |
|---|---|---|
| Score | 75/100 | 86/100 ✓ |
| Rank in category | #3 of 44 in Container Management | #1 of 48 in Network Monitoring |
| GitHub stars | 6 519 | 46 462 ✓ |
| Stars, last 30 days | +273 | +1 318 ✓ |
| Stable releases, 12 months | 16 ✓ | 5 |
| Latest release | v7.0.2 · 16 Oct 2026 | v12.3.1 · 25 Oct 2026 ✓ |
| Setup | Advanced | Moderate ✓ |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | MIT |
| Main language | Go | Python |

## Which one should you pick?

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

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

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

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

## Details

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

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