# Encore vs mitmproxy

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

| | Encore | mitmproxy |
|---|---|---|
| Score | 72/100 | 86/100 ✓ |
| Rank in category | #4 of 14 in Platform as a Service | #1 of 48 in Network Monitoring |
| GitHub stars | 12 651 | 46 462 ✓ |
| Stars, last 30 days | +166 | +1 327 ✓ |
| Stable releases, 12 months | 9 ✓ | 5 |
| Latest release | v1.58.8 · 20 Oct 2026 | v12.3.1 · 25 Oct 2026 ✓ |
| Setup | Moderate | Moderate ✓ |
| Official Docker image | No | Yes ✓ |
| License | MPL-2.0 | MIT |
| Main language | Go | Python |

## Which one should you pick?

mitmproxy scores 86/100 against 72/100 for Encore, so it is the safer default.

Encore ships more often: 9 stable releases in the past year, against 5 for mitmproxy.

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

## Details

- [Encore](https://selfhost.directory/project/encore) (markdown: https://selfhost.directory/project/encore.md)
- [mitmproxy](https://selfhost.directory/project/mitmproxy) (markdown: https://selfhost.directory/project/mitmproxy.md)

---
Source: https://selfhost.directory/compare/encore-vs-mitmproxy