ChartDBvsmitmproxy
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| ChartDB | mitmproxy | |
|---|---|---|
| Score | 74/100 | 86/100 |
| Rank in category | #7 of 40 in Database Management | #1 of 48 in Network Monitoring |
| GitHub stars | 23 026 | 46 459 |
| Stars, last 30 days | +76 | +1 324 |
| Stable releases, 12 months | 5 | 5 |
| Latest release | v1.20.1 · 7 Apr 2026 | v12.3.1 · 25 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | AGPL-3.0 | MIT |
| Main language | Typescript | Python |
Which one should you pick?
mitmproxy scores 86/100 against 74/100 for ChartDB, so it is the safer default.
If you want the quickest setup, ChartDB is easier to run; mitmproxy needs more configuration.
mitmproxy is growing faster right now (+1 324 stars in 30 days).
ChartDB details →mitmproxy details →
Swap a project
Keep ChartDB, compare it with
Keep mitmproxy, compare it with