Four route types and smart routing
What Smart Direct, Edge Accelerated, AI Compliant Exit and Residential Line are, and who decides which one is used.
The four routes
| Route | Path | Typical resources |
|---|---|---|
| Smart Direct | Your network → target | Targets that need no optimization (decided by the server) |
| Edge Accelerated | You → edge node → target | GitHub, npm, PyPI, Docker Hub, Cursor |
| AI Compliant Exit | You → edge node → IDC exit → target | ChatGPT, Gemini, Grok, Hugging Face |
| Residential Line | You → edge node → residential exit → target | Claude Code |
Who decides
- The server keeps a connection policy for each resource in different network environments and issues route policies according to your plan.
- The client fetches the policy when it connects and applies it to each request in real time.
- You can adjust the node for each segment in Node settings, but you cannot move a resource onto a route it does not support.
Different network environments
The best route for the same resource can differ between environments: targets that are directly reachable are judged Smart Direct, and the rest take their assigned routes. The client fetches the policy for your current environment automatically when it connects; no manual setup is needed.
Why not send everything through one exit
The fastest node may not reach AI services, exits that reach AI are often slow, and residential IPs are rarely a good main exit for anything except Claude Code. Per-resource routing sends every request along the most suitable path.