head to head · open source

frp vs wiredoor

frp has 109,775 GitHub stars, 15,236 forks, 48 open issues and last shipped 23 days ago. wiredoor has 1,623 stars, 78 forks, 9 open issues and last shipped yesterday. frp leads on adoption by 6,664% (109,775 vs 1,623 stars). frp is written in Go under Apache-2.0; wiredoor is written in TypeScript under Apache-2.0. frp has attracted 14% as many forks as stars, wiredoor 5%. wiredoor was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (reverse-proxy), 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.

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

← all 20902 open source comparisons

Side by side

frp wiredoor
GitHub stars ★ 110K ★ 1.6K
License Apache-2.0 Apache-2.0
Written in Go TypeScript
Last push 2026-09-15 2026-10-07
Forks ⑂ 15K ⑂ 78
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 wiredoor if

  • You want the wiredoor feature set and don't need the biggest community
  • You prefer the Apache-2.0 license terms
  • Your stack matches TypeScript
  • You evaluated both and wiredoor fits your workflow better

full wiredoor 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 wiredoor

wiredoor is a self hosted ingress as a service platform for developers and infrastructure operators who need to expose HTTP, TCP, and UDP services running behind NAT or firewalls in private networks to the internet.

read the full wiredoor overview →

More in Infrastructure & Operations

kubernetes ★ 128K Immich ★ 116K Uptime Kuma ★ 92K worldmonitor ★ 88K 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 wiredoor more popular?

frp has 109,775 GitHub stars and wiredoor has 1,623. frp has the larger community by that measure.

Are frp and wiredoor free?

Both are open source. frp is licensed under Apache-2.0 and wiredoor under Apache-2.0. Neither carries a licence fee.

What is the difference between frp and wiredoor?

frp is written in Go and wiredoor in TypeScript. 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 wiredoor?

Choose frp if you want the larger community (109,775 stars) or its Apache-2.0 licence terms. Choose wiredoor if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.