The edge gateway is the piece of ICP that lives at your site. It connects your field equipment to the platform — pulling telemetry for monitoring and safely pushing configuration back — and it buffers locally (store-and-forward) so nothing is lost if the network link drops. It is the on-site half of the edge-gateway monitoring and device control platform.
Device status
A gateway reports one of: Pending, Provisioning, Online, Degraded, Offline, or Decommissioned. It's shown online when it has sent a heartbeat within the last five minutes. Each gateway carries its serial, name, model, hardware revision, firmware version, and last-seen time.
Connectivity
The gateway is built to fit real industrial sites:
- Serial: dual RS-232 / RS-485
- Network: two Ethernet ports (so you can keep the equipment/OT network separate from the uplink)
- Wireless: Wi-Fi and Bluetooth (used for technician provisioning)
- Cellular: 4G LTE with SIM / eSIM and dual-SIM failover
- Location: optional GPS / GNSS
- I/O: digital inputs and outputs
- A hardware security element for device identity
Supported equipment
| Device types | Industrial protocols |
|---|---|
| PLCs, RTUs, meters, IoT sensors, network devices, gateways | Modbus (RTU/TCP), DNP3, OPC-UA, IEC 61850, BACnet, SNMP, MQTT / Sparkplug B |
Field provisioning
A technician commissions or swaps a gateway from the mobile app using QR code or Bluetooth, following a guided checklist — connectivity, discovered field devices, the point map, and a health check.
Telemetry points
Each monitored value the gateway reads is a telemetry point:
- Key, name, unit
- Data type — boolean, integer, float, or string
- The address it reads (for example, a Modbus register or an OPC-UA node id) and its protocol
- Access — read or read-write — and a writable flag
- Health, plus the last value and last sample time
Points are what alert rules watch and what device commands write to.