frp
gofrp.org
- Free plan
- Windows
- macOS
- Linux
- Android
- Self-hosted
What frp is
frp is a free, self-hosted reverse proxy that makes 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 can also use QUIC, KCP, WebSocket, and other protocols. XTCP uses P2P hole punching so successful connections send traffic directly rather than through frps, but success depends on the network's NAT type and is not assured. Authentication supports tokens and OIDC, with token authentication as the default; encryption is also listed among the project's capabilities. Proxy groups can balance load, and TCP or HTTP health checks can remove failed services from frps. Monitoring is available in memory or through Prometheus, which requires the Dashboard. frps has a browser Dashboard for status and proxy statistics, while frpc has an Admin UI for proxy status and configuration. Configuration supports TOML, YAML, and JSON; INI remains supported but is no longer recommended. The project is written in Go, supplies platform-specific binaries, and documents use cases such as exposing SSH and web services. It supports Linux, macOS, Windows, Android, and self-hosted deployment.
Who it suits
frp suits technical users who need to expose intranet services through a self-hosted proxy. It may suit operators managing proxy groups, monitoring, and multiple configuration formats.
Good to know, and what to watch
- Supports TCP, UDP, HTTP, and HTTPS.
- Offers token and OIDC authentication.
- Proxy groups support load balancing.
- Includes in-memory and Prometheus monitoring.
- Free, self-hosted software with platform-specific binaries.
- XTCP reliability depends on network NAT type.
- Prometheus monitoring requires the Dashboard.
- Dashboard is not optimized for large data volumes.
- Version 2 will not be compatible with version 1.
Plans
Every plan and pricefrp
Free plan
Getting started
- Visit gofrp.org and obtain the platform-specific binaries
- Deploy the self-hosted frps server and frpc client
- Create configuration files in TOML, YAML, or JSON
- Choose token or OIDC authentication
- Define proxies, groups, and health checks
- Enable the Dashboard if Prometheus monitoring is required
Limits to check
XTCP availability and stability cannot be guaranteed because hole-punching depends on NAT type. The Dashboard is not optimized for large amounts of proxy data, and Prometheus monitoring requires the Dashboard to be enabled.
The verdict
frp offers protocol support, monitoring, authentication, and traffic management for self-hosted reverse proxy deployments. Its XTCP mode and Dashboard have stated limitations, and the project notes a future version incompatibility.
Questions people ask
Is frp free?
Yes. The listed frp plan costs nothing and describes open-source reverse proxy software with self-hosted client and server binaries.
Which platforms can run frp?
It supports Android, Linux, macOS, self-hosted deployment, and Windows.
What protocols does frp support?
Proxying supports TCP, UDP, HTTP, and HTTPS. Client-server communication also supports QUIC, KCP, WebSocket, and other protocols.
Is frp open source?
Yes. The GitHub repository identifies the project license as Apache-2.0.
How does authentication work?
Client and server authentication support token and OIDC methods, with token authentication as the default.
Does frp provide monitoring?
frps supports in-memory monitoring and Prometheus monitoring. Prometheus requires the Dashboard to be enabled.
What the maker publishes
- Configuration
- Configuration files support TOML, YAML, and JSON; the older INI format remains supported but is no longer recommended. source
- Dashboard limitation
- The Dashboard has not been optimized for large amounts of proxy data, and the documentation advises against enabling it if access is slow. source
- Deployment
- frp is written in Go and supports cross-platform deployment using platform-specific binaries without additional dependencies. source
- Development status
- The project says it is under development and that version 2 will not be compatible with version 1. source
- Encryption
- The project lists encryption among its capabilities and documents communication security features. source
- License
- The GitHub repository identifies the project license as Apache-2.0. source
- Monitoring
- frps supports in-memory monitoring and Prometheus monitoring; Prometheus requires the Dashboard to be enabled. source
- P2P
- XTCP uses P2P hole punching so successful connections send traffic directly instead of relaying it through frps. source
- P2P limitation
- XTCP availability and stability cannot be guaranteed because hole-punching success depends on the network’s NAT type. source
- Protocols
- It supports TCP, UDP, HTTP, and HTTPS, and client-server communication also supports QUIC, KCP, WebSocket, and other protocols. source
- Purpose
- frp is a high-performance reverse proxy for exposing intranet services to the public network through nodes with public IP addresses. source
- Security
- Client and server authentication supports token and OIDC methods, with token authentication as the default. source
- Traffic management
- Proxy groups support load balancing, and TCP or HTTP health checks can remove failed services from frps. source
- Use cases
- Documented examples include exposing SSH and web services, forwarding DNS and Unix domain sockets, serving files, and creating P2P or virtual network connections. source
- Web interfaces
- frps includes a browser Dashboard for status and proxy statistics, while frpc has an Admin UI for proxy status and configuration. source
Checked against the maker's pages on 7 Oct 2026.