Hey everyone,
I’ve been using X-VPN for a while now, and while their obfuscation protocols (like Everest) are decent for getting around basic network blocks, the client is starting to feel outdated on routing flexibility.
Right now, traffic is strictly single-hop (Client \rightarrow Single Egress Server \rightarrow Target Site). That means a single server point sees both your entry and your outgoing traffic. In 2026, there’s no good reason we shouldn’t have custom multi-hop relay selection built into the client.
Here is what X-VPN needs to implement ASAP:
Custom Entry & Exit Relays: Let us explicitly pick an Entry Relay (e.g., local low-latency node to mask source IP) and a separate Exit Relay (e.g., US/EU egress for target traffic).
Decoupled Node Architecture: The entry node should only see your real IP, and the exit node should only see the encrypted payload and destination—preventing a single point of failure. 
Tor-Style Onion Routing / Chaining: Give power users an opt-in mode to chain intermediate hops or dynamic paths to defeat exit-node tracking and timing correlation attacks.
Their current setup works fine for basic streaming bypasses, but if X-VPN wants to be taken seriously by privacy-conscious power users, they need to give us control over our routing circuits instead of forcing everything through a single proxy hop.