Gotenbergvsmitmproxy
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Gotenberg | mitmproxy | |
|---|---|---|
| Score | 77/100 | 86/100 |
| Rank in category | #2 of 12 in Document Processing | #1 of 48 in Network Monitoring |
| GitHub stars | 13 476 | 46 477 |
| Stars, last 30 days | +320 | +1 333 |
| Stable releases, 12 months | 16 | 5 |
| Latest release | v8.39.0 · 27 Oct 2026 | v12.3.1 · 25 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | MIT | MIT |
| Main language | Go | Python |
Which one should you pick?
mitmproxy scores 86/100 against 77/100 for Gotenberg, so it is the safer default.
Gotenberg ships more often: 16 stable releases in the past year, against 5 for mitmproxy.
If you want the quickest setup, Gotenberg is easier to run; mitmproxy needs more configuration.
mitmproxy is growing faster right now (+1 333 stars in 30 days).
Gotenberg details →mitmproxy details →
Swap a project
Keep Gotenberg, compare it with
Keep mitmproxy, compare it with