// the take
V2Ray (Project V) is a modular proxy framework in Go for building custom proxy and traffic-routing setups — VMess, Shadowsocks, SOCKS5, HTTP inbound/outbound, with its own router and DNS layer. It's for developers who want to assemble their own censorship-circumvention or privacy proxy stack, not end users who want a one-click client.
Clean split between features (interfaces), app (dispatcher, dns, router, policy, stats, commander) and proxyman (inbound/outbound workers), so proxies, routing and stats are pluggable without touching core dispatch logic. Protocol sniffing (common/protocol/http, common/protocol/tls) lets the router make domain-based routing decisions off the first bytes of a connection, without a TLS-terminating man-in-the-middle. A gRPC command API (app/commander, app/stats/command, app/router/command) exposes live connection stats and routing config at runtime, so you can build real monitoring on top instead of parsing logs. common/mux multiplexes many logical streams over one underlying connection, cutting per-connection handshake overhead for workloads with lots of short-lived requests.
The README itself says the project moved to v2fly/v2ray-core — this repo is the original that got forked, so fixes and new protocol work land there, not here, and anyone landing on this one via search or an old link is building against a dead origin. Access control is pre-shared IDs (VMess) or passwords (Shadowsocks) baked into static JSON configs, with no key rotation or multi-tenant ACL model — all of that is left to the operator. Routing/DNS behavior (app/router, app/dns) is powerful but entirely config-driven with no tool to test which rule a given connection would match, so debugging routing decisions means reading source. Like any DPI-evasion protocol, VMess/Shadowsocks traffic fingerprints get discovered and blocked over time — which is exactly why the ecosystem kept forking (v2fly, then Xray) — so adopting this means ongoing protocol churn, not a one-time setup.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →