mitmproxyvsntopng
Two self-hosted Network Monitoring projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| mitmproxy | ntopng | |
|---|---|---|
| Score | 85/100 | 71/100 |
| Rank in category | #1 of 47 in Network Monitoring | #2 of 47 in Network Monitoring |
| GitHub stars | 47 002 | 8 351 |
| Stars, last 30 days | +1 533 | +110 |
| Stable releases, 12 months | 5 | 2 |
| Latest release | v12.3.1 · 25 Oct 2026 | 7.0 · 22 Sept 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | Yes | Yes |
| License | MIT | GPL-3.0 |
| Main language | Python | Lua |
Which one should you pick?
mitmproxy scores 85/100 against 71/100 for ntopng, so it is the safer default.
mitmproxy ships more often: 5 stable releases in the past year, against 2 for ntopng.
mitmproxy is growing faster right now (+1 533 stars in 30 days).
Key differences
- License: mitmproxy is MIT, ntopng is GPL-3.0.
- Language: mitmproxy is written mainly in Python, ntopng in Lua.
- Platforms only mitmproxy lists: Python.
- Platforms only ntopng lists: FreeBSD.
- Features only mitmproxy lists: Command-line interface (mitmdump), Console interface (mitmproxy), HTTP/1, HTTP/2, HTTP/3, and WebSocket support, Intercept, inspect, modify, and replay traffic and 6 more.
- Features only ntopng lists: Active monitoring, Behavioural checks and alerts, Historical reports and timeseries, Host geolocation and 11 more.
mitmproxy details →ntopng details →All Network Monitoring projects →