frp vs Reproxy
frp
gofrp.org
Reproxy
reproxy.ioSide by side
| Figure | frp | Reproxy |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| Android | Yes | — |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Reverse Proxy Software | 8.2 (#12) | 7.1 (#26) |
| Monitoring | frps supports in-memory monitoring and Prometheus monitoring; Prometheus requires the Dashboard to be enabled. | Its optional management server exposes route information and Prometheus metrics. |
| Purpose | frp is a high-performance reverse proxy for exposing intranet services to the public network through nodes with public IP addresses. | Reproxy is an HTTP(S) edge server and reverse proxy that routes requests to destination servers using configured providers. |
| Security | Client and server authentication supports token and OIDC methods, with token authentication as the default. | The documentation recommends running the container as a less-privileged user when Docker discovery is not needed and warns that forwarded IP headers can be spoofed unless controlled by a trusted proxy. |
| Traffic management | Proxy groups support load balancing, and TCP or HTTP health checks can remove failed services from frps. | It supports health checks, failover, and load balancing. |
Plans
In their own words
frp
frp is a free, self-hosted reverse proxy for making intranet services reachable from the public network through nodes with public IP addresses. It supports TCP, UDP, HTTP, and HTTPS proxying, while client-server communication also supports QUIC, KCP, WebSocket, and other protocols. Its XTCP mode uses P2P hole punching so successful connections send traffic directly rather than through frps, but success depends on the network’s NAT type and cannot be assured. Client and server authentication support tokens and OIDC, with token authentication as the default; encryption is among the project’s listed capabilities. Proxy groups can balance load, and TCP or HTTP health checks can remove failed services from frps. Monitoring can run in memory or through Prometheus, which requires the Dashboard to be enabled. frps has a browser Dashboard for status and proxy statistics, while frpc includes an Admin UI for proxy status and configuration. Configuration supports TOML, YAML, and JSON; INI is still supported but no longer recommended. Written in Go, frp provides platform-specific binaries for cross-platform deployment without additional dependencies. The project is under development and says version 2 will not be compatible with version 1.