Admin · Registry
The platform's own iron.
Where no federation provider operates a span, NaaS Labs runs it directly. Same registry engine every operator gets, scoped to the spans we own. No shadow tooling, no second source of truth.
Operated spans 0 of 0 on the fabric
Sites 0 0 racks
Devices 0 0 need eyes
Circuits 0 0 customer services
Strand miles 0 strand-level OSP records
Prefixes 0 IPAM pools tracked
Registry surfaces
One registry engine serves every operator. This lens sees the NaaS Labs-operated scope.
Sites and racks 0 · 0 0 sites, 0 racks. Elevations, units, and power per rack. Open in the registry →Devices 0 0 devices in service. 0 failed or in maintenance. Open in the registry →Circuits 0 0 backbone circuits, CLR to optical port, plus 0 customer services. Open in the registry →IP space 0 0 prefixes under management, with VLANs and federation ASNs. Open in the registry →Fiber plant 0 0 strand miles. Cables, splice cases, strand-level light paths. Open in the registry →Serviceability 0 0 tracked buildings. 0 on-net, 0 near-net, 0 off-net. Open in the registry →Calibration and ITAM 0 · 0 Test-equipment calibration schedule and the fixed-asset feed export. Two thin surfaces on the device model. Open the ITAM tail →Asset lifecycle 0 0 devices rolled through procurement, deploy, maintain, and retire. The fleet count and the warranty refresh wave. Open the lifecycle rollup →
NaaS Labs-operated spans
0 of 0 backbone spans| Route | Capacity | Used | Utilization | Status |
|---|
Operating directly is a choice, not a privilege. These spans sit under the same audit, the same settlement rules, and the same exit rights as every federation provider's.