Documentation Index
Fetch the complete documentation index at: https://docs.rootkey.ai/llms.txt
Use this file to discover all available pages before exploring further.
Overview
ROOTKey’s MQTT integration model is designed for environments where the REST API model is architecturally impractical - industrial control systems, IoT device networks, edge deployments, and real-time sensor pipelines that already operate over the MQTT protocol. MQTT is a lightweight, publish-subscribe messaging protocol designed for constrained environments and unreliable networks. ROOTKey’s MQTT integration allows devices and systems to publish data directly into ROOTKey’s integrity pipeline without requiring an HTTP stack or persistent connection management. This model is the recommended choice for Operational Technology (OT) environments, industrial IoT (IIoT) deployments, and any architecture where events are naturally expressed as MQTT messages.Architecture Overview
Devices publish messages to defined MQTT topics. ROOTKey’s MQTT bridge subscribes to those topics, processes incoming payloads through the configured data processing protocol, and anchors the integrity proof to the blockchain. The result is a tamper-evident, cryptographically verifiable record of every event published through the pipeline - without requiring devices to implement HTTP clients or manage connection state.Typical Use Cases
Industrial IoT and SCADA Systems
Sensor readings, PLC outputs, and SCADA events published to ROOTKey’s integrity pipeline for tamper-evident archiving and regulatory compliance.
Smart Manufacturing
Production line telemetry, quality control measurements, and machine event logs anchored in real time without disrupting the OT network architecture.
Energy and Utility Monitoring
Smart meter readings, grid events, and energy consumption data published over MQTT and anchored for regulatory reporting and dispute resolution.
Connected Vehicle and Fleet
Vehicle telemetry, GPS events, and condition data published from edge devices and anchored for custody, insurance, and compliance purposes.
Environmental Monitoring
Air quality, water quality, and environmental sensor networks publishing to ROOTKey for regulatory reporting with cryptographic evidence of data integrity.
Building and Facility Management
BMS sensor data, access logs, and environmental controls published over MQTT for compliance and operational auditing.
Integration Considerations
Broker selection ROOTKey supports both a managed broker model (hosted by ROOTKey) and a client-hosted broker model. The managed broker is the fastest path to integration. For environments with network isolation requirements, a client-hosted broker with a controlled egress to ROOTKey’s MQTT bridge is the recommended architecture. Topic design MQTT topic structure maps to ROOTKey vault and asset hierarchy. Topic design should be agreed during the integration scoping phase to ensure correct routing and data classification. QoS and delivery guarantees Use QoS level 1 or 2 for data that must be reliably delivered to the integrity pipeline. QoS 0 is appropriate for high-frequency telemetry where occasional loss is acceptable. Message ordering and deduplication behaviour depends on the selected QoS level. Payload size and frequency High-frequency, small-payload workloads are well-suited to RKP-2 (Off-Chain). For mixed workloads where some events require stronger on-chain evidence, RKP-3 (Hybrid) allows per-topic routing configuration. Device authentication Each device or device class authenticates to the broker using credentials scoped to the target ROOTKey workspace. Credential rotation policies should be defined as part of the device lifecycle management process. OT/IT convergence For environments where MQTT brokers sit within the OT network boundary, ROOTKey supports a broker bridge architecture that relays messages across the OT/IT boundary without exposing OT systems directly to external networks.Request a technical scoping call
MQTT deployments are scoped per environment. Our engineering team will assess your broker topology, device architecture, and data classification requirements.
Contact enterprise sales
Discuss MQTT integration options, broker models, and enterprise agreement terms.