bore vs boringproxy
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?
bore
Modern, simple TCP tunnel in Rust
VS
boringproxy
Simple self-hosted reverse proxy and tunnel manager
| Feature | bore | boringproxy |
|---|---|---|
| Category | Remote Access & VPN | Remote Access & VPN |
| License | MIT | MIT |
| Language | Rust | Go |
| Setup difficulty | Easy | Easy |
| Min. RAM | 64 MB | 64 MB |
| Deployment | binary, docker | binary, docker |
| GitHub stars | ★ 11,363 | ★ 1,381 |
| First released | 2022 | 2020 |
| Replaces | ngrok | ngrok |
Why pick each one
Choose bore if…
- Released under the MIT license
- Easy to set up — beginner-friendly
- First-class Docker support for quick deployment
- Mature project with 11.4k GitHub stars
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)
Frequently asked questions
Is bore or boringproxy better?
Neither is universally better. bore has the larger community; both share a easy setup difficulty, so the decision comes down to features and licensing.
Are bore and boringproxy free and open-source?
Yes. bore is licensed under MIT and boringproxy under MIT. Both can be self-hosted at no software cost.
Can I run bore and boringproxy with Docker?
bore: yes. boringproxy: yes.