llms.txt
+72 −5
https://www.offlineprotocol.com/llms.txt
− > 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. Its open-source mesh SDK (v0.27.0, AGPL-3.0 with commercial licensing) is a Rust core with a React Native TypeScript binding for iOS and Android, a Python binding for desktop, and twelve crates on crates.io. It provides DORS multi-transport routing over Bluetooth LE, WiFi Direct, internet, Reticul− - Packages (npm unless noted): @offline-protocol/mesh-sdk 0.27.0 (React Native; Rust core on crates.io as offline-protocol, Python binding), @offline-protocol/id-react 0.2.0 and @offline-protocol/id-react-native 0.3.3 (OfflineID sign-in), @offline-protocol/pol 0.1.2 (Proof of Location, early access on Ethereum Sepolia testnet), @offline-protocol/cli 0.2.6 (the `offline` command and local MCP server).− - [Embedded and OEM platforms](https://www.offlineprotocol.com/embedded): A no_std Rust leaf profile that speaks real MLS on a Cortex-M33 class part in 449.5 KiB, beside the radio stack you already ship.− - [Compare overview](https://www.offlineprotocol.com/compare): Offline Protocol against Ditto, Bridgefy, Meshtastic, goTenna, Berty, Briar, Amazon Sidewalk, and Google Nearby Connections.− - [Offline Protocol vs Google Nearby Connections](https://www.offlineprotocol.com/compare/nearby-connections): A routed multi-hop mesh SDK versus an Android direct-link API.+ > 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. Its open-source mesh SDK (v0.28.0, AGPL-3.0 with commercial licensing) is a Rust core with a React Native TypeScript binding for iOS and Android, a Python package on PyPI for desktop and gateways, early native Swift and Android packages, and twelve crates on crates.io. It provides DORS multi-trans+ - Packages (npm unless noted): @offline-protocol/mesh-sdk 0.28.0 (React Native), @offline-protocol/id-react 0.2.0 and @offline-protocol/id-react-native 0.3.3 (OfflineID sign-in), @offline-protocol/pol 0.1.2 (Proof of Location, early access on Ethereum Sepolia testnet), @offline-protocol/cli 0.2.6 (the `offline` command and local MCP server).+ - Mesh SDK installs, all v0.28.0 (2026-10-06):+ - React Native (iOS and Android): `npm install @offline-protocol/mesh-sdk`. React Native 0.70+, iOS 13+, Android API 24+.+ - Python: `pip install offline-protocol-sdk` (import `offline_protocol_sdk`). Python 3.10 to 3.13. Wheels for macOS arm64 (macOS 14+), Linux x86_64 and aarch64 (glibc 2.34+), and Windows x86_64; no Intel macOS wheel, no musl or Alpine wheel, no source distribution. Includes `offline-protocol-service`, the local API server: one engine for several local applications over JSON-RPC 2.0 on a WebSocket.+ - Rust: `cargo add offline-protocol` (twelve offline-protocol crates on crates.io, Rust 1.87+). Built-in file stores sealed under a store key serve hosts with no platform keystore.+ - Swift (early): Swift Package Manager, `https://github.com/Offline-Protocol/offline-protocol-swift.git` from 0.28.0, product OfflineProtocolSDK. iOS 13+, iOS only. Its public API is not settled yet, storage providers are not public, and wiring transports to the engine is the app's job.+ - Android (early): the Kotlin bindings and native libraries for four ABIs, as offline-protocol-0.28.0-android.zip on the GitHub release (https://github.com/Offline-Protocol/offline-protocol-sdk/releases/tag/v0.28.0). Not on Maven Central. Same early status as the Swift package.+ - Desktop native libraries for Linux x86_64 and aarch64, macOS arm64, and Windows x86_64 are attached to the same GitHub release.+ - Embedded: `offline-protocol-leaf` (no_std). CI gates its compile for Cortex-M33, Cortex-M0, ESP32-C6 and ESP32-H2, ESP32-C3 and ESP32-C2, and WASI. That is a compile result only; firmware supplies the radio, storage, entropy, and clock.+ - Transports on phones: Bluetooth LE on iOS and Android. The peer stream is WiFi Direct on Android only; since 0.28.0, Android 10 and later can form the WiFi Direct group with no system dialog (autoAccept). On iOS the peer stream runs on the Network framework over the local network or AWDL, not MultipeerConnectivity; an iPhone on 0.28 does not see one on 0.27 or earlier over that path.+ ## Cost answers+ From https://www.offlineprotocol.com/pricing.+ - Is it free? The mesh SDK is free under AGPL-3.0-only, including in production when the AGPL obligations are met. Local mesh traffic between devices is never metered, on any plan.+ - Closed-source and App Store apps need the commercial license, because they cannot meet the AGPL obligations. It is annual with no published price: contact us for pricing (https://www.offlineprotocol.com/contact).+ - Hosted services are optional. Plans: Free $0 with no card required, Pro $99 a month, Scale $499 a month, Enterprise annual. Included each month on Free, Pro, and Scale: 1,000, 10,000, and 50,000 OfflineID monthly active users; 10,000, 100,000, and 1 million hosted relay deliveries; 250,000, 2 million, and 10 million telemetry events; 250, 2,500, and 10,000 Proof of Location verifications.+ - Overage: $0.02 per additional monthly active user, $0.50 per 1,000 hosted relay deliveries, $0.05 per 1,000 telemetry events, $0.03 per location verification, billed monthly in arrears. A billing limit can be set on any meter.+ - At a quota: with a card on file, service continues and overage is billed. On Free without a card, the first meter to reach its quota pauses all of the organization's metered hosted services (OfflineID sign-ins, hosted relay deliveries, telemetry ingest, Proof of Location verifications) until a card or paid plan is added, or the next billing period starts.+ - What counts as a monthly active user: A monthly active user (MAU) is a unique end user who signs in to any app in your organization at least once in a calendar month (UTC). Each person counts once per month per organization, however many apps, devices or sessions they use, and a guest counts once per install. The hosted relay accepts only signed-in OfflineID accounts, not guests, so relay users are counted through their OfflineID sign-ins. Local mesh traffic between devices is never metered.+ - Startup and nonprofit discounts: yes, contact us.+ - [Proof of Location](https://www.offlineprotocol.com/technology/proof-of-location): Witness-attested location evidence on Ethereum Sepolia testnet. Operators time a network round trip and sign EIP-191 attestations; a coarse geohash cell and time are public. Not a zero-knowledge proof or proof of presence.+ - [Embedded and OEM platforms](https://www.offlineprotocol.com/embedded): A no_std Rust leaf profile that speaks real MLS on a Cortex-M33 class part in 449.5 KiB, beside the radio stack you already ship. Since 0.28.0, CI also gates its compile for Cortex-M0, ESP32 RISC-V parts, and WASI.+ - [Mesh SDK on PyPI](https://pypi.org/project/offline-protocol-sdk/): The Python package.+ - [Swift package](https://github.com/Offline-Protocol/offline-protocol-swift): The early native Swift package for iOS.+ - [GitHub releases](https://github.com/Offline-Protocol/offline-protocol-sdk/releases): Release notes and downloads, including the Android library and desktop native libraries.+ ## How-to by task+ Step-by-step guides in the developer documentation.+ - [Two-phone quickstart](https://www.offlineprotocol.com/docs/getting-started/quickstart): Run two physical phones and exchange an encrypted message over Bluetooth LE with no account or API key.+ - [Local handoff](https://www.offlineprotocol.com/docs/guides/local-handoff): Hand an update from one nearby device to another, persist it locally, and track the receiving app's explicit acceptance.+ - [Shared state](https://www.offlineprotocol.com/docs/guides/shared-state): Sync checklists, notes, counters, and settings between devices with replicated documents, then merge when peers reconnect.+ - [Backend delivery](https://www.offlineprotocol.com/docs/guides/backend-delivery): Retain readings and events while offline, deliver them to your existing backend through an adapter, and reconcile acceptance.+ - [Nearby service](https://www.offlineprotocol.com/docs/guides/nearby-service): Advertise a capability, discover an approved provider on nearby devices, and handle request and response over the mesh.+ - [OfflineID SDK](https://www.offlineprotocol.com/docs/id-sdk/overview): Hosted email sign-in, profiles, and connections; setup for [React Native](https://www.offlineprotocol.com/docs/id-sdk/setup-rn) and [React](https://www.offlineprotocol.com/docs/id-sdk/setup-react).+ - [Licensing and plans](https://www.offlineprotocol.com/docs/operations/licensing): AGPL-3.0 or commercial licensing, App Store distribution, hosted plans, quotas, and pauses.+ - [Python](https://www.offlineprotocol.com/docs/mesh-sdk/python): Install the Python binding from PyPI and run a full peer on a Linux or desktop gateway over local IP.+ - [Embedded and Rust](https://www.offlineprotocol.com/docs/mesh-sdk/embedded): A full Rust peer or the constrained offline-protocol-leaf firmware component, with your transport and storage.+ - [Proof of Location](https://www.offlineprotocol.com/docs/proof-of-location/submit-pol): Submit a location claim and verify each operator's attestation; see the [overview](https://www.offlineprotocol.com/docs/proof-of-location/intro) for testnet and trust limits.+ - [Compare overview](https://www.offlineprotocol.com/compare): Offline Protocol against Ditto, Bridgefy, Meshtastic, goTenna, Berty, Briar, Bitchat, Amazon Sidewalk, Google Nearby Connections, and offline sync alternatives.+ - [Offline Protocol vs Google Nearby Connections](https://www.offlineprotocol.com/compare/nearby-connections): A routed multi-hop mesh SDK versus Google's Android-first direct-link API, which is limited to Wi-Fi LAN on iOS.+ - [Offline Protocol vs Bitchat](https://www.offlineprotocol.com/compare/bitchat): A Bluetooth mesh messaging app versus a mesh SDK for building an app like it.