Network digital twin
The migration that already failed — in the lab, where it was cheap
A replica of your network in EVE-NG running real network operating systems: migration, failure and rollback proven before production is touched.
The problem
The change runs in production for the first time
The migration plan works on paper. In the real network the BGP policy turns out to touch another prefix, the MTU does not match, and the rollback takes 40 minutes — inside a 30-minute window.
Architecture
Architecture
- 01DiscoverConfig extraction
- 02ReproduceLab replica
- EVE-NG
- Real NOS images
- 03Simulate
- BGP
- MPLS
- L2 failover
- 04FailDeliberate breakage
- 05RecoverRollback tested
- 06DeployWith an approved plan
Operator consoles
Operator consoles
These exact systems run on the group's own infrastructure — the screenshots are processed before publication.
The digital twin — the lab that comes before production
A topology built from real network operating systems: border routers, IXP and CDN peerings, the aggregation layer, VLANs and the management network — production, replicated in the lab. Migration, failure and rollback run here first; only then does anyone touch the live network.
Capabilities
Capabilities
Every item is marked: verified production experience, or engineering capability.
Real network OS emulation
Capability- EVE-NG
- IOS XR
- Junos
- RouterOS
BGP / MPLS / L2 replication
Capability- BGP
- MPLS
- STP
- LACP
Migration testing
ProvenFailure scenarios
ProvenSimulated link, node and upstream failure.
Rollback validation
ProvenTraining labs
ProvenThe same topologies are reused in Academy courses.
Engagement model
Engagement model
Project
A one-off scope: audit, migration or implementation with a fixed outcome.
Retainer
Monthly engineering hours — specialist access on demand.