Knock-Knockvsmitmproxy
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Knock-Knock | mitmproxy | |
|---|---|---|
| Score | 48/100 | 86/100 |
| Rank in category | #49 of 78 in Security | #1 of 48 in Network Monitoring |
| GitHub stars | 214 | 46 462 |
| Stars, last 30 days | — | +1 327 |
| Stable releases, 12 months | 5 | 5 |
| Latest release | v3.0.0 · 26 Jul 2026 | v12.3.1 · 25 Oct 2026 |
| Setup | Advanced | Moderate |
| Official Docker image | Yes | Yes |
| License | MIT | MIT |
| Main language | Python | Python |
Which one should you pick?
mitmproxy scores 86/100 against 48/100 for Knock-Knock, so it is the safer default.
If you want the quickest setup, mitmproxy is easier to run; Knock-Knock needs more configuration.
mitmproxy is growing faster right now (+1 327 stars in 30 days).
Knock-Knock details →mitmproxy details →
Swap a project
Keep Knock-Knock, compare it with
Keep mitmproxy, compare it with