# 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.31.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, a Java package on Maven Central for the JVM, a Ruby gem on RubyGems, a C API for any language that calls C, early native Swift and Android packages, a preview Flutter plugin with the React Native module's native surface, an experimental browser build that runs a full node in a Web Worker, and thirteen 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, an HTTP front that lets programs that do not use the SDK call services on other devices with plain HTTP, opt-in telemetry the SDK uploads itself, and a no_std leaf profile for constrained devices. The Offline Protocol CLI (0.2.9) 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.31.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.9 (the `offline` command and local MCP server).
- Mesh SDK installs, all v0.31.0 (2026-10-27):
  - 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. It starts every transport its config enables (peer streams on TCP 7878, `--lan` DNS-SD discovery, Bluetooth LE central and peripheral through BlueZ on Linux, the internet relay with `--relay`). `pip install "offline-protocol-sdk[lan,http]"` adds LAN discovery, the HTTP front (`--http 127.0.0.1:8080`, or `offline-protocol-http-front`), and `offline-protocol-verify`, a command that drives the service and reports what it proved.
  - HTTP front: `PUT /services/<name>` with `{"callback": "http://127.0.0.1:9000"}` registers a local HTTP endpoint; a request to `<service>.<device address>.offline.protocol.internal` on another box reaches it inside an end-to-end encrypted message, and the callback sees the caller's authenticated address in `X-Offline-Protocol-Sender`. Bodies up to 128 KiB, 30 s default deadline. The front does not authorize: the provider decides who it serves. Spec: https://github.com/Offline-Protocol/offline-protocol-sdk/blob/main/docs/spec/http-front.md
  - Container: `bindings/python/docker` in the SDK repository builds one service per host from PyPI (`python:3.12-slim`, configured by environment variables), with a two-box HTTP demo in `examples/http-front`. The image is published as `ghcr.io/offline-protocol/offline-protocol-service` (tags `0.31.0`, `0.31`, `latest`; linux/amd64 and linux/arm64), with build provenance, an SBOM and a GitHub attestation: `docker pull ghcr.io/offline-protocol/offline-protocol-service:0.31.0`.
  - Rust: `cargo add offline-protocol` (thirteen offline-protocol crates on crates.io, including `offline-protocol-web` for the browser, Rust 1.87+; building the native library for the other bindings from source needs Rust 1.91). Built-in file stores sealed under a store key serve hosts with no platform keystore.
  - Java: `com.offlineprotocol:offline-protocol-java` 0.31.0 on Maven Central, a typed Java API for the JVM on desktop and server, generated from the same interface definition as the other bindings. JDK 22 or later, run with `--enable-native-access=ALL-UNNAMED`. The jar holds no native code: take the native library for your platform from the desktop archives on the GitHub release. On Android, use the Android library instead.
  - C: `offline_protocol.h` and the native library, in each desktop archive on the GitHub release (Linux x86_64 and aarch64, macOS arm64, and Windows x86_64 with the DLL's import library). Create an engine from a JSON configuration, call any method by its local API name with JSON parameters, and receive events as JSON, from C, C++, Go through cgo, C# through P/Invoke, or Zig. The iOS XCFramework carries the same C functions; the Android libraries do not. Guide: https://github.com/Offline-Protocol/offline-protocol-sdk/blob/main/bindings/c/README.md
  - Ruby: `gem install offline_protocol` (0.31.0 on RubyGems), a typed Ruby API for scripts, tooling, and servers, generated from the same interface definition as the other bindings and calling the native library through the `ffi` gem. Ruby 3.3 or later. The gem holds no native code: take the native library for your platform from the desktop archives on the GitHub release. Guide: https://github.com/Offline-Protocol/offline-protocol-sdk/blob/main/bindings/ruby/README.md
  - Browser (experimental): the engine, MLS included, runs as a full node in a dedicated Web Worker, with durable storage in sealed origin-private (OPFS) files, WebRTC links between devices set up from two codes with no server, a nearby room where browsers on one network find each other, the Nostr transport over the application's own relays, and, in Chromium, a Web Bluetooth link to a phone or a board running the SDK. The `offline-protocol-web` crate is on crates.io; the JavaScript in `bindings/web` is built from the SDK repository and is not on npm. Needs a secure context (HTTPS or localhost); its pages are tested in Chromium, Firefox, and WebKit. Contract: https://github.com/Offline-Protocol/offline-protocol-sdk/blob/main/docs/bridges/web.md
  - Flutter (preview): the `offline_protocol` plugin in the SDK repository (`bindings/flutter/offline_protocol`), added as a path dependency; it is not on pub.dev yet. Flutter 3.10+, iOS 13+, Android API 24+, and a one-time build of the mobile native libraries from source. Since 0.31.0 its `MeshSdk` gives Dart the React Native module's native surface: Bluetooth LE, WiFi Direct, internet, Nostr, and Reticulum transports, telemetry, and on Android the same mesh foreground service.
  - Swift (early): Swift Package Manager, `https://github.com/Offline-Protocol/offline-protocol-swift.git` from 0.31.0, product OfflineProtocolSDK. iOS 13+, iOS only, Swift 5.10 (Xcode 15.3) or newer. 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): on Maven Central as com.offlineprotocol:offline-protocol-sdk 0.31.0 (Android 7+, API 24): the Kotlin bindings, native libraries for four ABIs, and the Android transport and storage classes, which the app wires to the engine. The same bindings and libraries are also on the GitHub release as offline-protocol-0.31.0-android.zip. 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, with the C header.
  - Embedded: `offline-protocol-leaf` (no_std) lets firmware join a phone's MLS group as a peer. CI builds it for Cortex-M33, Cortex-M0, ESP32-C6 and ESP32-H2, ESP32-C3 and ESP32-C2, and WASI; the firmware supplies the radio, storage, entropy, and clock.
  - ESP32 hardware: the IntelligenceMesh Relay (https://shop.offlineprotocol.com/products/intelligencemesh-dual-protocol-mesh-node), an ESP32-PICO-V3-02 node pre-flashed with Offline Protocol firmware, relays encrypted Offline Protocol mesh traffic (and Bitchat) over Bluetooth LE.
- Transports on phones: Bluetooth LE on iOS and Android, with no Bluetooth pairing step. The peer stream uses 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. Since 0.29.0 the Android peer stream also joins the Wi-Fi network it is on (DNS-SD `_offlineprotocol._tcp`), so Android phones, iPhones, and Python hosts on one network find each other; networks that block multicast or isolate clients find nothing.
- Sessions and service calls (0.29.0): two devices that have never met start an encrypted session through a third, which carries frames it cannot read. Service request and response bodies are sealed in the MLS session once the recipient runs 0.29 and the session is confirmed; discovery, and the first request to a provider never met, are signed and readable by the devices that carry them.
- Files: `send_file` (`sendFile` in React Native) takes the file's bytes. Since 0.30.0, `send_file_from_path` (`sendFileFromPath` in React Native) takes a path or `file://` URI and the Rust core reads the file itself, so a large file never crosses the React Native bridge as base64. Up to 100 MiB per file; the file is read whole, not streamed.
- Telemetry security (0.30.0): the telemetry uploader trusts only the sixteen roots of the four certificate authorities the ingest's certificate can come from. From 0.26.0 to 0.29.0 it trusted the bundled Mozilla root set, which still included the eMudhra root withdrawn after the October 2026 key compromise. Apps that call enableTelemetry on 0.26.0 to 0.29.0 should update to 0.30.0.
- Library size (0.30.0): link-time optimisation now reaches the libraries a release ships, and the iOS and Android libraries are built for size. Measured on the macOS arm64 build, the static library the iOS framework is built from went from 138 MB to 23 MB, and the shared library from 10.9 MB to 8.5 MB. The npm package went from 466.4 MB to 100.7 MB unpacked, 0.29.0 to 0.30.0, as npm reports it.
- Sessions and signal strength (0.31.0): with Nostr on, a send or `establish_secure_session` to a device with no session asks the application's relays for the key packages it published, so two devices that share only a relay form a session on iOS, Android, Flutter, and the browser. A 1:1 pair split into two sessions, or left without one by a lost reset, now heals (both devices on 0.31.0). An iPhone serves the Bluetooth LE Hello characteristic, so it names a central it cannot dial back, such as a browser. A `peer_rssi` event reports a linked peer's live Bluetooth LE signal strength while the app listens. Behaviour changes: https://github.com/Offline-Protocol/offline-protocol-sdk/blob/main/docs/UPGRADING.md
- Reported test results for 0.29.0 (not guarantees): two Raspberry Pi 4s joined only through a laptop over USB networking, with no route between them, plus an Android phone over Bluetooth LE. An HTTP call through the middle box answered in 5.2 s; an HTTP call between the two Pis over Bluetooth LE alone passed; store and forward, a restarted sender, delivery through the middle box, and delivery while the sender was off all passed; a four-member group across the three computers and the phone delivered 12 of 12 messages.
- 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.9 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.
- [Demos](https://www.offlineprotocol.com/demos): Native demo apps (open-source React Native apps that sync over Bluetooth between phones nearby: Order Up, Stock Sync, Cowrite, Tic Tac Together, OutageNet, YardGate, Event Floor, AgriMesh, ChargeCatch) and what developers have built on the SDK (Radius, an Obsidian folder-sharing plugin, a shielded Zcash payment, hopchat, Heimdall, MeshWallet and more).
- [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): Eleven open-source (MIT-0) React Native apps built on @offline-protocol/mesh-sdk 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), Cowrite (a shared document with live cursors), OutageNet (outage coordination), YardGate (logistics yard check-in), Event Floor (event staff dispatch and gate admission), AgriMesh (field readings over a multi-hop mesh), ChargeCatch (EV charge-site sessions), SurfrRoll (incident alerts and staff roll call), and DockHand (fleet-yard dock assignment).
- [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.
- [Offline Protocol vs Matter](https://www.offlineprotocol.com/compare/matter): Matter standardises certified smart home device control across brands; Offline Protocol coordinates the apps, gateways, and agents around those devices. Where Matter wins, and how the two work side by side.
- [Matter alternatives](https://www.offlineprotocol.com/compare/matter-alternatives): Thread, Zigbee, Bluetooth Mesh, ESP-NOW, MQTT brokers, AWS IoT Greengrass, Azure IoT Edge, Ditto, and Offline Protocol compared with Matter by the layer each covers.
- [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 vs Zigbee](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.
- [SDKs and platforms](https://www.offlineprotocol.com/learning/sdks): Language bindings (React Native and TypeScript, Python, Rust, Swift, Kotlin, Java, C, Flutter, Ruby, browser), supported platforms and chips, the CLI, and the MCP server for Claude, Cursor, VS Code and ChatGPT.
- [AI and network security](https://www.offlineprotocol.com/learning/ai-security): Attack surface, AI agents, leaked API keys, worms, air gaps and why one narrow gateway shrinks what an attacker can reach.
- [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.
- [How can a program call an HTTP service on another device with no internet?](https://www.offlineprotocol.com/learning/mesh-networking/how-to-call-an-http-service-on-another-device-without-internet): Routes and overlays versus carrying HTTP requests as messages across a mesh, and what changes for timeouts, body size and caller identity.
- [Does Matter work without internet?](https://www.offlineprotocol.com/learning/embedded/does-matter-work-without-internet): What keeps working on the local network during an outage, and what needs a hub, a border router, or the cloud.
- [What is a Matter fabric, and how does multi-admin work?](https://www.offlineprotocol.com/learning/embedded/what-is-a-matter-fabric): Fabrics, operational certificates, sharing a device with a second ecosystem, and fabric limits.
- [Matter vs Thread](https://www.offlineprotocol.com/learning/embedded/matter-vs-thread): The application standard and the low-power IPv6 mesh it often runs on.
- [Thread vs Zigbee](https://www.offlineprotocol.com/learning/embedded/thread-vs-zigbee): Two IEEE 802.15.4 meshes compared on IP, hubs, phones, scale, and security.
- [Zigbee vs Bluetooth Mesh](https://www.offlineprotocol.com/learning/embedded/zigbee-vs-bluetooth-mesh): Two lighting and building meshes compared on controllers, phones, security, and cost.
- [Matter vs Zigbee vs Z-Wave vs Thread, which should you use?](https://www.offlineprotocol.com/learning/embedded/matter-vs-zigbee-vs-z-wave-vs-thread): The four smart home standards compared by layer, radio, range, hubs, phones and cost.
- [What is a Thread border router, and do you need one?](https://www.offlineprotocol.com/learning/embedded/what-is-a-thread-border-router): What a border router does, when you need one, how to find yours, and why several help.
- [How does Matter commissioning work?](https://www.offlineprotocol.com/learning/embedded/how-does-matter-commissioning-work): The steps behind scanning a Matter QR code, from Bluetooth LE to certificates, and how to fix failed setups.
- [Can a smart home run without the cloud?](https://www.offlineprotocol.com/learning/embedded/can-a-smart-home-run-without-the-cloud): What keeps working with no internet, what still calls the cloud, and how to check a device before buying.
- [BLE vs Wi-Fi Direct vs Wi-Fi Aware: which should two devices use?](https://www.offlineprotocol.com/learning/resilience/ble-vs-wi-fi-direct-vs-wi-fi-aware): The direct links compared on speed, range, platforms, battery and background rules.
- [Can a Bluetooth LE app run in the background on Android?](https://www.offlineprotocol.com/learning/bluetooth-le/can-a-ble-app-run-in-the-background-on-android): Foreground services, PendingIntent scans, the Companion Device Manager, and wearable sync.
- [ESP32 mesh options compared: ESP-WIFI-MESH, ESP-BLE-MESH, ESP-NOW, painlessMesh and more](https://www.offlineprotocol.com/learning/embedded/esp32-mesh-network-options): Wi-Fi, Bluetooth LE, ESP-NOW, Thread, Zigbee and LoRa meshes on ESP32, judged on the same terms.
- [Meshtastic vs MeshCore vs Reticulum: which off-grid mesh should you use?](https://www.offlineprotocol.com/learning/embedded/meshtastic-vs-meshcore-vs-reticulum): Three off-grid meshes compared on routing, hardware, privacy, licence and maturity.
- [How does Wi-Fi provisioning over Bluetooth LE work?](https://www.offlineprotocol.com/learning/embedded/how-does-wi-fi-provisioning-over-ble-work): How a phone hands a new device its Wi-Fi credentials over Bluetooth LE, and how Improv, ESP-IDF and Matter do it.
- [Can AI agents control smart home and IoT devices locally?](https://www.offlineprotocol.com/learning/industry/can-ai-agents-control-devices-locally): Cloud APIs, local hubs, MCP servers and local models, and how to keep an agent safe around devices.
- [AWS IoT Greengrass vs Azure IoT Edge](https://www.offlineprotocol.com/learning/edge-data/aws-iot-greengrass-vs-azure-iot-edge): Two edge runtimes compared on footprint, offline operation, local messaging, and pricing.
- [Ditto vs Couchbase Lite](https://www.offlineprotocol.com/learning/offline-first/ditto-vs-couchbase-lite): Two embedded databases with peer-to-peer sync compared on transports, conflicts, platforms, and licensing.
- [Best offline-first sync SDKs for mobile apps](https://www.offlineprotocol.com/learning/offline-first/best-offline-first-sync-sdks-for-mobile-apps): PowerSync, Firebase, Couchbase Lite, Ditto, RxDB, and Offline Protocol by the job each does.
- [How do devices coordinate locally beyond the smart home?](https://www.offlineprotocol.com/learning/industry/how-do-devices-coordinate-locally-beyond-the-smart-home): What work sites need beyond device control, and the building blocks teams use.
- [Wi-Fi vs private 5G vs a device mesh for industrial sites](https://www.offlineprotocol.com/learning/industry/wi-fi-vs-private-5g-vs-device-mesh-for-industrial-sites): What dead zones cost per shift, when more Wi-Fi is enough, when private LTE or 5G pays off, and where a device mesh helps on top.
- [What is a Matter bridge?](https://www.offlineprotocol.com/learning/embedded/what-is-a-matter-bridge): How Zigbee, Z-Wave and other non-Matter devices join Matter apps, and how a bridge differs from a hub, controller or border router.
- [Matter over Wi-Fi vs Matter over Thread](https://www.offlineprotocol.com/learning/embedded/matter-over-wi-fi-vs-matter-over-thread): The same Matter devices on two networks, compared on hubs, speed, battery, reliability and network settings.
- [What is Z-Wave?](https://www.offlineprotocol.com/learning/embedded/what-is-z-wave): The sub-GHz smart home mesh: regional frequencies, Long Range, S2 security, hubs, and Matter through bridges.
- [How do you build a Matter controller app?](https://www.offlineprotocol.com/learning/embedded/how-to-build-a-matter-controller-app): Ecosystem APIs or your own fabric, on Android, iOS, Python, JavaScript and ESP32.
- [How does a BLE to MQTT gateway get sensor data to a broker?](https://www.offlineprotocol.com/learning/edge-data/ble-to-mqtt-gateway): Scanning or connecting to BLE sensors, the main gateway options, topic design, and buffering while the broker is away.
- [How do offline payments work?](https://www.offlineprotocol.com/learning/offline-auth/how-do-offline-payments-work): EMV offline approval, POS store and forward, UPI Lite and the proposed offline digital euro, and how each limits double spending.
- [How is a mobile driver's license verified offline?](https://www.offlineprotocol.com/learning/offline-auth/how-is-a-mobile-drivers-license-verified-offline): ISO/IEC 18013-5 device engagement and retrieval, issuer and device signatures, selective disclosure, and what an offline reader cannot know.
- [How do you send a file between two phones without internet?](https://www.offlineprotocol.com/learning/resilience/how-to-send-a-file-between-two-phones-without-internet): AirDrop, Quick Share and its AirDrop support, why iPhone Bluetooth will not send files, and how apps move files phone to phone.
- [Can AI hack my website?](https://www.offlineprotocol.com/learning/ai-security/can-ai-hack-my-website): What AI attackers look for, and the fixes that close the doors they try.
- [Are AI agents a security risk for businesses?](https://www.offlineprotocol.com/learning/ai-security/are-ai-agents-a-security-risk-for-businesses): What can go wrong when software reads, decides and acts on its own.
- [How do I protect my company from AI agents?](https://www.offlineprotocol.com/learning/ai-security/how-do-i-protect-my-company-from-ai-agents): A plan for the agents attacking you and the agents working for you.
- [What is attack surface?](https://www.offlineprotocol.com/learning/ai-security/what-is-attack-surface): Every door an attacker can try, and why fewer doors beat stronger locks.
- [What is an antifragile internet?](https://www.offlineprotocol.com/learning/ai-security/what-is-an-antifragile-internet): Many small local networks with narrow doors, instead of one giant shared target.
- [What is an air gap, and is a local network the same thing?](https://www.offlineprotocol.com/learning/ai-security/what-is-an-air-gap): The strictest boundary there is, and the airlock that keeps most of its protection.
- [How do I protect my account from AI attacks?](https://www.offlineprotocol.com/learning/ai-security/how-do-i-protect-my-account-from-ai): Passkeys, unique passwords and a call-back habit beat convincing fakes.
- [What happens when an API key leaks?](https://www.offlineprotocol.com/learning/ai-security/what-happens-when-an-api-key-leaks): Revoke first, then rotate, check the logs, and need fewer long-lived keys.
- [Device-issued identity vs API keys: which is safer?](https://www.offlineprotocol.com/learning/ai-security/device-issued-identity-vs-api-keys): A secret anyone can copy versus a key that never leaves the device.
- [How does a single gateway reduce attack surface?](https://www.offlineprotocol.com/learning/ai-security/how-does-a-single-gateway-reduce-attack-surface): One door to the internet instead of one per device, and how to build it.
- [Can an AI worm spread across a local network?](https://www.offlineprotocol.com/learning/ai-security/can-a-worm-spread-across-a-local-network): How worms find their next target, and why a narrow gateway works like an airlock.
- [Is on-device AI more private than cloud AI?](https://www.offlineprotocol.com/learning/ai-security/is-on-device-ai-more-private-than-cloud-ai): Data that never leaves the device has no server copy to leak.

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

- [SDK 0.31: a browser runs a full Offline Protocol node](https://www.offlineprotocol.com/blog/sdk-0-31-the-browser-as-a-full-node) (2026-10-27): The engine and MLS in a browser worker with durable OPFS storage, WebRTC between browsers, nearby rooms on one network, the Nostr transport over the application's relays, and Web Bluetooth to a phone or a board.
- [SDK 0.31: a Ruby gem, Flutter parity, live BLE signal and sessions that heal](https://www.offlineprotocol.com/blog/sdk-0-31-ruby-flutter-and-sessions-that-heal) (2026-10-27): The offline_protocol gem on RubyGems, Flutter's MeshSdk with the React Native native surface, a peer_rssi event, cold contact over Nostr relays and self-healing MLS sessions.
- [Local coordination: protecting connected devices with one internet gateway](https://www.offlineprotocol.com/blog/local-coordination-one-internet-gateway) (2026-10-22): Why devices at a site should share one encrypted local network and one gateway to the internet: fewer entry points for AI-driven attacks, lower backhaul costs and sites that keep working through outages. By Satvik Sethi.
- [hopchat: smart home control with a shared local model and a peer-to-peer terminal chat](https://www.offlineprotocol.com/blog/hopchat-peer-to-peer-terminal-chat-in-rust) (2026-10-22): An open-source Rust terminal chat on the Offline Protocol SDK: serverless discovery, MLS chat, file handover, Wiz and LG TV control, and one shared local model. By Gokul Santhosh.
- [SDK 0.30: smaller libraries, C, Java and Flutter bindings, and a telemetry security fix](https://www.offlineprotocol.com/blog/sdk-0-30-smaller-libraries-c-java-and-flutter) (2026-10-21): The iOS static library drops from 138 MB to 23 MB, C, Java and Flutter bindings, narrower telemetry trust roots and Bluetooth LE fixes under load.
- [SDK 0.29: call a service on another device with one HTTP request](https://www.offlineprotocol.com/blog/sdk-0-29-call-a-service-over-http) (2026-10-13): An HTTP front for the Python service, end-to-end sealed service calls, a Dockerfile and a two-box demo.
- [SDK 0.29 on a box: every carrier on, sessions through a middle box, and a way to prove it](https://www.offlineprotocol.com/blog/sdk-0-29-every-carrier-on-a-box) (2026-10-13): Every configured transport starts at once, encrypted sessions between devices that only meet through a third, and offline-protocol-verify.
- [SDK 0.29 on phones: Android meets iPhone on Wi-Fi, and phones reach a box over Bluetooth LE](https://www.offlineprotocol.com/blog/sdk-0-29-phones-on-wi-fi-and-bluetooth) (2026-10-13): Android finds iPhones and Python hosts on shared Wi-Fi, phones open sessions with Linux or Mac boxes over Bluetooth LE, and Android BLE link fixes.
- [SDK 0.28 on servers and desktops: Python on PyPI and a local API](https://www.offlineprotocol.com/blog/sdk-0-28-servers-and-desktops) (2026-10-06): Python wheels on PyPI, a local API so several programs share one node, sealed stores on hosts with no keychain, and held document frames for absent peers.
- [SDK 0.28 on iOS and Android without React Native](https://www.offlineprotocol.com/blog/sdk-0-28-native-ios-and-android) (2026-10-06): Packaged bridge code for native apps, Network framework peer streams on iOS, Android-owned Wi-Fi Direct groups and Bluetooth LE fixes.
- [SDK 0.28: the leaf node compiles for ESP32 RISC-V, Cortex-M0 and WASI](https://www.offlineprotocol.com/blog/sdk-0-28-leaf-builds-for-esp32-and-cortex-m0) (2026-10-06): The firmware crate that holds an MLS session with a phone now builds for ESP32 RISC-V, every Cortex-M0 and WASI, gated in CI.
- [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.