Skip to main content
AI Automation & Agents

Nanites

AI agents that investigate network incidents like a senior NOC engineer: parallel checks on real devices, correlated evidence with a confidence score, and a scoped fix for an engineer to approve.

  • Sector Network operations, IT infrastructure
  • Client US agentic network-automation startup
Root-cause accuracy on the incident evaluation set
94%
A sub-agent per device, running read-only CLI checks
Parallel
Each finding carries evidence and a confidence score
Explainable
A scoped fix is proposed; an engineer applies it
Safe fixes
Nanites investigating a Grafana alert: reasoning steps, parallel device checks, evidence with a confidence score and a live log stream
A live investigation: two device sub-agents, vendor MTU normalisation and an evidence list with its confidence score.
The starting point

The challenge

Network incidents are slow to diagnose because the evidence is scattered across vendor devices, operating systems, telemetry, logs and configs. On-call engineers log into box after box to piece the story together, often in the middle of the night.

The solution

What we built

  • Built a ReAct-style investigation agent with LangGraph and LangChain. A Grafana alert triggers it, and it sets a goal and pulls the relevant context.

  • Spawns a sub-agent for each device, which connects and runs real read-only commands, so checks across devices happen in parallel.

  • Normalises vendor differences before comparing, for example IOS-XR layer-2 MTU against IP MTU, so a flagged mismatch is real rather than a reporting artefact.

  • Correlates the findings into an evidence list with a confidence score, then proposes a scoped fix for an engineer to review and apply.

  • Engineers can ask follow-up questions against the same investigation context.

Architecture

How the system works

How it fits together
  1. 01Grafana alertAn incident triggers the agent
  2. 02Agent managerSets the goal, gathers context
  3. 03Device sub-agentsParallel read-only CLI checks
  4. 04NormaliseVendor and OS differences
  5. 05CorrelateEvidence and confidence score
  6. 06Scoped fixAn engineer reviews and applies it
Engineering

How it was engineered

  • Built evaluation sets from recorded incidents and device outputs, including synthetic failure scenarios run on a network testbed.

  • Evaluated the agent's reasoning and root-cause findings after every iteration, locally and against the testbed.

  • Traced every run in LangSmith, from the incoming alert to the proposed fix.

Scope

What was delivered

01

Alert-triggered investigation agent

02

Per-device sub-agents for parallel checks

03

Vendor and OS normalisation logic

04

Evidence and confidence reporting

05

Follow-up questions on an investigation

06

LangSmith tracing

Gallery

Screens and diagrams

Technology

Stack

OpenAILangGraphLangChainLangSmithGrafanaPython

Need something similar?

We can scope and build a system with comparable capabilities, shaped around your own workflows, data and integrations.