Each site runs a managed edge: a deployable facility, local data buffer, and a site fabric with three explicit service classes. Telemetry holds a protected class with guaranteed minimum bandwidth; bulk vision data is shaped into the engineered remainder; recovery traffic drains backlog through deliberately reserved spare capacity. Headroom is an engineering requirement, not padding.
02
Dedicated transport, engineered per site.
Fiber, dedicated wave, free-space optical, or millimeter-wave point-to-point, alone or in combination, chosen by survey and stated in the Site Deployment Plan. Where fiber cannot reach the site, it does not have to: at qualifying sites, point-to-point wireless links from fiber-fed towers up to ten kilometers away deliver 10, 25, 50, 75, or 100 Gbps, bringing AI offload service to sites that were previously impossible to serve. The service is defined by capacity, availability, and demarcations, not by transmission medium, and the SLA is identical regardless of the path.
A closed fabric of isolated per-site circuits: no extended layer-2 domain, no internet transit anywhere on the data path, encryption on every segment terminated only at OSI-controlled aggregation points, and a management plane that never shares addressing with customer traffic.
Deployed from day one as an A/B pair with dual cross-connects to every destination. Aggregate demand is the arithmetic sum of contracted site tiers, capacity is contracted non-blocking, utilization is reviewed quarterly, and upgrades follow a published tier ladder ahead of saturation. Convergence is not eliminated; it is owned.
Private cross-connects hand traffic directly to your existing cloud interconnect, leaving your cloud relationship and billing untouched, and to your GPU environment. Ancillary site traffic rides the same fabric to one centralized, hardened internet breakout, so no site buys local internet at all.