Incusvsmitmproxy
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 517 | 46 462 |
| Stars, last 30 days | +277 | +1 327 |
| 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 327 stars in 30 days).
Incus details →mitmproxy details →
Swap a project
Keep Incus, compare it with
Keep mitmproxy, compare it with