An encrypted REALITY data plane
Every hop speaks VLESS-Vision over REALITY through sing-box, so a chain looks like normal TLS on the wire.
Multi-hop SOCKS5 over REALITY
linksward composes a private SOCKS5 chain for every link: an entry, the relays you choose, and an exit you control.
Entry
shanghai
Relay
× n
Exit
egress
Internet
open
Your client opens a SOCKS5 connection to the entry box using that link's own credentials.
Each hop crosses the next box over VLESS-Vision and REALITY, so the path blends into ordinary TLS.
The last box egresses directly, or hands the connection to an external SOCKS5 upstream you nominate.
Every hop speaks VLESS-Vision over REALITY through sing-box, so a chain looks like normal TLS on the wire.
Passwords, REALITY keys, and per-segment UUIDs are AES-256-GCM encrypted, opened only server-side for the box that needs them.
Each connection carries its own SOCKS5 user, routed by username, so one box serves many isolated chains.
Run one command on a machine. It mints its own keypair, registers as pending, and serves traffic once you approve it.
docker run … linkward-box → POST /api/agent/enrollCompose a chain and watch a live estimate, then fire a real end-to-end probe from the entry box before you rely on it.
Egress straight from one of your own boxes, or pass the final hop to an external SOCKS5 upstream.
Sign in with Google to request access. An administrator approves new accounts before they can compose connections.