Network monitoring that speaks every vendor's language.
SAMURAI is a self-hosted network monitoring and security platform that watches Cisco APIC, FMC, NDO, ISE, Palo Alto, Fortinet FortiGate, VMware vCenter, routers, and switches from one dashboard, device health, configuration changes, endpoint inventory, and compliance, continuously synchronized.
Updated June 2026
What it monitors
Health checks every 2 minutes
HTTPS and TCP reachability with per-device latency, fleet-wide: controllers, firewalls, and CLI devices alike.
Configuration change detection
Snapshot-based diffs with volatile-field filtering, so you see real changes, not noise, with the admin who made them.
Endpoint discovery
Endpoints correlated from MAC tables, ARP, DHCP snooping, CDP/LLDP, 802.1X, and an offline IEEE OUI database.
CIS compliance checks
140+ automated checks for IOS-XE, NX-OS, IOS-XR, and ASA with scoring, waivers, and remediation tracking.
Open observability
Prometheus metrics endpoint and RFC5424 syslog forwarding. Plug into the monitoring stack you already run.
Reports & exports
Any table exports to CSV, XLSX, HTML, or PDF: inventory, policies, endpoints, compliance results.
SAMURAI vs traditional SNMP monitoring suites
SolarWinds NPM, PRTG, and Zabbix are mature SNMP-based monitors. SAMURAI watches a different layer of the same network: configuration state and security posture rather than interface counters.
Data plane
SAMURAI
Configuration state read over native APIs and SSH, the way an engineer would
SolarWinds / PRTG / Zabbix
SNMP polling, agents, and flow collectors
What you catch
SAMURAI
Configuration changes with admin attribution, policy drift, compliance regressions
SolarWinds / PRTG / Zabbix
Interface utilization, up/down state, performance baselines
Setup
SAMURAI
One self-hosted container; device types auto-detected, no per-sensor licensing
SolarWinds / PRTG / Zabbix
Per-device SNMP/agent setup; sensor- or element-based licensing
Performance graphs
SAMURAI
Not our focus: no bandwidth graphing or NetFlow analytics today
SolarWinds / PRTG / Zabbix
Their core strength: counters, flows, and long-term performance history
Honestly: if you need bandwidth graphs and NetFlow, the SNMP suites do that well. Many teams run SAMURAI beside one: counters from the monitor, configuration truth and change attribution from SAMURAI.
Frequently asked questions
What is network monitoring software?
Network monitoring software continuously checks the health, configuration, and inventory of network devices (firewalls, switches, routers, controllers) and alerts you when something changes or breaks. SAMURAI does this across nine device types from one self-hosted dashboard: health checks, configuration change detection, endpoint discovery, and compliance.
Is SAMURAI a network analyzer or a packet analyzer?
SAMURAI is a network analyzer at the configuration level: it reads device state — policies, routes, endpoints, changes — over native APIs and SSH. It is not a packet analyzer or Wi-Fi analyzer: it does not capture or decode traffic. Engineers typically keep a packet-capture tool for deep dives and use SAMURAI to know what the network is configured to do and who changed it.
Is SAMURAI real-time network monitoring?
Health checks run every 2 minutes and configuration syncs run continuously in the background; completed syncs push updates to the dashboard instantly. For any view you can also bypass the cache and query the device live.
Does SAMURAI use SNMP or agents?
No agents and no SNMP polling required. SAMURAI talks to controllers and firewalls over their native APIs and to routers and switches over SSH, the same way an engineer would, just continuously.
What scale does it handle?
Production deployments run multi-vendor fleets with thousands of correlated endpoints; endpoint queries return in 100-300 ms.
How does alerting work?
Email, Telegram, and webhook notifications for sync failures and compliance regressions, plus a Prometheus endpoint if you want to alert from your own stack.
How do I deploy it?
A single docker run. The image is published on Docker Hub (beyrak44/samurai) and runs fully self-hosted, including air-gapped environments.