See every asset on the plant floor. Without touching the network.
EmberNet gives you continuous visibility into plant floor equipment without putting your control systems on the internet. It registers the PLCs, HMIs, switches, gateways, and sensors you already run, reads them over the protocols they already speak, and does it with read-only collectors: no writes, no discovery broadcasts, and no network scanning. Data is processed on the edge node and sent outbound only, so there is no inbound port to open.
A registry of everything on the network, with health on each.
Device Monitor is the registry for every PLC, HMI, switch, firewall, protocol gateway, and sensor on the network.
Each device shows one of four health states: Healthy, Warning, Critical, or Unknown. Unknown and Critical mean very different things and the registry tracks both. A device that stops reporting is not the same as a device reporting a fault, and your operators can see the difference.
On top of the registry, EmberCORE collects process values from every device it connects to: the readings your PLCs are producing, carried with the quality status the collector assigns on each cycle. Good, Uncertain, or Bad. A Bad reading is never plotted as a value.
Health states tracked per device
Industrial protocols supported
Reading quality levels on every value
The protocols your equipment already speaks.
EmberCORE connects to equipment over the protocols it already uses. You configure the devices you want to read. Nothing else is touched.
| Protocol | Devices it reaches | What it reads |
|---|---|---|
| OPC UA | PLCs, SCADA servers, historians | Secured per organization, with modern security policies only |
| Modbus TCP | PLCs, RTUs, meters | Holding and input registers |
| Modbus RTU | Serial-attached RTUs and meters | Via RS-485 gateway |
| S7comm | Siemens S7-300, S7-400, S7-1200, S7-1500 | Data blocks and memory areas |
| EtherNet/IP | Allen-Bradley PLCs and drives | Tag-based reads |
| MTConnect | CNC machines and machining centers | Device streams |
| FINS | Omron PLCs | DM area and IO memory |
| MELSEC | Mitsubishi PLCs | Word and bit devices |
| BACnet/IP | Building automation, HVAC | BACnet objects |
| DNP3 | RTUs, IEDs, substations | Binary inputs, analog inputs, counters |
| MQTT | IoT gateways and sensors | Subscribe only; broker-side only |
Five additional protocols are available through a gateway. See the full list in the docs.
Read only, always.
The statement that matters most to a security reviewer is this: every collector reads, and nothing else.
There are no writes, no RUN or STOP commands, no discovery broadcasts, and no scanning. The collector connects to the device addresses you configure, reads the values you specify, and closes. The device does not know the difference between a poll and a watchdog.
On the network side, EmberFLUX means the edge node never opens an inbound port. The data leaves the plant outbound over port 443 to a zero-trust overlay. No firewall rule is added to let traffic in. No VPN gateway is installed. The control network stays dark to the outside.
The read-only guarantee
- No writes to any device
- No RUN or STOP commands
- No discovery broadcasts
- No network scanning
- No inbound ports on the edge node
- Collectors only reach the devices you configure
- OPC UA: secured per organization, modern security policies only
Process anomalies, not network anomalies.
EmberNet runs AI anomaly detection on process data, not on network traffic.
It watches the values your PLCs are producing: temperatures, pressures, flow rates, cycle times, and the quality status on every reading. When a value drifts outside its established pattern, or when a reading goes Uncertain or Bad, EmberCORE flags it and your operators see it.
This is not the same job a network anomaly detection tool does. A network tool watches packets. EmberNet watches process values. If you need packet-level detection, a dedicated OT network monitoring tool is the right buy for that layer, and they can run alongside EmberNet without conflict.
The honest list.
A page that states its limits is more trustworthy than one that claims everything. Here is what EmberNet does not do in this area.
- Write to any device or issue control commands
- Scan the network for new devices
- Send discovery broadcasts
- Inspect network traffic packets
- Replace a dedicated OT network monitoring tool for packet-level detection
- Require an inbound firewall port on the plant network
Answers for the security review.
Does EmberNet scan the OT network?
No. EmberNet reads from devices you configure explicitly, using read-only collectors. There are no discovery broadcasts and no network scanning. Every collector reads and nothing else: no writes, no RUN or STOP commands.
What industrial protocols does EmberNet support for OT monitoring?
EmberCORE reads over OPC UA, Modbus TCP, Modbus RTU, S7comm, EtherNet/IP, MTConnect, FINS, MELSEC, BACnet/IP, DNP3, and MQTT natively, plus five more through a gateway.
What is EmberNet's OT asset inventory?
Device Monitor is the registry for every PLC, HMI, switch, firewall, protocol gateway, and sensor on the network. Each device shows one of four health states: Healthy, Warning, Critical, or Unknown.
What anomalies does EmberNet detect?
EmberNet detects anomalies in process data: values outside expected ranges, missing readings, and patterns that differ from established baselines. It does not inspect network traffic packets. A dedicated OT network monitoring tool is the right choice for packet-level network anomaly detection.
Can EmberNet send OT data to a SIEM?
Yes. Data collected at the edge moves outbound over EmberFLUX to your time-series store and can be forwarded to Splunk, Microsoft Sentinel, or any SIEM that accepts a webhook or syslog feed, without opening an inbound port on the plant network.
Ready to see your plant floor in one view?
Tell us what PLCs and protocols you run. We will show you how EmberNet connects to them.