mitmproxy vs go-doxy
A side-by-side comparison of two self-hosted reverse proxy & gateways options — licensing, setup difficulty, resource needs, and what each one replaces.
Not the right match-up?
mitmproxy
Interactive HTTPS proxy for inspection and debugging
VS
go-doxy
Lightweight, simple, and performant reverse proxy with WebUI, Docker
| Feature | mitmproxy | go-doxy |
|---|---|---|
| Category | Reverse Proxy & Gateways | Reverse Proxy & Gateways |
| License | MIT | MIT |
| Language | Python | Go |
| Setup difficulty | Easy | Medium |
| Min. RAM | 256 MB | 512 MB |
| Deployment | docker, binary, source | docker |
| GitHub stars | ★ 44,605 | ★ 3,826 |
| First released | 2010 | 2026 |
| Replaces | Charles Proxy, Fiddler | — |
Why pick each one
Choose go-doxy if…
- Released under the MIT license
- First-class Docker support for quick deployment
- Active community (3.8k GitHub stars)
- Written in Go
Frequently asked questions
Is mitmproxy or go-doxy better?
mitmproxy is the stronger all-round pick: it has both the larger community and the simpler easy setup. Consider go-doxy if its specific feature set fits your needs better.
Are mitmproxy and go-doxy free and open-source?
Yes. mitmproxy is licensed under MIT and go-doxy under MIT. Both can be self-hosted at no software cost.
Can I run mitmproxy and go-doxy with Docker?
mitmproxy: yes. go-doxy: yes.