Quick Network Configuration

Sets an upper bound on throughput for this subscription.

• The configured value is a limit, not a guaranteed speed.
• Measured speed may be lower because of access network quality, routing, and endpoint performance.
• When throughput reaches the configured value, additional traffic is shaped to remain at or below the cap.

Controls how many device identities can be active at the same time.

• A device identity is evaluated by the public IPv4 address observed by service nodes.
• Multiple endpoints behind the same NAT address are typically counted as one identity.
• If the public address changes, it may be treated as a different identity.
• Current enforcement applies to IPv4 traffic.
• When the limit is reached, additional identities are rejected until capacity is available.

Seats are independent sub-accounts created by the subscription owner.

• Each seat uses separate credentials and usage records.
• Seat status can be managed individually.
• If the limit is 0, seat creation is unavailable.

Limits how many new tunneled connection handshakes per second are accepted for this subscription. It is a ceiling on connection setup, not a target; sustained rates from everyday clients are usually much lower.

• Each new handshake attempt contributes to this rate.
• Short bursts may be allowed by the limiter implementation.
• If sustained handshake volume exceeds the configured rate, excess attempts are delayed or rejected.
• Established sessions are not retroactively terminated by this control.

BYOE (Bring Your Own Egress) means you supply an HTTP or SOCKS5 proxy that acts as the exit from the service path. Your traffic is carried over the service network to an access node; the node forwards it to your proxy, and the path to the public Internet continues from your proxy onward.

• One slot is one saved proxy target (host, port, credentials if any) and related binding settings.
• The service provides transport to the node and relay to your proxy; operation and policy of the proxy endpoint remain your responsibility.
• If the limit is 0, BYOE management is unavailable.
• If the subscription limit is reduced, entries above the new limit are removed according to system retention rules.
• If a bound node becomes unavailable, the entry may be switched to unbound while proxy settings are preserved.