Composable tunnel chains
Build network paths from small nodes: listeners, protocol transforms, encryption, multiplexing, packet bridges, and connectors.
Why it feels different
A network toolkit built around composition.
Instead of one fixed proxy shape, WaterWall lets each route describe the exact chain it needs.
High-throughput runtime
WaterWall is designed around asynchronous I/O, worker threads, buffer pools, and low-copy packet movement.
Stream and packet workflows
Use ordinary TCP/UDP flows, raw packet pipelines, TUN devices, WireGuard edges, or bridge between models when a route needs it.
The mental model
Describe the path, then let each node do one job.
A route can stay linear, or hand traffic to Router so rules choose different branches by domain, protocol, identity, port, or source.
Client tunnel chain
TcpListener→MuxClient→VlessClient→TlsClient→TcpConnector
Documentation
Start from the shape you need to build.
Project introductionUnderstand the node model, tunnel composition, and the shape of a WaterWall configuration.Getting startedWalk through the first working configuration and learn how the core JSON files fit together.Node referenceBrowse the available listeners, connectors, protocol nodes, packet nodes, and test utilities.