Network operations that repeat
We build the automation chain for your network: source of truth, configuration as code, validation and controlled execution — a tool for dependable changes, not an end in itself.
- NetBox as source of truth
- Changes from templates
- Pre- and post-checks with pyATS
- Git history for every change
The chain from data record to post-check
Source of truth
NetBox as the leading data model: sites, devices, VLANs and prefixes — reconciled against reality.
Configuration as code
Target configuration from Jinja2 templates and structured data, versioned in Git instead of loose files.
Pipelines & rollout
Render, diff, dry run, approval, deploy: every standard change travels the same proven track.
Validation with pyATS
Pre- and post-checks for routing, adjacencies, redundancy and reachability — before and after every change.
Drift detection
Target-versus-actual comparison in operations: deviations surface before they become incidents.
Operational handover
Runbooks, roles and training: your team runs the chain — or we do, as a managed service.
How we proceed
Automation follows risk and economic benefit — in exactly that order.
Assessment
How reliable are inventory, standards and the change process? Where does automation pay off first?
Data model & source of truth
NetBox is built and populated; the truth moves out of spreadsheets and heads into a verified model.
First chain in production
One recurring change is automated end to end — with tests, approval and rollback.
Scale-out & governance
Further use cases, mandatory peer review, separated environments and complete logging.
Tooling & platforms
- NetBox
- Ansible
- Python
- Jinja2
- Git
- Cisco pyATS / Genie
- Meraki Dashboard API
Next step
Your first automated change
We start with the assessment, then automate the track that pays off first — traceable and under defined controls.
Request an assessment