Source of truth
NetBox or Nautobot holds devices, interfaces, IPs and intent; configuration is generated from it, never typed.
Signature program
The fabric is the repository. You own it.
Every design we deliver lives in version control: topology, variables, templates, tests and pipeline. Changes are pull requests, reviewed and twin-validated before they deploy. At handover the repository is yours, with the history.
What's included
01
02
Templates and roles
Vendor-specific Jinja templates or Arista AVD, Apstra blueprints or ACI schemas as code.
03
Pipeline
GitLab CI or GitHub Actions: lint, render, twin validation, approval, deploy, post-check.
04
Testing
Batfish assertions and live pre/post checks on reachability, BGP state and interface health.
05
Drift and compliance
Nightly comparison of running configuration to the repository; deviations opened as issues.
06
Enablement
Your engineers trained to make changes the same way; we review the first ten pull requests with them.
How an engagement runs
01
Baseline
Existing configurations imported, normalised and reproduced from templates.
02
Pipeline
CI built, twin integrated, first change through the full path.
03
Expand
Remaining estate onboarded; team trained.
04
Hand over
Repository, runbooks and pipeline transferred. Optional review retainer.
Questions we get asked
Do we need to be programmers?
No. Day-to-day changes are edits to YAML and a pull request. The templates and pipeline are ours to build and yours to keep.
What if we already use Apstra or ACI?
Then the controller is the deployment target and the repository drives it through its API. The review and twin gates stay in front.
Request a quote
Tell us about the project; a senior engineer responds the same business day.