NetBrain Technologies announced major new platform features that advance Agentic NetOps from an emerging category to operational reality.
These new features further extend the platform with new agent tooling, cross-domain context, and open interfaces for the broader agentic enterprise.
"NetBrain is enabling our customers to achieve Agentic NetOps in production today," said Bernadette Nixon, CEO of NetBrain Technologies. "Our agents are not simply AI assistants, but act as operators that diagnose, decide, and act, governed by the verified network grounding our platform provides. We are delivering on both the innovative, purpose-built Agents and a platform to provide the trusted network context that allows our customers to pursue automation confidently."
NetBrain's network context model spanning Device, Topology, Path, and Intent across 150+ hardware vendors is the proprietary foundation that makes autonomous network operations possible. Available June 1, these new features extend the NetBrain platform:
- AI Path Doctor: Validates network paths, flags inaccuracies, and generates runbooks to remediate. Reliable paths are the precondition for every diagnosis and automation the agents run.
- Agent Skills: Institutional knowledge and best practices captured as Agent Skills tailoring NetBrain Agents to each customer's environment – without writing code or retraining models.
- Cross-Domain Context: New integrations consume application and infrastructure context from ITSM, security, and APM platforms, including Dynatrace, into NetBrain's diagnosis workflow, resolving the "is it the network or the application" question and eliminating 40% or more of tickets.
- Golden Assessment Library 26.06: Pre-built, industry-validated network assessments released on a regular basis to help stay abreast of industry shifts. This release includes updated coverage for capacity management, Cisco ACI intent integration with Deep Diagnosis, and Troubleshooting Skills for Deep Diagnosis.
- LLM Flexibility and MCP Support: Native support for Claude, Gemini, GPT, and any OpenAI-compatible endpoint including self-hosted models. Through MCP, NetBrain's network intelligence is now available to the broader agentic enterprise, extending NetBrain's grounded truth to whatever AI platforms our customers operate alongside it.
"The agentic conversation has been dominated by model choice and agent design and on ticket and log analysis use cases. The key to unlock adoption is grounded network truth that informs diagnosis and a remediation plan – for a real fix to real customer problems," said Song Pang, CTO of NetBrain Technologies. "Agent Skills tailor our agents to each customer's environment. AI Path Doctor guarantees path accuracy. MCP ties in the rest of the AI ecosystem. Together, they enable immediate business value and close the loop from diagnosis to remediation, at machine speed, with human confidence."
The Latest
Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...
Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...
When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...
If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...
Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...
AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...
Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...
Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...
Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...
In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ...