Gitnessvsmitmproxy
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Gitness | mitmproxy | |
|---|---|---|
| Score | 80/100 | 86/100 |
| Rank in category | #2 of 14 in Code Hosting | #1 of 48 in Network Monitoring |
| GitHub stars | 38 745 | 46 446 |
| Stars, last 30 days | +318 | +1 311 |
| Stable releases, 12 months | 6 | 5 |
| Latest release | v2.28.2 · 20 Apr 2026 | v12.3.1 · 25 Oct 2026 |
| Setup | Easy | 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 80/100 for Gitness, so it is the safer default.
Gitness ships more often: 6 stable releases in the past year, against 5 for mitmproxy.
If you want the quickest setup, Gitness is easier to run; mitmproxy needs more configuration.
mitmproxy is growing faster right now (+1 311 stars in 30 days).
Gitness details →mitmproxy details →