Early internet networks were small enough that a single engineer could hold the entire system in their head. You didn’t need a system of record — you were the system of record. As networks expanded into the cloud, that model broke down. Infrastructure now sprawls across regions, providers, and services. The live state of the network became both impossible to understand and critical to get right fully.
Network infrastructure is now the backbone of the business, and configuration errors are no longer nuisances; they are business-critical events. AI agents are further pressuring network infrastructure to the extreme — so how are network engineers to keep it all running flawlessly?
Bespoke tracking doesn’t scale
Excel spreadsheets and cloud dashboards are no longer going to cut it. Running modern infrastructure requires a reliable representation of what the network should be — what systems and services exist, where they live, and how they connect. Without that, managing the network becomes high-risk.
In the past, your mapping might have fit into an Excel spreadsheet, and everything could be configured in the terminal. But today’s networks need more than a wizard at the terminal; they need architects who can look at the big picture and understand how the pieces of the network fit together.
“In the past, your mapping might have fit into an Excel spreadsheet… But today’s networks need more than a wizard at the terminal; they need architects who can look at the big picture.”
NetBox Labs provides network architects with the tooling needed to map out complex architectures, modeling everything from IP addresses to physical cabling. This mapping becomes the “system of record” used to make future decisions about the network and to form the foundation for systems of control.
But a system of record alone isn’t enough. Knowing what should exist doesn’t guarantee that’s what actually exists.
As modern networks and infrastructure are constantly being updated and reconfigured, that change is increasingly driven by intent, modeled in the system of record. NetBox Labs is central to change management, and teams drive configuration changes directly from the platform, ensuring the infrastructure is aligned with the intended design.
But not all changes in the network happen intentionally. How can network engineers surface every change and determine whether it is a meaningful update or drift — changes that deviate from the intended structure?
Are network changes updates or drift?
Network changes can be bucketed (loosely) into two categories: updates (a new service launch) or drift (an engineer pokes open a port for testing and forgets to close it, a team fires up a farm of test servers, and forgets to shut them down)
Updates are great — the network is growing, becoming stronger and more secure. These are planned and generally driven by changes that first occur directly in the system of record, which then drive downstream configuration in the network itself. This ensures the network’s truth evolves directly in tandem with live changes.
Drift is the opposite. The network is moving away from the system of record in a way that impacts security, reliability, performance, and ultimately the cost of running the network. Changes that introduce drift must be resolved to bring the network back into compliance.
So how do you tell? First, you must have a system of record (provided by NetBox) to know what should be there, and a way to quickly surface changes so your network engineers can identify them as growth or drift.
“What modern networks require is a system of control — a continuous loop that compares intended state to operational reality and acts on the difference.”
What modern networks require is a system of control — a continuous loop that compares intended state to operational reality and acts on the difference.
Reconciling changes
NetBox Discovery’s continuous mapping of the network provides the truth of what is live in the network today. NetBox Assurance compares the network’s live state to your system of record.
Assurance automatically discovers changes in the network that deviate from the system of record. These changes are surfaced to network engineers, who are given the opportunity to either update the source of record (this is a planned change to the network) or remediate any changes that have drifted from the system of record.
Companies like CoreWeave use NetBox Labs to accelerate data center deployments by helping them maintain their source of truth.
The future of network engineering
Network engineering is shifting. Engineers are no longer just configuring devices — they’re defining how the network should behave.
This becomes even more critical as we move away from scripts and syntax. In an AI-driven world, our intent becomes the prompts that define the outcomes, and the systems will execute against them — and orient by leveraging the system of record as the structured context map for the infrastructure.
But none of that works if there is not a source of truth that can be used to ground the intent.
That’s where the NetBox Labs Platform comes in, providing a system of record, along with discovery and validation, giving teams a complete picture of the network’s intended and operational state.
Network engineering isn’t going away — it’s evolving.
The future isn’t engineers writing better configurations. It’s engineers defining better intent — and relying on systems that continuously enforce it.
The post From system of record to system of control: How NetBox Labs is making network engineers “masters of intent.”