OPC-UA and MQTT native

The Edge Gateway subscribes to OPC-UA nodes and MQTT topics. Configuration is done through the admin UI — no code required. A profile rule maps raw topics to Qontiv's data model (equipment, tag, value) using a pattern-matching syntax that handles ISA-95 Unified Namespace topics automatically.

Native protocol and vendor support

OPC-UA — the industry baseline. Subscribe to nodes, browse address spaces, configure via the admin UI.
MQTT Sparkplug B — Ignition, Sepasoft, and any Sparkplug B-compatible broker. Auto-discovery of edge nodes and devices.
Rockwell FactoryTalk Optix and Linx — direct integration for the dominant SCADA stack in North American automotive. No OPC-UA bridge required.
Ignition — Ignition tags consumed via Sparkplug B or direct gateway-to-gateway connections.
Atlas Copco smart tools — torque values, fastening cycles, and calibration status pulled directly from Atlas Copco controllers for real-time SPC and traceability.
ISA-95 Unified Namespace — auto-discovery and conformance for plants standardizing on UNS architecture.

Runs anywhere on your factory network

The gateway is a containerized Linux service. Run it on a Raspberry Pi, an industrial PC, or a VM — whatever's already on your OT network. Minimum specs: 512 MB RAM, 2 GB storage.

Outbound-only connection

The gateway initiates the connection to the Qontiv cloud; nothing connects inbound to your factory network. This satisfies most OT security and network segmentation requirements without firewall exceptions.

ISA-95 Unified Namespace support

Factories following ISA-95 UNS MQTT conventions connect with zero configuration. A single profile rule captures the enterprise/site/area/equipment/tag structure and maps it automatically.

Custom protocol extension

For equipment that doesn't speak OPC-UA or MQTT (legacy Modbus, REST APIs, file-based output), the extension interface allows custom connectors without modifying the core gateway.

First machine connected in under 2 hours