# 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. 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-transport routing over Bluetooth LE, WiFi Direct, internet, Reticulum, and Nostr with automatic failover and relay up to 8 hops, self-certifying Ed25519 identity with OfflineID account binding, MLS (RFC 9420) encryption on by default, serverless service discovery and invocation, edge sync (replicated CRDT documents), restart-safe delivery, opt-in custody of replication frames for peers that are away, a local API that lets one engine serve several applications on a host, opt-in telemetry the SDK uploads itself, and a no_std leaf profile for constrained devices. The Offline Protocol CLI (0.2.6) and MCP server connect coding agents to the SDK. Deployed across 350,000+ cumulative device instances in 140+ countries.

## Key facts

- 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.
- 440,000+ location proofs received in the last 30 days (to 2026-09-30).
- Hosted services: OfflineID accounts, the hosted relay, hosted telemetry, Proof of Location verification, and the hosted MCP server at https://mcp.offlineprotocol.com/mcp. Local mesh traffic is never metered.
- Plans: Free ($0), Pro ($99 a month), Scale ($499 a month), and Enterprise (annual agreement), each with a monthly quota of OfflineID monthly active users, relay deliveries, telemetry events, and location verifications, and published overage rates. Details: https://www.offlineprotocol.com/pricing
- Licensing: the mesh SDK is free under AGPL-3.0-only, including in production when the AGPL obligations are met. A commercial license covers proprietary apps, closed firmware, App Store distribution, OEM, and redistribution (legal@offlineprotocol.com). OfflineID and Proof of Location client packages are MIT or ISC; the CLI is Apache-2.0.
- Start building: developer portal https://dev.offlineprotocol.com (organizations, applications, API keys, usage, billing); docs https://www.offlineprotocol.com/docs
- Contacts: sales@offlineprotocol.com (sales), support@offlineprotocol.com (support), security@offlineprotocol.com (security), legal@offlineprotocol.com (legal and licensing).

## 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.

Full text of every page: https://www.offlineprotocol.com/llms-full.txt
Developer documentation for language models: https://www.offlineprotocol.com/docs/llms.txt (index) and https://www.offlineprotocol.com/docs/llms-full.txt (full text)

## Platform and technology

