Articles
Network technology, explained
We write about what we use every day: multi-vendor source of truth, configuration and state compliance, digital twin, ChatOps, telemetry, test network, and security. Every article stands on its own, even if you never hire us.
Local AI with your company's context
Argos answers with an open model on your own server, using vendor guides, your network design, your standard and your procedures: it cites source and page, never indexes secrets, and every change goes through the digital twin.
Security in Oktavia and Argos
Vulnerabilities by version with NVD, CISA KEV and EPSS, security posture with evidence, per-role hardening as intent, and a diagnosis that sends no configurations or secrets to AI.
Test before you touch production: the Oktavia test network
Site creation and removal, device onboarding, replacement and retirement rehearsed in Cisco Modeling Labs, connectivity tests from intent, and the same loop on Cisco SD-WAN.
Networks degrade for weeks before anyone calls
Why an audit is a snapshot and not enough, what measuring over time adds, how to write an event rule that does not end up silenced, and which events are worth watching.
ChatOps for networks: useful if it declares what it costs
What ChatOps means for networking and what it does not, why much of what operators ask needs no language model at all, and what guardrails a chat that can change configuration requires.
Detecting is easy. Closing the loop is the problem
Why automatic remediation is dangerous, what a digital twin means in concrete terms, why every vendor has its own safe primitive, and why without verification the loop never closes.
Your configuration passes and your network is still broken
The difference between configuration compliance and state compliance, why correlating them changes what you can claim about your network, and why almost no tool does it.
The inventory nobody has
Why a manual inventory is out of date the day it is written, the difference between an inventory and a source of truth, why multi-vendor is where most tools break, and what becomes possible once the network describes itself.