head to head · open source
frp vs nps
frp has 110,030 GitHub stars, 15,249 forks, 48 open issues and last shipped 2 days ago. nps has 1,089 stars, 156 forks, 15 open issues and last shipped 2 days ago. frp leads on adoption by 10,004% (110,030 vs 1,089 stars). frp is written in Go under Apache-2.0; nps is written in Go under GPL-3.0. frp has attracted 14% as many forks as stars, nps 14%. nps was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 8 topic tags (expose, firewall, frp, go), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| frp | nps | |
|---|---|---|
| GitHub stars | ★ 110K | ★ 1.1K |
| License | Apache-2.0 | GPL-3.0 |
| Written in | Go | Go |
| Last push | 2026-10-20 | 2026-10-20 |
| Forks | ⑂ 15K | ⑂ 156 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick frp if
- You weight community size — 110K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick nps if
- You want the nps feature set and don't need the biggest community
- You prefer the GPL-3.0 license terms
- Your stack matches Go
- You evaluated both and nps fits your workflow better
About frp
frp README 中文文档 Sponsors frp is an open source project with its ongoing development made possible entirely by the support of our awesome sponsors. If you'd like to join them, please consider sponsoring frp's development. Gold Sponsors High performance residential and ISP proxies for developers 90M+ residential IPs worldwide. Rotating IPs, sticky sessions, and traffic that never expires. From $0.55/GB. Use RAPID10 for 10% off. Try it for free. The complete IDE crafted for professional Go developers The sovereign cloud that puts you in control An open source, self hosted alternative to public clouds, built for…
About nps
NPS Enhanced An enhanced and actively maintained NAT traversal and reverse proxy system with Web UI. ⭐️ Give us a star on GitHub if you like it! 中文文档 Introduction NPS is a lightweight and efficient NAT traversal and reverse proxy system for exposing services behind NAT or firewalls. It supports multiple protocols such as TCP, UDP, HTTP, HTTPS, and SOCKS5, and provides a Web management interface for convenient deployment and monitoring. Based on the original NPS project, NPS Enhanced has evolved into an actively maintained and extensively improved edition with continuous refactoring, better stability, and many…
More in Infrastructure & Operations
Related comparisons
More Networking & Connectivity projects
Compare either of these against the rest of the Networking & Connectivity field.
Frequently asked questions
Is frp or nps more popular?
frp has 110,030 GitHub stars and nps has 1,089. frp has the larger community by that measure.
Are frp and nps free?
Both are open source. frp is licensed under Apache-2.0 and nps under GPL-3.0. Neither carries a licence fee.
What is the difference between frp and nps?
frp is written in Go and nps in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, frp or nps?
Choose frp if you want the larger community (110,030 stars) or its Apache-2.0 licence terms. Choose nps if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.