Open Source Rust Reverse Proxy Servers

A secure, stable and high-performance reverse proxy for NAT traversal, written in Rust. rathole, like frp and ngrok, can help to expose the service on the device behind the NAT to the Internet, via a server with a public IP. High Performance Much higher throughput can be achieved than frp, and more stable when handling a large volume of connections. Low Resource Consumption Consumes much fewer memory than similar tools. See Benchmark. The binary can be as small as ~500KiB to fit the constraints of devices, like embedded devices as routers. Security Tokens of services are mandatory and service-wise. The server and clients are responsible for their own configs. With the optional Noise Protocol, encryption can be configured at ease. No need to create a self-signed certificate! TLS is also supported.

Frpc-Desktop is a free, open-source desktop client that simplifies configuration and management of FRP reverse proxy connections. It allows users to expose services running on private networks through publicly accessible servers without configuring traditional router port forwarding. The application provides a graphical interface for managing FRP clients, servers, and proxy configurations. It supports multiple FRP versions and enables users to download and manage the required client binaries. Configuration options accommodate remote access, web services, and development environments. Frpc-Desktop also includes proxy controls, configuration import and export, and automatic startup options. Built with Tauri, it runs on Windows, macOS, and Linux and reduces the complexity of command-line network tunneling.

Open source HTTP reverse proxy built in Rust for immutable infrastructures. Most existing tools have a static vision of production: a service is installed once on a long-lived server, updated from time to time, with configuration rarely changing. There's now a shift in infrastructure to short-lived virtual machines and hundreds of new deployments per day, and the usual tools reach their limits. How do we reconcile a dynamic environment with availability guarantees? How can we get "zero downtime" deployments for critical services? SŌZU is a HTTP reverse proxy built in Rust, that can handle fine-grained configuration changes at runtime without reloads, and is designed to never ever stop. SŌZU receives and handles configuration changes at runtime and updates its internal configuration without restarts. You can update the configuration multiple times per second, and it will take care of lingering connections.