Gateway origin containment
Less of your connection exposed.
Participating platforms see a CAIRL egress address instead of your own connection address. Other destinations continue to connect directly.
- Participating-platform routing
- Account-managed setup
- Direct connections elsewhere
Details & highlights
GateWay routes participating-platform destinations through a CAIRL egress node. Destinations outside the participating set continue to connect directly.
It changes the connection address a participating platform sees; it does not hide the identity you disclose by signing in. Account setup and availability remain governed by the GateWay guide.
Specifications
| Routing scope | Participating platforms in CAIRL’s service registry |
|---|---|
| Other destinations | Direct connection |
| Node order | US East, then US West for failover |
| Routing policy | Ordered; not per-caller or latency-based |
| Failure behavior | Participating routes fail closed |
| Credential secret | Shown once; rotation or revocation invalidates the old credential |
| Safari | Not yet qualified for the current TLS-to-proxy route |
Questions & answers
Answers from CAIRL’s documentation.
Does GateWay route everything?
No. Only participating-platform destinations use CAIRL’s egress nodes.
Does routing hide my signed-in identity?
No. Signing in still identifies you to the destination.
Customer reviews
No customer reviews have been published on this page yet.
What you need
Account-managed setup
Availability and proxy credentials are managed in your CAIRL account.
A compatible browser configuration
Firefox can be configured per profile. Chrome and Edge use computer proxy settings; consult the guide before configuring.
Workflows
Configure the participating-platform route
- Read the browser and computer scope.
- Copy the one-time credential secret when issued.
- Apply the documented proxy configuration.
Get started with Gateway origin containment
Setup, usage, and the details that matter.