bore vs frp
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?
| Feature | bore | frp |
|---|---|---|
| Category | Remote Access & VPN | Remote Access & VPN |
| License | MIT | Apache-2.0 |
| Language | Rust | Go |
| Setup difficulty | Easy | Medium |
| Min. RAM | 64 MB | 64 MB |
| Deployment | binary, docker | binary, docker |
| GitHub stars | ★ 11,363 | ★ 108,622 |
| First released | 2022 | 2016 |
| 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 frp if…
- Released under the Apache-2.0 license
- First-class Docker support for quick deployment
- Mature project with 108.6k GitHub stars
- Written in Go
Frequently asked questions
Is bore or frp better?
Neither is universally better. frp has the larger community, while bore is simpler to set up (easy difficulty). Choose based on the comparison table above and your own setup.
Are bore and frp free and open-source?
Yes. bore is licensed under MIT and frp under Apache-2.0. Both can be self-hosted at no software cost.
Can I run bore and frp with Docker?
bore: yes. frp: yes.