Twin construction
Your running configurations and topology imported into Batfish and Containerlab or the vendor's virtual images; refreshed automatically from production.
Signature program
No change without a dry run.
Every config, every route, every cutover is proven on a digital twin of your fabric before it touches production. Candidate configuration in, predicted state and routes out, compared with reality — so cutovers are boring.
What's included
01
02
Pre-change analysis
Candidate configurations applied to the twin: reachability, route tables, ACL behaviour and policy differences predicted before the window.
03
Failure simulation
Link, node and route failures exercised so resilience is measured, not hoped for.
04
Cutover rehearsal
The full method of procedure run on the twin, step by step, with rollback tested.
05
Pipeline integration
Validation as a gate in your Git pipeline — changes cannot merge without a passing twin run.
06
Drift detection
Production compared with the twin daily; unapproved changes surfaced.
How an engagement runs
01
Import
Configurations and topology collected; twin built and baselined against production.
02
Calibrate
Predicted versus observed state compared; model gaps closed.
03
Operate
Every change through the twin; results attached to the change record.
Questions we get asked
Which platforms can be twinned?
Junos, IOS-XE, NX-OS, EOS, PAN-OS and FortiOS configurations through Batfish; full behavioural twins with Containerlab for Junos, EOS, NX-OS and SONiC images.
Is this included in your migration programs?
Always. It is also available on its own for networks we did not build.
Request a quote
Tell us about the project; a senior engineer responds the same business day.