Provider · Design
Design the network.
Everything built here moves through one pipeline: draft, validate, review the change-set, commit as planned records, provision. The registry documents what you designed; the network is built from the record — never the other way around.
- New serviceDescribe intent — endpoints, rate, protection — or compose on the canvas. Candidates are ranked against live capacity and shared-risk; allocation proposes addresses before anything is written.Forms + canvas · opens the composer →
- New devicePlace a device from a template into a site and rack. Ports arrive from the template; the record lands as planned until provisioning flips it active.Arrives with the device-type library
- Extend fabricAdd links and inter-network interconnects on the topology canvas. Auto-addressing draws from your infrastructure pools; routing artifacts are rendered and documented in the registry.Arrives with the workbench slices
How a design becomes the network
- Intentwhat you want — yours to state, always editable
- Candidatesranked paths and options; pin any value to take it over
- Allocationaddresses and identifiers reserved with a TTL — auto by policy, or yours manually; both validated identically
- Change-set reviewevery write shown before it happens; blocking checks cannot be waived
- Commitplanned records land in the registry; reservations hold
- Provisionsteps run auto, assisted, or manual — your choice per step; records flip active on verified completion