boringproxy vs zrok
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
zrok
Open-source sharing platform built on OpenZiti
| Feature | boringproxy | zrok |
|---|---|---|
| Category | Remote Access & VPN | Remote Access & VPN |
| License | MIT | Apache-2.0 |
| Language | Go | Go |
| Setup difficulty | Easy | Medium |
| Min. RAM | 64 MB | 256 MB |
| Deployment | binary, docker | docker, binary |
| GitHub stars | ★ 1,381 | ★ 4,611 |
| First released | 2020 | 2022 |
| Replaces | ngrok | ngrok |
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 zrok if…
- Released under the Apache-2.0 license
- First-class Docker support for quick deployment
- Active community (4.6k GitHub stars)
- Written in Go
Frequently asked questions
Is boringproxy or zrok better?
Neither is universally better. zrok 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 zrok free and open-source?
Yes. boringproxy is licensed under MIT and zrok under Apache-2.0. Both can be self-hosted at no software cost.
Can I run boringproxy and zrok with Docker?
boringproxy: yes. zrok: yes.