What is Offline Protocol?
Offline Protocol is the coordination layer for physical systems: it keeps applications, machines, and agents authenticated, synchronized, and operational across local, mesh, gateway, and cloud paths.
How does the mesh work?
DORS routes over BLE, WiFi Direct, internet, Reticulum, and Nostr under one contract and switches between them based on live signal, congestion, energy, and reliability. Messages relay across multiple hops with acknowledgment, retry, and deduplication built in, up to an 8-hop TTL.
What is service discovery?
Service discovery lets any device advertise a capability and any device within hop range discover, authenticate, and invoke it with a request/response pattern. No server, no DNS, no infrastructure. A device five hops away is invocable like an API endpoint.
How is data secured?
Sessions are encrypted with MLS (RFC 9420). Identities are Ed25519 keypairs whose addresses are derived from the key, so a peer proves its address by presenting the key. Keys never leave the device.
What platforms are supported?
iOS and Android through the React Native SDK, @offline-protocol/mesh-sdk on npm, with early native Swift and Android packages that need no React Native; a Python binding on PyPI for macOS, Linux, and Windows hosts, which also runs as a service that other programs on the box call over plain HTTP; a Java package on Maven Central for the JVM; a C API for C, C++, Go, C#, and other languages that call C; a Ruby gem on RubyGems; a preview Flutter plugin for iOS and Android with the React Native module's native surface; an experimental browser build that runs a full node in a Web Worker; Rust crates on crates.io for gateways and full peers; and a no_std leaf profile for constrained devices. One Rust core runs under all of them. See the developers page for installs and quickstarts.
How does telemetry work?
Telemetry is off until your app turns it on with a key from the developer portal. Once on, the SDK batches what the protocol did, with no message content and no identifier fields, and uploads it to the Offline Protocol ingest itself, where the portal turns it into dashboards. The stream covers deliveries, relaying, routing decisions, transport changes, and MLS session health.
What happens during outages?
Nothing changes for the mesh. Devices keep discovering, authenticating, and invoking each other over local transports, and state syncs opportunistically when a connection returns.
How large are the files the mesh can move?
Chunked transfer supports files up to 100 MiB across the mesh, with per-chunk acknowledgment and resume.
How do we evaluate this?
We run scoped evaluations of 4 to 16 weeks against your fleet, environment, and success criteria. Use the contact form to book one.
How do developers get started?
Install @offline-protocol/mesh-sdk from npm and sign up free at dev.offlineprotocol.com for API keys, hosted services, and analytics. The docs quickstart pairs two phones over the mesh, and the Offline Protocol CLI and MCP server give coding agents the same context.
How is Offline Protocol priced?
The mesh SDK is free under AGPL-3.0-only, the OfflineID and Proof of Location client packages are MIT or ISC, and local mesh traffic is never metered. Hosted services run on Free, Pro at $99 a month, Scale at $499 a month, and Enterprise on an annual agreement, each with included usage and published overage rates. A commercial license for the mesh SDK covers proprietary and App Store distribution.
Mizan Ali
Gokul
Satvik
