Software · Cloud and infrastructure
Networking software
Software that configures, documents and checks your network, so changes are repeatable and mistakes are caught.
Networks are still often changed by hand, one device at a time, with the real configuration living only on the switches. We build automation that generates and pushes configuration from a single source of truth, backs up every device, validates changes before and after they land, and keeps an accurate inventory of addresses, links and sites.
What we build
- A source of truth for devices, sites, IP addresses and VLANs in NetBox
- Configuration templates and automated pushes with Ansible or Nornir
- Nightly configuration backups with diffs that show who changed what
- Pre- and post-change checks for routing, interfaces and reachability
- WireGuard and IPsec VPNs linking offices, cloud networks and remote staff
- Custom network services and proxies in Go or Rust for specific protocols
DemoInteractive · sample data
Try it live.
A working sample with made-up data. It runs in your browser; nothing is sent anywhere.
- Branch site BLR-04 (6 devices)
- Config backup
- Config drift
- BGP sessions
- IPsec tunnel to HQ
- DNS resolution
What it does well
Single source of truth
Device configs are generated from NetBox data, so documentation and reality agree.
Change validation
Routing tables, neighbours and reachability are compared before and after each change.
Drift detection
Manual edits made on a device are flagged, then either approved or reverted.
Multi-vendor
Templates cover Cisco, Juniper, Arista, MikroTik and Linux-based routers alike.
Identity-aware access
Remote access goes through VPNs tied to user identity, not flat network trust.
Generated topology
Diagrams and site reports are produced from live data, not drawn by hand.
Questions
Is network automation worth it for a small network?
Even a few sites benefit from automatic configuration backups, an accurate IP inventory and templates for common changes. Full automated pushes make the most sense once you have many similar devices or sites, or frequent changes that keep causing mistakes.
Our devices come from different vendors. Is that a problem?
No. We model the intent once in a source of truth and render vendor-specific configuration from templates. Where a device supports modern interfaces such as NETCONF or gNMI we use them; otherwise Nornir and Netmiko work over SSH.
How do you avoid breaking the network with automation?
Changes are reviewed as code, tested against a model of the network with Batfish, pushed to one device or site first, and checked automatically afterwards. If the post-change checks fail, the previous configuration is restored.