frpc-desktop vs Wiredoor
FRP tunnel management and self-hosted ingress compared
frpc-desktop is a graphical client for configuring and managing FRP tunnels, while Wiredoor is a self-hosted ingress platform built on WireGuard and NGINX. The main difference is scope: frpc-desktop manages FRP client proxies, whereas Wiredoor routes services through a server you operate.
frpc-desktop: Manage FRP Tunnels with a Desktop App
Frpc-Desktop is a cross-platform desktop client for configuring and managing FRP tunnels. It suits people who want a visual alternative to editing frpc configuration files, with support for multiple proxy types and configuration import and export.
Wiredoor: Self-Host Ingress over WireGuard
Wiredoor is a self-hosted ingress platform built on WireGuard and NGINX for exposing HTTP, TCP, and UDP services on private networks. It connects Linux, Windows, and macOS client nodes, plus Docker and Kubernetes gateways, to a server you control.
| frpc-desktop | Wiredoor | |
|---|---|---|
| Language | TypeScript | TypeScript |
| License | MIT | Apache-2.0 |
| Stars | 6.9k | 1.6k |
| Forks | 498 | 77 |
| Last analyzed | Oct 3, 2026 | Oct 16, 2026 |
Key differences
- frpc-desktop focuses on managing FRP client proxies; Wiredoor exposes HTTP, TCP, and UDP services through WireGuard tunnels and NGINX.
- frpc-desktop provides a desktop interface with configuration import and export; Wiredoor provides a web dashboard and CLI for managing nodes, domains, and services.
- Wiredoor supports Linux, Windows, and macOS client nodes, plus Docker and Kubernetes gateways; frpc-desktop is a desktop client with platform-specific guidance for Linux and macOS.
- Wiredoor requires a reachable server and network access for HTTP/HTTPS and the WireGuard port; frpc-desktop is a client and still requires a working FRP server.
- frpc-desktop uses the MIT License; Wiredoor uses Apache-2.0, with versions before 1.5.1 identified as MIT-licensed.
- The supplied project facts list 6.9k stars and 498 forks for frpc-desktop, compared with 1.6k stars and 77 forks for Wiredoor.
Choose frpc-desktop if you…
- want a graphical way to configure and manage FRP client proxies.
- need to import or export an existing frpc.toml configuration.
- prefer desktop tools for switching among proxy entries and controlling individual proxies.
Choose Wiredoor if you…
- need to publish HTTP, TCP, or UDP services through WireGuard and NGINX.
- want to manage client nodes, domains, and services through a web dashboard or CLI.
- need Docker or Kubernetes gateway options for services on private networks.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.