- [The platform](https://www.offlineprotocol.com/platform): Transport, identity, discovery, shared documents, and invocation across local, mesh, gateway, and cloud paths, in one SDK. The cloud stays the system of record.
- [Technology overview](https://www.offlineprotocol.com/technology): The composable primitives inside the SDK and how they interlock.
- [Mesh networking (DORS)](https://www.offlineprotocol.com/technology/mesh-networking): Peer-to-peer mesh over five transports (Bluetooth LE, WiFi Direct, internet, Reticulum, Nostr) with the Dynamic Offline Relay Switch scoring transports in real time, automatic failover, and relay up to 8 hops.
- [Offline identity (OfflineID)](https://www.offlineprotocol.com/technology/offline-identity): Ed25519 identities verified device-to-device with zero connectivity, MLS (RFC 9420) sessions, MLS-encrypted group messaging with roles, account binding through a signed challenge and an issuer-signed credential.
- [Service discovery](https://www.offlineprotocol.com/technology/service-discovery): Advertise, discover, and invoke capabilities across the mesh with no server and no DNS.
- [Edge sync](https://www.offlineprotocol.com/technology/edge-sync): Replicated documents that merge deterministically after offline edits, exchanged as compact deltas inside encrypted spaces.
- [Offline telemetry](https://www.offlineprotocol.com/technology/telemetry): Opt-in runtime observability that the SDK batches and uploads itself, covering transport, routing, delivery, and MLS records, with identifier scrubbing on by default.
- [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.
- [Security](https://www.offlineprotocol.com/security): MLS (RFC 9420) encryption, Ed25519 identity, no server in the message path, a published threat model with stated limits, and coordinated disclosure.

## Developers

- [Developers](https://www.offlineprotocol.com/developers): The Offline Protocol mesh SDK reference: install, quickstart, the API by layer, events, defaults, and requirements.
- [Developer portal](https://dev.offlineprotocol.com): Sign up or sign in, create organizations and applications, and manage API keys. The main place to start building on Offline Protocol.
- [Offline Protocol CLI](https://www.offlineprotocol.com/developers/cli): The `offline` command (@offline-protocol/cli 0.2.6 on npm): sign in to the developer portal, wire a project, add packages, plan an app, manage organizations, apps, and keys, and run the local MCP server.
- [MCP server for coding agents](https://www.offlineprotocol.com/developers/mcp): Connect Claude Code, Codex, Cursor, Gemini CLI, VS Code, or any MCP client. Local mode (`npx -y @offline-protocol/cli mcp serve`, no key, 18 tools including project scaffolding) or hosted at https://mcp.offlineprotocol.com/mcp (application API key as bearer token plus x-app-id, 15 read-only tools). Integration guidance and planning; it does not run the mesh or reach live devices.
- [CLI and MCP docs](https://www.offlineprotocol.com/docs/tools/overview): Install, login, project setup, and per-client MCP configuration.
- [Documentation](https://www.offlineprotocol.com/docs): Technical reference and API docs.
- [Developer guides](https://www.offlineprotocol.com/guides): How-to guides for the SDK.
- [Quickstart](https://www.offlineprotocol.com/guides/quickstart): Install the SDK, initialize, join the mesh, send a first message, and advertise, discover, and invoke a service.
- [Offline peer-to-peer messaging](https://www.offlineprotocol.com/guides/offline-messaging): Send and receive device-to-device with no server, encrypted by default and relayed across hops.
- [Service discovery guide](https://www.offlineprotocol.com/guides/service-discovery): Advertise a capability, discover it from another device, and invoke it request/response.
- [Verify identities offline with OfflineID](https://www.offlineprotocol.com/guides/device-to-device-auth): Authenticate peers device-to-device with no connectivity and no certificate authority.
- [Enable hosted telemetry](https://www.offlineprotocol.com/guides/offline-telemetry): One call with a portal key, a fixed event inventory with no identifiers, and batches that wait for a link.
- [Example apps](https://github.com/Offline-Protocol/offline-app-examples): Four open-source (MIT-0) React Native apps on @offline-protocol/mesh-sdk 0.27.0 that sync between phones over Bluetooth with no internet: Tic Tac Together (a two-player game), Stock Sync (shared inventory), Order Up (restaurant orders to a kitchen display), and Cowrite (a shared document with live cursors).
- [Live demo](https://www.offlineprotocol.com/sandbox): A working model of the DORS transport switch: watch it score five transports, hold, switch, and deliver, with the events your app sees.
- [Changelog](https://www.offlineprotocol.com/changelog): Every SDK release, newest first.
- [Mesh SDK on npm](https://www.npmjs.com/package/@offline-protocol/mesh-sdk): The React Native package and installation entry point.
- [Mesh SDK on crates.io](https://crates.io/crates/offline-protocol): The Rust core crate.
- [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.
- [Source on GitHub](https://github.com/Offline-Protocol): The Offline Protocol GitHub organization.
- [Offline Protocol Status](https://status.offlineprotocol.com/): Live service availability, uptime, incidents, and maintenance updates.

## 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.

## Solutions by industry

- [Solutions overview](https://www.offlineprotocol.com/solutions): One coordination layer across every environment where the network ends.
- [Robotics and autonomous systems](https://www.offlineprotocol.com/solutions/robotics): Swarm coordination that survives GPS denial and lost links.
- [AI agents and edge intelligence](https://www.offlineprotocol.com/solutions/ai-agents): Peer-to-peer agent discovery and invocation without a broker.
- [Logistics and fleets](https://www.offlineprotocol.com/solutions/logistics): Fleet communication, offline telematics, and proof of delivery in yards, ports, and dead zones.
- [Agriculture](https://www.offlineprotocol.com/solutions/agriculture): Machine and sensor connectivity across acres with no cellular coverage or SIM.
- [Industrial, energy, and maritime](https://www.offlineprotocol.com/solutions/industrial-energy): Underground mine, offshore platform, plant, and vessel coordination off-grid.
- [Humanitarian and public sector](https://www.offlineprotocol.com/solutions/public-sector): Emergency communication when cell towers are down.
- [Live events, venues, and ticketing](https://www.offlineprotocol.com/solutions/events): Connectivity at stadium and festival scale when cellular saturates, and ticket verification, gate scanning, and scan-state sync that work with no internet.

## Customer stories

- [Customer stories](https://www.offlineprotocol.com/case-studies): Workflows that kept running when the network did not, measured in scoped evaluations.
- [Fernweh](https://www.offlineprotocol.com/case-studies/fernweh): Private messaging beyond internet coverage.
- [Quick-service restaurants](https://www.offlineprotocol.com/case-studies/qsr-order-continuity): Counter, drive-thru, kitchen, and handoff on one shared order workflow through outages.
- [EV charging](https://www.offlineprotocol.com/case-studies/ev-charging): Chargers and site controllers that keep operating through cloud outages.
- [Airline catering](https://www.offlineprotocol.com/case-studies/airline-operations): A complete batch record from kitchen to ramp across coverage gaps.
- [Fleet and field service](https://www.offlineprotocol.com/case-studies/fleet-coordination): Telemetry, assignments, and completion evidence beyond cellular coverage.
- [Renewable energy](https://www.offlineprotocol.com/case-studies/renewable-energy): Wind-farm technicians across brands and backhaul gaps.
- [OEM and embedded](https://www.offlineprotocol.com/case-studies/oem-integration): A semiconductor integration of the embedded runtime, gateway software, and qualification tools.
- [Industrial inspections](https://www.offlineprotocol.com/case-studies/industrial-inspections): Inspection findings that reach the lead with no internet.

## Compare

- [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 Ditto](https://www.offlineprotocol.com/compare/ditto): A coordination layer with replicated documents, identity, and invocation versus an offline-first CRDT database.
- [Offline Protocol vs Bridgefy](https://www.offlineprotocol.com/compare/bridgefy): MLS and Ed25519 encryption versus app-level security, and a Bridgefy alternative.
- [Offline Protocol vs Meshtastic](https://www.offlineprotocol.com/compare/meshtastic): Phone-native mesh with no hardware versus LoRa radio mesh.
- [Offline Protocol vs goTenna](https://www.offlineprotocol.com/compare/gotenna): A software SDK on the phone's own radios versus dedicated mesh radios.
- [Offline Protocol vs Amazon Sidewalk](https://www.offlineprotocol.com/compare/amazon-sidewalk): A phone-native mesh SDK versus a shared gateway network.
- [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.
- [Offline Protocol vs Briar](https://www.offlineprotocol.com/compare/briar): A secure messenger in maintenance mode versus a mesh SDK for iOS and Android apps.
- [Offline Protocol vs Berty](https://www.offlineprotocol.com/compare/berty): A privacy-first messenger and Go protocol library versus a packaged mesh SDK.
- [Offline sync alternatives](https://www.offlineprotocol.com/compare/offline-sync-alternatives): After Atlas Device Sync, how Couchbase Lite, PowerSync, and device-to-device replicated documents compare.
- [Best offline mesh networking SDKs](https://www.offlineprotocol.com/compare/best-offline-mesh-networking-sdks): A side-by-side of Offline Protocol and the alternatives.

## Glossary

- [Glossary](https://www.offlineprotocol.com/glossary): Definitions of offline, mesh, and identity terms.
- [What is offline mesh networking?](https://www.offlineprotocol.com/glossary/what-is-offline-mesh-networking)
- [Offline-first architecture](https://www.offlineprotocol.com/glossary/offline-first-architecture)
- [Peer-to-peer network](https://www.offlineprotocol.com/glossary/peer-to-peer-network)
- [Mesh topology](https://www.offlineprotocol.com/glossary/mesh-topology)
- [Multi-hop relay](https://www.offlineprotocol.com/glossary/multi-hop-relay)
- [Store and forward](https://www.offlineprotocol.com/glossary/store-and-forward)
- [Delay-tolerant networking](https://www.offlineprotocol.com/glossary/delay-tolerant-networking)
- [Opportunistic networking](https://www.offlineprotocol.com/glossary/opportunistic-networking)
- [Service discovery](https://www.offlineprotocol.com/glossary/service-discovery)
- [CRDT](https://www.offlineprotocol.com/glossary/crdt)
- [Bluetooth LE mesh](https://www.offlineprotocol.com/glossary/bluetooth-le-mesh)
- [WiFi Direct](https://www.offlineprotocol.com/glossary/wifi-direct)
- [WiFi Aware](https://www.offlineprotocol.com/glossary/wifi-aware)
- [LoRa](https://www.offlineprotocol.com/glossary/lora)
- [Zigbee](https://www.offlineprotocol.com/glossary/zigbee)
- [NFC](https://www.offlineprotocol.com/glossary/nfc)
- [Google Nearby Connections](https://www.offlineprotocol.com/glossary/nearby-connections)
- [Amazon Sidewalk](https://www.offlineprotocol.com/glossary/amazon-sidewalk)
- [BLE mesh vs Thread vs Matter](https://www.offlineprotocol.com/glossary/ble-mesh-vs-thread-vs-matter)
- [MLS protocol (RFC 9420)](https://www.offlineprotocol.com/glossary/mls-protocol)
- [Ed25519](https://www.offlineprotocol.com/glossary/ed25519)
- [Trust on first use](https://www.offlineprotocol.com/glossary/trust-on-first-use)
- [Self-sovereign identity](https://www.offlineprotocol.com/glossary/self-sovereign-identity)
- [GPS spoofing](https://www.offlineprotocol.com/glossary/gps-spoofing)
- [Signal jamming](https://www.offlineprotocol.com/glossary/signal-jamming)
- [Local-first software](https://www.offlineprotocol.com/glossary/local-first-software)
- [mDNS and DNS-SD](https://www.offlineprotocol.com/glossary/mdns-dns-sd)
- [MultipeerConnectivity](https://www.offlineprotocol.com/glossary/multipeer-connectivity)
- [ESP-NOW](https://www.offlineprotocol.com/glossary/esp-now)
- [Reticulum](https://www.offlineprotocol.com/glossary/reticulum)
- [Nostr](https://www.offlineprotocol.com/glossary/nostr)
- [MQTT](https://www.offlineprotocol.com/glossary/mqtt)
- [Proof of location](https://www.offlineprotocol.com/glossary/proof-of-location)
- [AGPL-3.0](https://www.offlineprotocol.com/glossary/agpl)
- [Monthly active user (MAU)](https://www.offlineprotocol.com/glossary/monthly-active-user)

## Learning Center

- [Offline Protocol Learning Center](https://www.offlineprotocol.com/learning): How mesh networks, Bluetooth Low Energy, offline sync, end-to-end encryption and device identity work, with store-and-forward delivery, edge telemetry, location, embedded devices and network outages. Every article's full text is in llms-full.txt.
- [Mesh networking](https://www.offlineprotocol.com/learning/mesh-networking): Mesh topologies, routing protocols, relays, hop limits, and phone meshes.
- [Bluetooth Low Energy](https://www.offlineprotocol.com/learning/bluetooth-le): Advertising, GATT, MTU, range, battery, and platform rules on iOS and Android.
- [Offline-first and sync](https://www.offlineprotocol.com/learning/offline-first): Offline sync, conflict resolution, consistency models, and sync engines.
- [Local-first data](https://www.offlineprotocol.com/learning/local-first): CRDTs, replicated documents, on-device storage, sharing, and deletion.
- [Encryption and identity](https://www.offlineprotocol.com/learning/encryption): Public keys, signatures, MLS, forward secrecy, and metadata.
- [Offline authentication](https://www.offlineprotocol.com/learning/offline-auth): Signed credentials, challenge-response, trust on first use, and revocation.
- [Delivery and store-and-forward](https://www.offlineprotocol.com/learning/delivery): Outboxes, acknowledgments, retries, deduplication, relays, and receipts.
- [Telemetry and edge data](https://www.offlineprotocol.com/learning/edge-data): Edge telemetry, buffering, batching, MQTT, backhaul, and clock drift.
- [Location and proof of location](https://www.offlineprotocol.com/learning/location): GNSS, spoofing and jamming, indoor positioning, and proof of location.
- [Embedded and IoT](https://www.offlineprotocol.com/learning/embedded): Microcontrollers, firmware, LoRa, Thread, Matter, Zigbee, and radio rules.
- [Connectivity resilience](https://www.offlineprotocol.com/learning/resilience): Direct links, outages, failover, congestion, Reticulum, and Nostr.
- [Industry problems](https://www.offlineprotocol.com/learning/industry): Field operations, venues, machines, and evaluating offline software.
- [How to build an app like Bitchat (Bluetooth mesh + Nostr)](https://www.offlineprotocol.com/learning/mesh-networking/how-to-build-an-app-like-bitchat): A Bluetooth LE mesh with a Nostr fallback, built from scratch or with an SDK.
- [Can react-native-ble-plx connect two phones directly?](https://www.offlineprotocol.com/learning/bluetooth-le/can-react-native-ble-plx-connect-two-phones): Why ble-plx cannot do phone to phone, and what React Native apps use instead.
- [Bridgefy alternatives without per-user (MAU) fees](https://www.offlineprotocol.com/learning/mesh-networking/bridgefy-alternatives-without-mau-fees): Free and open-source options for offline phone messaging, and their real costs.
- [Which mesh networking SDKs have an MCP server?](https://www.offlineprotocol.com/learning/mesh-networking/which-mesh-networking-sdks-have-an-mcp-server): The MCP servers offline and mesh SDKs publish, and what an agent can do with each.
- [Which Python libraries do peer-to-peer and mesh networking?](https://www.offlineprotocol.com/learning/mesh-networking/python-libraries-for-peer-to-peer-mesh-networking): Reticulum, py-libp2p, Bleak and Bless, python-zeroconf, the Meshtastic API, and the Offline Protocol SDK on PyPI, by layer.

## Company

- [Company](https://www.offlineprotocol.com/company): About Offline Protocol: what we believe, the founding team, investors (Portal Ventures, Draper Associates, Galaxy, AllianceDAO, Seed Club Ventures), and independent coverage.
- [The live network](https://www.offlineprotocol.com/network): 350,000+ devices across 140+ countries, with 11,500+ local networks active this month.
- [App ecosystem](https://www.offlineprotocol.com/ecosystem): Fernweh, MINE, and IntelligenceMesh, the apps and hardware built on Offline Protocol.
- [Pricing](https://www.offlineprotocol.com/pricing): Free, Pro at $99 a month, Scale at $499 a month, and Enterprise, with published overage rates and commercial licensing.
- [Roadmap](https://www.offlineprotocol.com/roadmap): What is shipped, what is in development, and what we are exploring.
- [Careers](https://www.offlineprotocol.com/careers): Open roles.
- [Contact](https://www.offlineprotocol.com/contact): Scope a paid evaluation, talk about OEM, commercial, or enterprise licensing, or ask a developer question.
- [Blog](https://www.offlineprotocol.com/blog): Engineering deep dives and perspective from the team.
- [Blog RSS feed](https://www.offlineprotocol.com/rss.xml): Subscribe to new posts.
- [Legal](https://www.offlineprotocol.com/legal): The privacy policy, developer terms, acceptable use policy, data processing addendum, subprocessors, cookie notice, and security disclosure policy.
- [Developer terms of service](https://www.offlineprotocol.com/legal/developer-terms): The agreement for developer accounts, organizations, API keys, the CLI and hosted MCP, hosted services, plans, billing, and usage limits.
- [Privacy policy](https://www.offlineprotocol.com/privacy): What personal data Offline Protocol collects across the website, developer portal, documentation, CLI, hosted MCP, and hosted services, why, for how long, and your rights.
- [Website terms of use](https://www.offlineprotocol.com/terms): The terms for browsing offlineprotocol.com.

## Blog posts

- [MINE: coordinating the mesh through the hardware we already own](https://www.offlineprotocol.com/blog/mine-app) (2026-09-30): How MINE rewards people for turning the phones they already own into mesh nodes where coverage is thin.
- [Fernweh V2 is live](https://www.offlineprotocol.com/blog/fernweh-v2-is-live) (2026-08-31): Offline delivery, verifiable identity, private local search, and encrypted calls in one private messenger.
- [Two kinds of offline: why we added Reticulum and Nostr](https://www.offlineprotocol.com/blog/two-kinds-of-offline-reticulum-and-nostr) (2026-08-17): Long-range, infrastructure-sparse networks and a decentralized relay path over reachable internet.
- [Open sourcing the coordination layer for the disconnected edge](https://www.offlineprotocol.com/blog/open-sourcing-the-mesh-sdk) (2026-08-13): The Mesh SDK, available under AGPL-3.0 with commercial licensing.
- [Telemetry that survives the dead zone](https://www.offlineprotocol.com/blog/telemetry-that-survives-the-dead-zone) (2026-08-01): Keeping telemetry flowing when cellular and satellite links drop.
- [We built the world on a dependency nobody declared](https://www.offlineprotocol.com/blog/the-network-is-an-undeclared-dependency) (2026-07-29): Why offline-first is the act of declaring the network as a dependency.
- [Store, carry, forward: delivery when the path blinks in and out](https://www.offlineprotocol.com/blog/store-carry-forward) (2026-07-23): Custody transfer, message IDs and TTLs, deduplication, buffering, and reconcile-on-return.
- [Proving identity with no authority to ask](https://www.offlineprotocol.com/blog/proving-identity-with-no-authority) (2026-07-17): Ed25519 keys, self-certifying addresses, and session re-keying with no certificate authority.
- [Sending a message with no server](https://www.offlineprotocol.com/blog/sending-a-message-with-no-server) (2026-07-14): A message that reaches its recipient with no server in the path.
- [How DORS failover works](https://www.offlineprotocol.com/blog/how-dors-failover-works) (2026-07-09): How the transport layer scores five transports and moves traffic between them automatically.
- [The hourly cost of being offline](https://www.offlineprotocol.com/blog/the-hourly-cost-of-being-offline) (2026-07-08): Why dollars per hour, not hours, is the right unit for downtime.
- [Service discovery without a server](https://www.offlineprotocol.com/blog/service-discovery-without-a-server) (2026-06-25): Advertise, discover, and invoke capabilities with no DNS and no registry server.
- [Why the edge is disconnected](https://www.offlineprotocol.com/blog/why-the-edge-is-disconnected) (2026-06-09): Internet shutdowns, blackout losses, and the people affected.
- [From a messenger to a network](https://www.offlineprotocol.com/blog/from-a-messenger-to-a-network) (2026-05-26): How a messenger that works without internet grew into a mesh on 350,000+ devices across 140+ countries.