For IT & OT Teams
Cameras, door controllers and PLCs run on your network, but each team sees only part of them. eyeOT maps what each device depends on, catches the recording, image and server failures ping misses, and puts IT, OT and security on one incident. Admin-only remote fixes need no inbound firewall rules.
How it works
eyeOT covers discovery through Day‑2 operations for cameras, VMS servers, door controllers, PLCs and the network underneath. IT, OT and security work from the same map without jumping between the VMS, the NMS and a spreadsheet.
01 · Know what’s on the network
“Which switch is that camera on?” Today the answer lives in a Visio of what someone thought was installed, a VMS device list and a login to every switch. eyeOT builds the inventory from SNMP, CDP/LLDP, CAM tables, your VMS and scans of the subnets you choose: make, model, IP, MAC and managed-switch port.
02 · Beyond up/down checks
“Legal needs footage from the 14th.” The camera answered ping all month, so nobody knew it had stopped recording. eyeOT checks recording and retention per camera, ImageAssure checks snapshots for blurred, blocked or shifted views, and server checks catch a degraded RAID array or a stopped VMS service.
03 · Point-of-failure incidents
“Cameras in the garage are down. Is it the network?” When a switch or uplink fails, eyeOT rolls the alerts into one incident at the point of failure and lists the cameras, controllers and PLCs behind it. IT, OT and security work the same incident instead of each team proving it isn’t their gear.
04 · Remote actions
“Can someone drive out and power-cycle it?” Not for a reset. Admins reboot Axis and Hanwha cameras, Cisco switches and servers, bounce a Cisco or MikroTik switch port (cycling PoE on supported switches), restart a Windows service or open SSH and RDP. Nothing runs unless an admin starts or schedules it.
05 · Reporting & capital planning
“What was our camera uptime last quarter, and what do we replace next year?” eyeOT reports uptime, MTTA/MTTR against your SLA and health scores by site, plus drive and RAID health, firmware versions on supported devices and the systems that keep failing.
Bring your device mix: cameras, VMS, controllers, PLCs and switch vendors. We’ll walk through discovery, a point-of-failure incident and a remote fix next to the NMS, VMS and ITSM you already run.
The operational impact
IT/OT convergence put these devices on your network. In a county, a hospital or a utility, their downtime is a safety and liability issue. Here is what changes when they’re in your operations, too.
Catch what staff, the public or auditors would notice first, including what your NMS still reports as up.
Open the failed switch or uplink with every camera, controller and PLC behind it already listed.
Port bounces, reboots, service restarts and SSH or RDP sessions run through the site agent.
Recording status, switch port, server health and OT availability in eyeOT instead of separate logins.
Scheduled MTTA, MTTR, availability and health score reports by site for leadership, auditors and vendors.
Hardware health, firmware and incident history by site behind each capital request.
Customer story
Donor Network of Arizona watches its servers, network and cameras in eyeOT, and chooses which alerts go to its outside NOC.
eyeOT watches our servers, network and cameras in one place, and we decide which alerts go to our outside NOC. When the NOC calls, we’re both looking at the same incident and can get straight to the fix.
Fits the stack you already run
Check fit before the demo: what eyeOT integrates with, which devices it covers and at what depth, and how the agent and hosting work.
IT & OT Team FAQs
eyeOT is an infrastructure management platform for the cameras, VMS and recording servers, door controllers and intercoms on your network, and the switches, servers and links they depend on. It discovers and maps them, checks that cameras are recording, flags unusable images with ImageAssure, groups the alerts behind a failed switch or uplink into one incident, and lets admins bounce ports, reboot supported devices and restart services remotely. It also monitors PLCs and building controllers at network level.
No. eyeOT runs alongside them. Keep your RMM for endpoints and patching, your VMS for video, your NMS for the network and your BMS or SCADA for control. eyeOT connects what each one sees only part of: the camera in the VMS, the switch port it’s on, whether it’s recording a usable image, and the remote fix when something fails. Teams without an NMS use eyeOT’s network monitoring for their switches, routers and wireless links: availability, interface errors and discards, and the topology.
No. eyeOT monitors availability and health and gives your engineers remote fixes. It doesn’t inspect industrial protocols or detect threats, so it runs alongside your OT security tools. What it adds to your security program is a current asset inventory, with new and unknown devices flagged for review, and config changes against a baseline on supported switches and routers.
Outbound HTTPS on port 443, nothing inbound. There’s no VPN or jump host to maintain, and we provide the destination list for your egress rules. The agent runs on Windows, Linux, macOS or Docker, covers 500 to 1,000 devices and reaches non-routed camera VLANs from a host with a second NIC in that VLAN, such as the recording server. Run one agent per segment, such as OT, security and infrastructure, and all of them report to one map. A backup agent keeps monitoring running if the primary drops. One customer environment runs more than 20,000 devices.
It goes only where you point it. Discovery scans just the subnets or IP ranges you add, so you can leave a control or SCADA network out of discovery and add PLCs and controllers one at a time by IP. eyeOT checks them over ICMP or SNMP and doesn’t read or write control points. Its only built-in action on a controller is a port bounce or PoE power-cycle on a supported switch, and an admin has to start it.
Yes. For networks with no internet egress, deploy the eyeOT platform on-premises. ImageAssure checks snapshots rather than streaming video, and in an on-premises deployment it runs locally, isolated from any cloud. For segmented networks that allow outbound HTTPS, an agent inside the segment is enough. Ask us which features are available on-premises.
Any IP device at network level: availability over ICMP or SNMP, IP and MAC address and its port on a managed switch. That covers PLCs, BMS and HVAC controllers, intercoms and door controllers. PoE-powered devices can also be power-cycled from supported switches. Deep integrations cover VMS, cameras, switches, wireless radios, servers, VMware vSphere and Life Safety Power supplies. eyeOT doesn’t read or write BACnet or Modbus points today.
Not at the software level. eyeOT sees door controllers and panels on your network: whether they’re online and which switch port they’re on. A PoE-powered controller can be power-cycled from its switch port on supported switches. eyeOT doesn’t read door, reader or lock status.
Bounce switch ports on Cisco and MikroTik, reboot Axis and Hanwha cameras, Cisco switches and servers, start and stop Windows services, power-cycle vSphere VMs, and open SSH or RDP sessions in the browser through the agent. Only account admins can run actions or open sessions. Nothing runs automatically except the reboots and scripts you schedule.
It should cut it. When a switch or link fails, the alerts behind it become one incident at the point of failure, and repeat alerts roll into the open incident with an occurrence count. You set the rules: duration thresholds so a brief drop doesn’t page anyone, a minimum severity for each channel, per-device mutes, and maintenance mode for planned work.
Incidents can open tickets in ServiceNow or ConnectWise PSA, and with ConnectWise, eyeOT updates the ticket’s status when the incident resolves. Alerts go to Microsoft Teams, Slack, PagerDuty, email or webhook; your PagerDuty schedules decide who gets paged. Other ticketing and work-order systems can take incidents by email or webhook, and maintenance mode suppresses alerts during a change window.
Yes. Give each integration partner its own account, as Queen Anne’s County does. Viewer access shows status without letting anyone change settings or run actions, and remote sessions stay limited to admins.
MTTA and MTTR against your SLA, an operational review with incidents by hour and type and the top failing systems, health scores by site, availability history and scheduled CSV reports. Firmware versions, drive and RAID health and incident history feed the refresh plan, and config snapshots on supported switches and routers show what changed against your baseline.
A current inventory with each device’s switch port, configuration snapshots of supported switches and routers, so the last known-good config is on file for the replacement, and the incident and availability history that shows what failed and when. eyeOT doesn’t push configs back to devices; your engineer configures the replacement from the saved copy.
eyeOT is priced per monitored device: a switch, a camera or a server counts once, with no separate charge per port or sensor. The total depends on how many devices you monitor and which add-ons you use, such as ImageAssure. Share a rough device count and we’ll send a quote.
Send a rough device count, your VMS and switch vendors and the networks that are off-limits. We’ll scope the demo to your environment and walk your security and OT teams through the outbound-only, agent-per-segment design.
