BunkerWeb vs frp

BunkerWeb is an open-source web application firewall and NGINX-based server that protects web services as a reverse proxy. Its core protections include HTTPS with automated Let's Encrypt, HTTP security headers, TLS hardening, ModSecurity with the OWASP Core Rule Set and automatic bans for suspicious behavior. It can block known malicious IPs through external blacklists and DNS-based blackhole lists. Bot challenges can use cookies, JavaScript, CAPTCHA, hCaptcha, reCAPTCHA or Turnstile. Supported deployment integrations include Docker, Docker autoconf, Swarm, Kubernetes and Linux. An optional web UI manages instances and configurations, though it is currently supported with Docker and Linux integrations. The open-source plan costs nothing under the AGPLv3 license. A PRO version has pricing based on the number of protected services; Standard has no technical support, while Enterprise includes dedicated technical support. Kubernetes Gateway API mode is in beta. For API access, the documentation recommends an IP whitelist and optionally an API token. Free community support is available through Discord, GitHub Discussions, Reddit, Server Fault and Super User; professional support and consulting are also offered.

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.