Offline Protocol: Peer-to-Peer Sync, Messaging and Identity for Devices

Every smart machine can do useful work on its own. Getting machines to complete a job together is the hard part. It takes custom integrations across devices, permissions, networks and backends, and companies pay for gateways, cloud services, messaging, synchronization and engineering teams to hold it all together.

Offline Protocol replaces that with one reusable software layer for discovery, trust, data exchange and nearby capabilities, running over the links your devices already have. The result is less custom integration, less dependence on paid backhaul and cloud round trips, fewer manual handoffs and faster access to operational information where the work happens. A technician pulls a turbine's history on site; a driver and yard worker complete a handoff directly. Continuity through outages is built in.

Common uses Field service and inspections: technicians share job data, photos and asset history on site, device to device. Logistics, yards and fleets: drivers, handhelds and vehicles hand off manifests and proof of delivery directly. Retail, events and venues: staff devices, kiosks and point-of-sale keep syncing when the network is congested. Defense, public safety and disaster response: teams coordinate across denied, disconnected, intermittent or limited (DDIL) networks. Industrial IoT and robotics: machines, sensors and robots discover and call each other's services locally. AI agents at the edge: on-device and nearby agents exchange context and invoke each other's tools without a cloud round trip.

For developers SDKs for React Native and Rust, a Python package on PyPI for servers and desktops (Python 3.10 to 3.13 on Linux, Windows and macOS on Apple silicon), and native iOS (Swift) and Android (Kotlin) packages in early preview. On a gateway or site computer, the Python service runs every link the box is configured for, LAN, Bluetooth LE and the hosted relay, and lets the programs you already run call services on other machines with plain HTTP, encrypted end to end, so site systems keep working together without a round trip through the cloud. For firmware teams, a Rust leaf crate compiles for ESP32-C6, ESP32-H2 and Cortex-M microcontrollers. Peer-to-peer transport over Bluetooth LE mesh and Wi-Fi, CRDT-based document sync, MLS (RFC 9420) end-to-end encryption on by default, a hosted relay, and an MCP server so coding agents can plan and scaffold an integration.

What is included OfflineID identity: device-owned keys, verified device to device and bound to your accounts. Edge sync: shared state that converges between nearby devices without a server in the loop. Encrypted messaging: MLS encryption on by default, with a hosted relay when no nearby path exists. Nearby service calls: devices, apps and agents advertise, discover and invoke each other's services with no server or DNS. Delivery to your systems: device data reaches the systems you already run, including AWS data services and Kafka.

Proven at scale Offline Protocol has reached 350,000+ devices across 140+ countries, with 60,000+ SDK downloads in 2026.

How to buy Pro and Scale plans. Annual contracts for 12, 24 or 36 months, with 15% off the 24 month term and 25% off the 36 month term. Pro includes, every month, 10,000 OfflineID monthly active users, 100,000 hosted relay deliveries, 2 million telemetry events and 2,500 Proof of Location verifications. Scale includes, every month, 50,000 monthly active users, 1 million hosted relay deliveries, 10 million telemetry events and 10,000 location verifications. When a quota is reached, that service pauses until the next month or until you upgrade; for capacity beyond Scale, contact us about Enterprise. Traffic that stays between nearby devices never counts against a quota.

SDK commercial licensing. The mesh SDK is free under AGPL-3.0-only. Proprietary apps, App Store apps and closed firmware ship it under a commercial license: $14,988 per app per year, with 15% off a 24 month term and 25% off a 36 month term. Choose the number of apps, and combine licenses with a plan in one contract.

Enterprise. Contracted usage, production support with an SLA, SCIM, audit logs and forward-deployed engineers who take a rollout from the first workflow to production. Enterprise is quoted to your deployment and sold by private offer. Request one on this page.

After you subscribe, you continue to the Offline Protocol developer portal to create or link an organization, take an API key and see your plan and usage.