# fn-knock vs mitmproxy

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

| | fn-knock | mitmproxy |
|---|---|---|
| Score | 50/100 | 86/100 ✓ |
| Rank in category | #42 of 78 in Security | #1 of 48 in Network Monitoring |
| GitHub stars | 198 | 46 462 ✓ |
| Stars, last 30 days | — | +1 327 |
| Stable releases, 12 months | 10 ✓ | 5 |
| Latest release | v2.5.7 · 27 Oct 2026 ✓ | v12.3.1 · 25 Oct 2026 |
| Setup | Moderate | Moderate ✓ |
| Official Docker image | Yes | Yes |
| License | MIT | MIT |
| Main language | Rust | Python |

## Which one should you pick?

mitmproxy scores 86/100 against 50/100 for fn-knock, so it is the safer default.

fn-knock ships more often: 10 stable releases in the past year, against 5 for mitmproxy.

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

## Details

- [fn-knock](https://selfhost.directory/project/fn-knock-turborepo) (markdown: https://selfhost.directory/project/fn-knock-turborepo.md)
- [mitmproxy](https://selfhost.directory/project/mitmproxy) (markdown: https://selfhost.directory/project/mitmproxy.md)

---
Source: https://selfhost.directory/compare/fn-knock-turborepo-vs-mitmproxy