Service
New fabric services from one request, applied consistently across devices
We build the orchestration that turns a fabric’s intent into device configuration: the fabric described as specs, validated before deployment, rendered for each hardware type, brought up by zero-touch provisioning and tested on a digital twin first. For a global e-commerce marketplace, the time to plan and deploy a large fabric fell from 3–4 weeks to 1–2 days.
Measured impact
What changes for your organization
- Today
Dozens of changes per service
Every new service or rack in the fabric means manual changes on many devices, one command at a time.
With intent-based orchestrationOne request per service
Engineers change the intent, and the orchestration derives and applies the configuration on every device it touches.
- Today
Weeks per topology
Fragmented tools and manual handoffs make every new fabric slow to define and deliver.
With intent-based orchestrationFabrics in days
Topologies are generated from declarative patterns, and scaling one means changing a handful of parameters.
- Today
Hardware tied to rework
Swapping a switch for another vendor’s model means rewriting its configuration by hand.
With intent-based orchestrationHardware you choose freely
One configuration model with a renderer per platform, so a new hardware type means adding a renderer.
- Today
Configuration that drifts
Build-time configuration goes stale within months, and hardware replacements fall back on backups.
With intent-based orchestrationOne source of the fabric’s state
The model is the record of the fabric, and every device gets its configuration from it at bring-up.
- Today
Designs proven on the floor
A fabric design is tested only once the hardware is racked and cabled.
With intent-based orchestrationDesigns proven before purchase
Specs are validated and the whole topology runs as a digital twin before any device arrives.
What we deliver
How it runs
The scope follows your fabric, hardware and tools; the order of the work stays the same.
Discovery
Your fabrics, hardware and the way they are built today, the target model and architecture, and a plan.
Model
The fabric’s specs and the configuration model, confirmed on a small topology before anything scales.
Renderers
Configuration rendered for each hardware platform you run, validated against its constraints.
Digital twin
The topology emulated and tested, designs and changes included, before deployment.
Zero-touch rollout
Devices brought up from the model, starting with one fabric, then the next.
Handover
Your engineers extend the model and add renderers and logic themselves, with our support for as long as you want it.
Proof
- A data center fabric planned and deployed in at most 2 daysFor a global e-commerce marketplace running SONiC: layered specs, one model with per-hardware renderers, ZTP bring-up and a digital twin, cutting a large topology from 3–4 weeks to 1–2 days.
- Controlling a heterogeneous data plane with the ONOS SDN controllerFor a data center provider, one control plane over legacy fabric devices and new hardware, with the missing adapters built and deployed in production.
- Recreating customer SD-WAN networks as virtual twins in ~90 minutes instead of ~15 daysFor a global networking leader, full networks rebuilt from their own backups as twins, ready for the existing automated tests.
