| Resource list | The server-maintained list of domains that can be accelerated, with connection policies labeled by category and region |
| Route policy | Rules the server issues to the client: which route each resource takes for your region and plan |
| Smart Direct | Reaching the target directly over your own network, without an edge node |
| Edge Accelerated | Reaching the target through an edge node |
| AI Compliant Exit | Reaching the target through an edge node and an IDC exit |
| Residential Line | Reaching the target through an edge node and a residential exit |
| Edge node | A relay node close to users that lowers link latency |
| IDC exit | An exit node with a data-center IP |
| Residential exit | An exit node with a home-broadband IP, which some AI platforms trust more |
| Chained connection | Going to the edge node first, which then connects to the exit node |
| PAC | Proxy Auto-Config: the system decides from a script which requests use the proxy |
| Explicit proxy | An app is configured with the proxy address directly |
| TUN | A virtual network adapter that takes over traffic at the system level |
| Shared proxy | Offering the local proxy to guests such as Docker, WSL and VMs, with separate credentials |
| Affinity base | The domain chosen in bot-check affinity; sites in the same group follow it through the same exit |
| Access lease | Authorization synced by nodes from the control plane: who may use which routes, and until when |
| No silent fallback | Pausing when the required exit is unavailable instead of switching to another exit |
| Device | The machine or browser behind one login |