open source · windows & linux
Understand networks. Isolate access.
NetSage is a provider-agnostic foundation for secure, AI-assisted network and infrastructure investigation. The AI context contains only sanitized evidence and tightly bounded tools, never passwords, keys, tokens or arbitrary shell access.
Apache-2.0
01 Device
FortiGate
02 Driver
read-only
03 Tool Broker
allowlisted
04 AI context
sanitized evidence only
principle
Pass on evidence. Isolate access.
NetSage strictly separates device access, credentials, data preparation and AI analysis. A model may request a structured query, but it receives neither credentials nor unrestricted access to a network device.
Version 0.1 stays entirely read-only. Configuration changes, unrestricted commands and automatic discovery are deliberately not part of the project.
security model
Investigate in a structured way. Limit traceably.
Credential Isolation
Passwords and keys are resolved only inside the trusted connection layer and are never passed on to the AI.
Allowlisted Tools
A tool broker validates and relays only named, structured operations that the respective driver allows.
Read-only First
Diagnosis instead of change: the current scope collects facts, interfaces, routes, ARP and health data without configuration access.
Sanitized Evidence
Device output is treated as untrusted and is sanitized, typed and tagged with its origin before it crosses the AI boundary.
Auditable Broker
Tool calls are designed for a secret-free audit trail. Investigations and evidence can be stored locally in a traceable way.
Provider-neutral
The architecture separates the AI provider boundary from network access and the evidence model. Real providers are deliberately outside the current product scope.
field validation
Intermittent WAN outage.
In a real, authorized production network aboard a ship, the Internet connection repeatedly failed only after several hours of operation.
NetSage correlated FortiGate logs, interface state, historical events, routing and network state, and the timing of the WAN events. After about five minutes, the evidence pointed strongly to the physical WAN link. A subsequent manual inspection confirmed a faulty WAN cable as the cause.
Outage after several hours
Logs · status · routing · time
Physical WAN link
Faulty WAN cable
- ~5 minutes
- NetSage analysis
- ~3 hours
- estimated manual troubleshooting
This is a single operational case, not a controlled benchmark. NetSage helps experienced administrators narrow down the fault domain faster; technical judgment and physical verification remain with the human. View the anonymized technical case study
current status
Foundation done. Device access controlled.
- Runtime
- Python 3.13 · uv
- Platform
- Windows · Linux
- Network access
- FortiGate experimental · read-only
- Credential Store
- OS keyring · no plaintext fallbacks
- Local data
- Sanitized evidence · SQLite history
- License
- Apache License 2.0
The AI may investigate, not administer.
NetSage gives the AI no raw SSH connection, no shell and no configuration operation. Every possible access is modeled as a fixed, read-only operation, bounded by policy and traceable through sanitized evidence.
roadmap
Prove the boundary first. Then extend the platform.
The actual project status and all releases are documented in the repository. Network diagnostics are intended only for your own or explicitly authorized systems.
Secure diagnostic base
Typed models, inventory, observe policy, redaction, audit events, FortiGate evidence and local investigation history.
More network platforms
FortiSwitch, HP/HPE/ArubaOS-Switch and Aruba AOS-CX follow only with clear, read-only driver operations.
Real AI providers
Codex, Claude, Ollama and OpenAI-compatible APIs will be connected only behind the proven provider and evidence boundary.
$ git clone https://github.com/Oexyz/NetSage
Source code, security model, roadmap and installation notes are available in the public repository.