Algernon vs mitmproxy
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?
Algernon
Small self-contained pure-Go web server with Lua, Markdown, HTTP/2,
VS
mitmproxy
Interactive HTTPS proxy for inspection and debugging
| Feature | Algernon | mitmproxy |
|---|---|---|
| Category | Reverse Proxy & Gateways | Reverse Proxy & Gateways |
| License | BSD-3-Clause | MIT |
| Language | JavaScript | Python |
| Setup difficulty | Medium | Easy |
| Min. RAM | 512 MB | 256 MB |
| Deployment | docker | docker, binary, source |
| GitHub stars | ★ 3,023 | ★ 44,605 |
| First released | 2026 | 2010 |
| Replaces | — | Charles Proxy, Fiddler |
Why pick each one
Choose Algernon if…
- Released under the BSD-3-Clause license
- First-class Docker support for quick deployment
- Active community (3k GitHub stars)
- Written in JavaScript
Frequently asked questions
Is Algernon or mitmproxy better?
mitmproxy is the stronger all-round pick: it has both the larger community and the simpler easy setup. Consider Algernon if its specific feature set fits your needs better.
Are Algernon and mitmproxy free and open-source?
Yes. Algernon is licensed under BSD-3-Clause and mitmproxy under MIT. Both can be self-hosted at no software cost.
Can I run Algernon and mitmproxy with Docker?
Algernon: yes. mitmproxy: yes.