# Hermes-Secure-Email-Gateway vs mitmproxy

> Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.

| | Hermes-Secure-Email-Gateway | mitmproxy |
|---|---|---|
| Score | 48/100 | 86/100 ✓ |
| Rank in category | #49 of 78 in Security | #1 of 48 in Network Monitoring |
| GitHub stars | 141 | 46 475 ✓ |
| Stars, last 30 days | +0 | +1 331 ✓ |
| Stable releases, 12 months | 21 ✓ | 5 |
| Latest release | v261027 · 29 Oct 2026 ✓ | v12.3.1 · 25 Oct 2026 |
| Setup | Advanced | Moderate ✓ |
| Official Docker image | No | Yes ✓ |
| License | AGPL-3.0 | MIT |
| Main language | JavaScript | Python |

## Which one should you pick?

mitmproxy scores 86/100 against 48/100 for Hermes-Secure-Email-Gateway, so it is the safer default.

Hermes-Secure-Email-Gateway ships more often: 21 stable releases in the past year, against 5 for mitmproxy.

If you want the quickest setup, mitmproxy is easier to run; Hermes-Secure-Email-Gateway needs more configuration.

mitmproxy is growing faster right now (+1 331 stars in 30 days).

## Details

- [Hermes-Secure-Email-Gateway](https://selfhost.directory/project/hermes-secure-email-gateway) (markdown: https://selfhost.directory/project/hermes-secure-email-gateway.md)
- [mitmproxy](https://selfhost.directory/project/mitmproxy) (markdown: https://selfhost.directory/project/mitmproxy.md)

---
Source: https://selfhost.directory/compare/hermes-secure-email-gateway-vs-mitmproxy