frp

Commercial tunneling services like ngrok charge monthly subscriptions for static endpoints, meter outbound bandwidth, and inspect incoming requests on their cloud edge. frp moves that ingress path onto your own hardware, proxying TCP, UDP, and HTTP traffic through a lightweight daemon pair without recurring seat fees. You run the server binary on any commodity virtual machine and connect clients behind NATs with full control over data flow.

Why frp instead of ngrok

ngrok packages ingress tunneling as a hosted SaaS product, offering temporary URLs, request inspection, and webhook replays. However, teams operating staging environments or internal services encounter strict concurrency caps, domain renewal fees, and bandwidth metering. Cloudflare Tunnel eliminates domain surcharges through its global edge, yet it requires DNS delegation to Cloudflare and restricts non-HTTP protocols on standard tiers. frp takes an infrastructure-first path: you supply a low-cost virtual private server, run the frps daemon on a public IP, and connect frpc clients with zero per-port or per-gigabyte surcharges.

Hosting frp scales with the flat price of your VPS rather than per-seat subscriptions. A single five-dollar cloud instance handles dozens of concurrent tunnels across HTTP virtual hosts, raw TCP database streams, and UDP sockets. The operational trade-off is maintenance responsibility. While ngrok automates TLS certificate provisioning and DDoS mitigation, frp requires operators to manage SSL termination, firewall ports, and server uptime.

What it does well

• Multi-protocol forwarding: routes raw TCP, UDP, HTTP, HTTPS, and Unix domain sockets through one daemon, exposing databases, SSH sessions, and Docker sockets alongside web services.
• Transport acceleration: multiplexes client connections over a single TCP stream, with optional KCP and QUIC transports to reduce latency over lossy networks.
• Private and peer-to-peer modes: supports preshared keys (STCP) and direct peer-to-peer hole punching (XTCP) to bypass the relay server for bandwidth-heavy traffic.
• HTTP routing: handles virtual hosting by subdomain, rewrites headers, and passes client IP addresses through the PROXY protocol or X-Forwarded-For.
• Traffic control: enforces per-proxy bandwidth limits and maintains connection pools to eliminate handshake latency on frequent requests.