head to head · open source
frp vs landscape
frp has 110,566 GitHub stars, 15,318 forks, 48 open issues and last shipped 3 days ago. landscape has 1,598 stars, 125 forks, 29 open issues and last shipped yesterday. frp leads on adoption by 6,819% (110,566 vs 1,598 stars). frp is written in Go under Apache-2.0; landscape is written in Rust under GPL-3.0. frp has attracted 14% as many forks as stars, landscape 8%. landscape was the more recently maintained of the two, and both are self-hostable with no licence fee.
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 | landscape | |
|---|---|---|
| GitHub stars | ★ 111K | ★ 1.6K |
| License | Apache-2.0 | GPL-3.0 |
| Written in | Go | Rust |
| Last push | 2026-11-10 | 2026-11-12 |
| Forks | ⑂ 15K | ⑂ 125 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick frp if
- You weight community size — 111K 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 landscape if
- You want the landscape feature set and don't need the biggest community
- You prefer the GPL-3.0 license terms
- Your stack matches Rust
- You evaluated both and landscape 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 landscape
Landscape routes traffic by domain—not just IP. Each flow gets its own DNS server. DNS answers populate kernel eBPF maps. Packets are steered at XDP/TC. No userspace datapath. No iptables. Built with Rust / eBPF. 简体中文 English Documentation Screenshot Architecture Landscape separates traffic steering into two planes: DNS plane (userspace). A flow is a policy group that devices join by IP or MAC. Each flow gets its own isolated Hickory DNS server with independent cache, upstream (UDP/DoH/DoT/DoQ), and rules. DNS answers populate per flow eBPF maps in the kernel. Data plane (kernel). XDP and TC hooks read these…
read the full landscape overview →
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 landscape more popular?
frp has 110,566 GitHub stars and landscape has 1,598. frp has the larger community by that measure.
Are frp and landscape free?
Both are open source. frp is licensed under Apache-2.0 and landscape under GPL-3.0. Neither carries a licence fee.
What is the difference between frp and landscape?
frp is written in Go and landscape in Rust. 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 landscape?
Choose frp if you want the larger community (110,566 stars) or its Apache-2.0 licence terms. Choose landscape if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.