frp vs ngrok

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.

ngrok is a cloud networking platform that secures, transforms, and routes traffic to services wherever they run. Its agent sends traffic through secure tunnels without requiring firewall changes. Traffic Policy uses CEL-based rules to route requests, authenticate them, apply rate limits or web application firewall controls, and reject them. Supported traffic includes HTTP, TLS, and TCP, including WebSockets, gRPC, SSH, Postgres, MQTT, and Minecraft. The Integrations Hub offers integrations and guides for areas such as SSO, databases, Kubernetes, OAuth, webhooks, and web servers. ngrok also verifies webhook signatures for more than 70 providers, including Stripe, GitHub, Twilio, Slack, and Shopify. The free plan includes $5 one-time usage, up to 3 online endpoints, up to 1GB data transfer, up to 20k HTTP/S requests, and one team member. Paid access starts at $10/mo. On Hobbyist, endpoints stop working when usage credit runs out, until the billing cycle ends and credit resets. ngrok lists region pinning across the United States, Europe, Asia Pacific, Australia, India, Japan, and South America.