Skip to main content
Offline Protocol connects local workflows to the systems that already store your data. A destination adapter handles schema mapping, authentication and backend acceptance. Your devices keep using the SDK for discovery, identity, messaging and shared state.

​
Confluent and Kafka

The Confluent connector is a private evaluation release (v0.1.1), qualified against Mesh SDK v0.26.0. Container images are private and access is provisioned for the evaluation. It is not a public marketplace listing. The Source Connector exports retained collector events into Kafka through Kafka Connect. The deployment includes the local source, collector/export service and connector; the connector alone does not add radios or local retention to a device. Use the retained-event contract to define when records move from pending to accepted. Contact sales@offlineprotocol.com for the evaluation package, supported deployment profile and commercial terms.

​
On request

These integrations are scoped on request; they are not installed connectors or approved marketplace listings. SAP and MongoDB integrations are also available for scoping on request; no released connector is documented. Use your existing backend API with the retained-event pattern today, or contact us to scope the destination you need.

​
MQTT

Keep the customer’s existing MQTT infrastructure. Offline Protocol adds local discovery, authorized device interactions and application-level acceptance around it. A bridge translates the resulting records into the required topics and schemas. A reachable local MQTT broker can already operate without internet. MQTT delivery acknowledgments and retained messages are not proof that a technician accepted a handoff or that an enterprise record was committed. Define those boundaries in your application and adapter. No MQTT bridge ships with the SDK. A bridge requires an explicit implementation and qualification scope.