Architecture

One system, from the machine in the field to the training computers.

OSI Managed Data-Transport Architecture ONE ENGINEERED SYSTEM, FROM THE MACHINE TO THE MODELmany-to-few data movement under a single SLA with one accountable operatorSITESedge facility + buffer + 3 service classesDense sitemachines · buffer · QoSStandard sitemachines · buffer · QoSStandard sitemachines · buffer · QoSRemote sitemachines · buffer · QoSDEDICATED TRANSPORTengineered per site100G+ wave10G fiber10G wavetower-fed PTP · 10–100 GbpsOSI PRIVATENETWORKisolated per-site circuitsno internet transitno extended L2 domainencrypted every segmentAGGREGATION CORE (A/B, day one)CORE Arouter A · power feed ACORE Brouter B · power feed BCloud storageprivate interconnectGPU trainingprivate cross-connectCentralized breakoutone hardened egressOSI NOCmanagement planeGEOGRAPHIC DR (roadmap)fabric re-home, alternate metroDELIVERY TELEMETRY · measured end to end, so shortfalls are localized, not argued aboutbytes generatedbytes queuedoldest queue agebytes transmittedreceived at aggregationaccepted at destination

The five parts of the system

01

The site edge.

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.

03

The Private Network.

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.

04

The Aggregation Core.

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.

05

Destinations.

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.

How we measure delivery

We measure every step, so we can show exactly where a delay happened.

Bytes generated, bytes queued, oldest queue age, bytes transmitted, bytes received at aggregation, bytes accepted at the destination: six measurements that assign any delivery shortfall to source, storage, transport, core, or destination ingest.

  1. 01

    Bytes generated

  2. 02

    Bytes queued

  3. 03

    Oldest queue age

  4. 04

    Bytes transmitted

  5. 05

    Bytes received at aggregation

  6. 06

    Bytes accepted at the destination