# DockerRegistry vs mitmproxy

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

| | DockerRegistry | mitmproxy |
|---|---|---|
| Score | 74/100 | 86/100 ✓ |
| Rank in category | #2 of 12 in Container Registry | #1 of 48 in Network Monitoring |
| GitHub stars | 10 666 | 46 459 ✓ |
| Stars, last 30 days | +43 | +1 324 ✓ |
| Stable releases, 12 months | 3 | 5 ✓ |
| Latest release | v3.1.2 · 24 Sept 2026 | v12.3.1 · 25 Oct 2026 ✓ |
| Setup | Easy ✓ | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | MIT |
| Main language | Go | Python |

## Which one should you pick?

mitmproxy scores 86/100 against 74/100 for DockerRegistry, so it is the safer default.

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

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

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

## Details

- [DockerRegistry](https://selfhost.directory/project/dockerregistry) (markdown: https://selfhost.directory/project/dockerregistry.md)
- [mitmproxy](https://selfhost.directory/project/mitmproxy) (markdown: https://selfhost.directory/project/mitmproxy.md)

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