YOUR NETWORK, IN CONTEXT
NeRTS brings network health, device performance, and topology together so your team can see what needs attention and where to start.
Self-hosted. Built for networks with many locations.
3 devices. One shared connection.The access switch and its downstream devices share the affected uplink.
GROUNDED IN REAL OPERATIONS
Developed through the day-to-day challenges of keeping infrastructure visible across hundreds of locations.
Internal deployment experience
LESS SEARCHING. MORE UNDERSTANDING.
Move from a network-wide view to the details of a single connection. Keep the pieces of an investigation together.
01 SITE HEALTH
Start with the locations that need you. See facility health, device availability, and active alerts together, then open a site to understand what changed.
| Facility | Health | Devices up | Alerts |
|---|---|---|---|
| Needs attention | 11 / 14 | 3 | |
| Healthy | 24 / 24 | 0 | |
| Healthy | 9 / 9 | 0 |
RIVERSIDE OFFICE / SELECT A DEVICE
This switch and two downstream devices share the interrupted connection to RV-SW01. Start with that uplink.
02 NETWORK TOPOLOGY
A device rarely exists on its own. See how firewalls, switches, and downstream equipment connect, and which devices share an affected link.
Three alerts can be
one place to investigate.
Topology shows discovered relationships. Engineers use those relationships alongside monitoring evidence to investigate the cause.
03 PERFORMANCE & HISTORY
A current status tells part of the story. Interface performance and recent events help explain what happened before an interruption—and what happened after.
We plan to integrate Claude to help engineers investigate outages, connect related alerts, and summarize incidents using the monitoring data available in NeRTS.
In development planning. This assistance is not available in the current platform. Engineers would review any proposed network changes.
“Why did these devices become unreachable at the same time?”
INTENDED INVESTIGATION WORKFLOW
Bring related alerts and state changes together.
Look for relationships in the available topology.
Explain the evidence and keep the engineer in control.
BUILT FROM THE OPERATOR’S SIDE
NeRTS grew out of hands-on infrastructure work across hundreds of facilities. When a small team supports a large network, finding the right context shouldn’t be another job.
The motivation is straightforward: make it easier to understand the environment, find the source of a problem, and support more locations with a small team.
LET’S GET A CLEARER PICTURE
Tell us what you manage and where visibility gets difficult. We’ll show you how NeRTS approaches it.