// the take
Fuso is a NAT traversal and port forwarding tool written in Rust, aimed at exposing local services to the internet through a relay server. It supports TCP/UDP forwarding, SOCKS5 proxying, KCP transport, cascading proxies, and RSA/AES encryption. The target audience is developers or homelab users who want a self-hosted ngrok alternative without the dependency on a third-party service.
1. KCP transport support is a real differentiator for high-latency or lossy networks where TCP performs poorly. 2. Cascading proxy mode lets you chain multiple hops through restricted network segments — useful for multi-layer corporate NATs where a single-hop solution won't reach. 3. Runtime abstraction over both tokio and smol means you can pick the async executor that fits your deployment constraints. 4. Encryption is layered in (RSA for key exchange, AES for data) with LZ4 compression, so you get a reasonable security + performance baseline out of the box.
1. The documentation is almost entirely in Chinese with no English equivalent beyond a brief header — anyone not reading Chinese will be guessing at flag semantics and error messages. 2. No web management panel or webhook support yet (explicitly listed as TODO), so you're flying blind operationally; the only connection event notification is shelling out to an external script. 3. WebSocket transport is unimplemented, which matters if you're trying to punch through corporate proxies or CDNs that block raw TCP but pass WebSocket. 4. The project bundles vendored C source (lz4.c, kcp third-party) directly in the tree — that's a maintenance and audit burden, and there's no sign of a security contact or CVE process if something upstream changes.
We read the README, the directory tree and a key source file in June 2026. Nobody pays to be listed. How we judge →