Docker Enginevsmitmproxy
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Docker Engine | mitmproxy | |
|---|---|---|
| Score | 80/100 | 86/100 |
| Rank in category | #1 of 11 in Container Orchestration | #1 of 48 in Network Monitoring |
| GitHub stars | 72 222 | 46 462 |
| Stars, last 30 days | +90 | +1 327 |
| Stable releases, 12 months | 17 | 5 |
| Latest release | docker-v29.9.2 · 20 Oct 2026 | v12.3.1 · 25 Oct 2026 |
| Setup | Advanced | Moderate |
| Official Docker image | No | Yes |
| License | Apache-2.0 | MIT |
| Main language | Go | Python |
Which one should you pick?
mitmproxy scores 86/100 against 80/100 for Docker Engine, so it is the safer default.
Docker Engine ships more often: 17 stable releases in the past year, against 5 for mitmproxy.
If you want the quickest setup, mitmproxy is easier to run; Docker Engine needs more configuration.
mitmproxy is growing faster right now (+1 327 stars in 30 days).
Docker Engine details →mitmproxy details →
Swap a project
Keep Docker Engine, compare it with
Keep mitmproxy, compare it with