head to head · open source

frp vs landscape

frp has 109,663 GitHub stars, 15,227 forks, 48 open issues and last shipped 13 days ago. landscape has 1,558 stars, 121 forks, 29 open issues and last shipped today. frp leads on adoption by 6,939% (109,663 vs 1,558 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.

frp ★ 110K landscape ★ 1.6K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

frp landscape
GitHub stars ★ 110K ★ 1.6K
License Apache-2.0 GPL-3.0
Written in Go Rust
Last push 2026-09-15 2026-09-28
Forks ⑂ 15K ⑂ 121
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

full frp profile →

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

full landscape profile →

About frp

frp is a fast reverse proxy written in Go that exposes a local server behind a NAT or firewall to the internet, built for operators and developers who need inbound access to machines they cannot port forward.

read the full frp overview →

About landscape

Landscape is an open source router platform that configures a standard Linux distribution as a router by steering traffic by domain rather than IP alone, built in Rust with eBPF and aimed at self hosters who want policy routing on hardware and distributions they already control.

read the full landscape overview →

More in Infrastructure & Operations

kubernetes ★ 128K Immich ★ 115K Uptime Kuma ★ 92K worldmonitor ★ 87K mall ★ 85K NetData ★ 81K

Related comparisons

frp vs caddy frp vs traefik frp vs adguardhome frp vs nginx frp vs algo frp vs nginx-proxy frp vs plakar frp vs pluton caddy vs traefik immich vs openvpn n8n vs huginn uptime-kuma vs worldmonitor uptime-kuma vs netdata uptime-kuma vs grafana worldmonitor vs netdata worldmonitor vs grafana uptime-kuma vs prometheus netdata vs grafana n8n vs kestra langchain vs haystack kubernetes vs rancher ansible vs compose ansible vs conductor ansible vs xxl-job

More Networking & Connectivity projects

Compare either of these against the rest of the Networking & Connectivity field.

frp vs caddy frp vs traefik frp vs AdGuardHome frp vs nginx frp vs algo frp vs nginx-proxy frp vs goproxy frp vs openvpn-install frp vs cloudflared frp vs amnezia-client frp vs OpenVPN frp vs coredns

Frequently asked questions

Is frp or landscape more popular?

frp has 109,663 GitHub stars and landscape has 1,558. 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 (109,663 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.