# mitmproxy vs RemoteTerm for MeshCore

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

| | mitmproxy | RemoteTerm for MeshCore |
|---|---|---|
| Score | 86/100 ✓ | 45/100 |
| Rank in category | #1 of 48 in Network Monitoring | #4 of 4 in Amateur Radio |
| GitHub stars | 46 459 ✓ | 337 |
| Stars, last 30 days | +1 324 | — |
| Stable releases, 12 months | 5 | 10 ✓ |
| Latest release | v12.3.1 · 25 Oct 2026 ✓ | 3.17.1 · 26 Jul 2026 |
| Setup | Moderate ✓ | Advanced |
| Official Docker image | Yes | Yes |
| License | MIT | MIT |
| Main language | Python | Python |

## Which one should you pick?

mitmproxy scores 86/100 against 45/100 for RemoteTerm for MeshCore, so it is the safer default.

RemoteTerm for MeshCore ships more often: 10 stable releases in the past year, against 5 for mitmproxy.

If you want the quickest setup, mitmproxy is easier to run; RemoteTerm for MeshCore needs more configuration.

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

## Details

- [mitmproxy](https://selfhost.directory/project/mitmproxy) (markdown: https://selfhost.directory/project/mitmproxy.md)
- [RemoteTerm for MeshCore](https://selfhost.directory/project/remote-terminal-for-meshcore) (markdown: https://selfhost.directory/project/remote-terminal-for-meshcore.md)

---
Source: https://selfhost.directory/compare/mitmproxy-vs-remote-terminal-for-meshcore