boringproxy vs rathole
A side-by-side comparison of two self-hosted remote access & vpn options — licensing, setup difficulty, resource needs, and what each one replaces.
Not the right match-up?
boringproxy
Simple self-hosted reverse proxy and tunnel manager
VS
rathole
Lightweight and high-performance reverse proxy for NAT traversal
| Feature | boringproxy | rathole |
|---|---|---|
| Category | Remote Access & VPN | Remote Access & VPN |
| License | MIT | Apache-2.0 |
| Language | Go | Rust |
| Setup difficulty | Easy | Medium |
| Min. RAM | 64 MB | 64 MB |
| Deployment | binary, docker | binary, docker |
| GitHub stars | ★ 1,381 | ★ 13,999 |
| First released | 2020 | 2021 |
| Replaces | ngrok | ngrok, frp |
Why pick each one
Choose boringproxy if…
- Released under the MIT license
- Easy to set up — beginner-friendly
- First-class Docker support for quick deployment
- Active community (1.4k GitHub stars)
Choose rathole if…
- Released under the Apache-2.0 license
- First-class Docker support for quick deployment
- Mature project with 14k GitHub stars
- Written in Rust
Frequently asked questions
Is boringproxy or rathole better?
Neither is universally better. rathole has the larger community, while boringproxy is simpler to set up (easy difficulty). Choose based on the comparison table above and your own setup.
Are boringproxy and rathole free and open-source?
Yes. boringproxy is licensed under MIT and rathole under Apache-2.0. Both can be self-hosted at no software cost.
Can I run boringproxy and rathole with Docker?
boringproxy: yes. rathole: yes.