The coordination layer for physical systems
Offline Protocol puts transport, identity, discovery, shared state, and execution in one SDK, so applications, machines, and agents stay authenticated, in sync, and working across local, mesh, gateway, and cloud paths. Your cloud stays the system of record.
Table: the platform as a stack. Your application on top. Connect: DORS transport and OfflineID identity. Sync: edge sync and telemetry. Invoke: service discovery, and Capability Exchange, which is coming soon. Underneath, the four paths a request can take: nearby, mesh, gateway, and cloud.
What a coordination layer is
Every product rebuilds the same plumbing. Pairing, store and forward, retry, recovery, and who is allowed to talk to whom get written again for each app and each radio, and the same failures get rediscovered each time.
One contract above every path. Your code sends a request once. Whether it is answered by the device next to it, a peer eight hops away, a provisioned gateway, or your cloud is decided underneath. The guarantees are the same on every one.
Your cloud stays the system of record. Offline Protocol is the system of local execution. Work happens where the devices are, and reconciles with the database you already run when a link returns.
DORS
The Dynamic Offline Relay Switch routes over BLE, WiFi Direct, internet, Reticulum, and Nostr, scores each transport on live signal, congestion, energy, and reliability, and moves every message to the best path. Multi-hop relay up to 8 hops, MLS encryption by default, and a reliability layer of acknowledgment, retry, and deduplication underneath.
How mesh networking worksDemonstration of transport failover on the offline mesh networking stack: a field unit whose internet link is down stays connected to a fleet dashboard over an active Bluetooth LE mesh link, with WiFi Direct on standby.
OfflineID
An Ed25519 keypair made on the device, with an address derived from the key, so two devices verify each other with one signature check and no server, certificate authority, or signal. Accounts bind through a signed challenge, credentials carry a fixed lifetime, and field data is signed at capture.
How offline identity worksDemonstration of offline identity verification: a phone holding an Ed25519 OfflineID authenticates against a gate access panel device-to-device with zero connectivity, and access is granted offline.
Service discovery
A device announces what it can do, the announcement travels hop by hop, and any peer up to 8 hops away calls it like an API endpoint. Caller and provider verify each other with OfflineID, and request and response ride the same encrypted session.
How service discovery worksDemonstration of serverless service discovery on the offline mesh: a phone discovers a thermal camera service advertised three hops away and invokes it request/response, streaming imagery with no server and no DNS.
Edge sync
Map, list, text, and counter documents that any member of a space edits while disconnected. When replicas meet, only the changes travel and every replica lands on the same result, with no server deciding who wrote last. On by default, on storage you already own.
How edge sync worksDemonstration of replicated documents: two field units edit the same work order while disconnected, exchange compact deltas when they meet, and converge on the same document with no server.
Gateways and paths
A gateway is something you deploy and configure, not a role a phone drifts into. It attaches a unit, carries what the mesh cannot deliver, and returns a verdict. Only the recipient ever settles a message, and a message with no path is parked and re-driven the moment one appears.
How reliable delivery worksDemonstration of gateway routing: a field unit with no internet reaches a provisioned gateway over the mesh, the gateway attaches the unit, carries the message, and returns a verdict.
One SDK surface
One Rust core underneath every binding, so the guarantees are the same on a phone, a laptop, a server, and a Cortex-M part.
iOS and Android through React Native, the surface most field apps ship on. Early native Swift and Android packages need no React Native.
macOS, Linux, and Windows, for gateways, tooling, and analysis. pip install offline-protocol-sdk.
The core itself, for anything that links a crate.
