frp vs Selkies
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?
frp
Fast reverse proxy to expose local servers behind NAT
VS
Selkies
Low-latency WebRTC remote desktop streaming
| Feature | frp | Selkies |
|---|---|---|
| Category | Remote Access & VPN | Remote Access & VPN |
| License | Apache-2.0 | MPL-2.0 |
| Language | Go | Python |
| Setup difficulty | Medium | Hard |
| Min. RAM | 64 MB | 2,048 MB |
| Deployment | binary, docker | docker, kubernetes |
| GitHub stars | ★ 108,622 | ★ 1,983 |
| First released | 2016 | 2019 |
| Replaces | ngrok | Parsec |
Why pick each one
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
Choose Selkies if…
- Released under the MPL-2.0 license
- First-class Docker support for quick deployment
- Kubernetes-ready with Helm charts available
- Active community (2k GitHub stars)
Frequently asked questions
Is frp or Selkies better?
frp is the stronger all-round pick: it has both the larger community and the simpler medium setup. Consider Selkies if its specific feature set fits your needs better.
Are frp and Selkies free and open-source?
Yes. frp is licensed under Apache-2.0 and Selkies under MPL-2.0. Both can be self-hosted at no software cost.
Can I run frp and Selkies with Docker?
frp: yes. Selkies: yes.