GateWay
Privacy Architecture
If they're breached, there's less of you in it. GateWay routes participating-platform destinations through a CAIRL egress node. Everything else connects directly, with no CAIRL involvement.
More documentation options
Features
A bounded route with explicit behavior and limits.
Participating platforms only
The route set comes from CAIRL's service registry. It is not a separate list that an account or environment can widen.
Direct by default
Destinations that are not participating platforms connect directly. They do not pass through a CAIRL node.
Fail closed for routed destinations
With the configuration applied, a participating platform does not silently connect directly when the credential is invalid or every CAIRL node is unavailable.
No sign-in disguise
GateWay changes the connection address a participating platform sees. It does not hide you from a platform you sign in to.
Ordered regional failover
US East is followed by US West in one ordered list. The second node is failover, not latency-based or caller-specific routing.
One-time credential secret
The proxy secret is shown once and stored as a hash. Rotation or revocation invalidates the prior credential.
How It Works
Add the configuration address
Firefox can be configured for one profile. Chrome and Edge use the computer's proxy settings, so other applications that honor those settings also route participating-platform destinations. Safari also uses the macOS proxy settings, but CAIRL has not yet qualified Safari’s support for the current TLS-to-proxy route; behavior can be uneven. Do not treat Safari as supported until that verification is complete.
Enter the credential once prompted
Use the issued handle and one-time secret when the proxy prompt appears. The secret cannot be retrieved later.
Route only the registered set
Participating-platform destinations use the ordered CAIRL egress nodes. Every other destination continues directly, with no CAIRL involvement.
Stop rather than bypass
If the credential stops working or both nodes are unreachable, participating platforms do not load until the route is restored or the configuration is removed.
Ready to get started?
Read the guide to understand the proxy scope, participating-platform boundary, credential behavior, and fail-closed result. Availability is managed inside your CAIRL account.