Resilient coordination for physical systems

Offline Protocol provides devices, applications, and AI agents with identity, edge sync, encrypted messaging, and nearby service calls across whichever local, mesh, gateway, or cloud path is available.

Get started Contact sales
City panorama showing industrial facilities, autonomous transport, remote energy sites, outdoor recreation, and a concert venue. City panorama showing industrial facilities, autonomous transport, remote energy sites, outdoor recreation, and a concert venue.
Tap a scene to track it

350,000+devices reached to date
60,000+SDK downloads in 2026
11,500+local networks active this month
140+countries with live devices

Keep operations functional, regardless of network conditions

Offline Protocol's edge-native solutions work alongside the company's existing systems to enable local authentication, data exchange, and communication, with automatic reconciliation with your cloud-based system of record when connectivity returns.

Build once, run on any path. The same request executes on a nearby device, across a multi-hop mesh, through a field gateway, or against a hosted provider.

Remove the single point of failure. Identity, encrypted messaging, and shared state need no server in the loop, so a lost link is a slower path, not an outage.

Reconcile, never re-enter. Local results land in the system of record when a link returns, with every retry and reroute accounted for.

One stack for transport, identity,discovery, data, and execution.

BLE, active
WiFi Direct
10:32●●● 84%
drone-ctlunit-07
Live feed
Rec Alt 120 m Live, 24 fps
59.9Speed200mRange84%Batt
Connectivity
InternetDown
Mesh5 peers
drone-07, hardware
ops.offlineprotocol.com/fleet
Fleet overviewLive
U-04 U-12 U-19 U-07, live
5Units live0Drops3Hops max
Zero connectivity
Verified, offline
10:32●●● 92%
OfflineIDunit-07
amara k. ed25519:8f3a…4c9
Key fingerprint8F3A 91C2 55E0 4C9D
Verify identity
Recent
gate-01✓ now
scout-12✓ 2m
relay-04✓ 1h
gate-01.local/access
Gate 01, North entryLocal
OfflineID check✓ Key on device✓ Signed challenge✓
Access granted, offline
Delta 212 B
No server
10:32●●● 84%
work-orderunit-07
Offline edits
statusin progress
visits+1
readings61.4 C
Connectivity
InternetDown
Meshunit-12
3Edits1Peer0Conflicts
work-order, unit-12
Merged documentConverged
statusin progress visits3 readings61.4 C assigneeunit-12
Same result on every replica
Discover, then invoke
10:32●●● 78%
Discoverunit-42
search services
NearbyServices
unit-19thermal-cam.v1 Invoke
IdentityOfflineID verified ✓Routevia relay-04, 3 hops
scout-12gps-fix.v2 Invoke
relay-04relay-uplink.v1 Connected
Mesh, 5 peers
thermal-cam.v1, stream
10:32:14 UTC Thermal, 240 ms Max 61.4°C
Advertising on meshReq 14, res 14
Dynamic Offline Relay Switch (DORS) Multi-transport, MLS encrypted routing over BLE, WiFi Direct, internet, Reticulum (Radio), and Nostr with automatic failover and multi-hop relay.
OfflineID Identity that verifies device-to-device with zero connectivity. Ed25519 keypairs that never leave the device. 330,000+ issued.
Edge sync Map, list, text, and counter documents that any member edits while disconnected and that merge deterministically when replicas meet.
Service discovery Advertise a capability, discover it across the mesh, invoke it request/response. No server, no DNS, no registry.

Customer stories

Learn how teams across industries are using Offline Protocol to keep their operations running smoothly.

Read all customer stories →

350,000+ devices reached in 140+ countries

Our infrastructure runs inside industrial and consumer apps, built by us and by third parties. It is battle-tested every day under real radio, power, and network conditions, at scale, around the world.

See the live network

Backed by

Draper Associates Galaxy AllianceDAO Portal Ventures Seed Club Ventures

Frequently asked questions

What is Offline Protocol?

Offline Protocol is the coordination layer for physical systems: it keeps applications, machines, and agents authenticated, synchronized, and operational across local, mesh, gateway, and cloud paths.

How does the mesh work?

DORS routes over BLE, WiFi Direct, internet, Reticulum, and Nostr under one contract and switches between them based on live signal, congestion, energy, and reliability. Messages relay across multiple hops with acknowledgment, retry, and deduplication built in, up to an 8-hop TTL.

What is service discovery?

Service discovery lets any device advertise a capability and any device within hop range discover, authenticate, and invoke it with a request/response pattern. No server, no DNS, no infrastructure. A device five hops away is invocable like an API endpoint.

How is data secured?

Sessions are encrypted with MLS (RFC 9420). Identities are Ed25519 keypairs whose addresses are derived from the key, so a peer proves its address by presenting the key. Keys never leave the device.

What platforms are supported?

iOS and Android through the React Native SDK, @offline-protocol/mesh-sdk on npm, with early native Swift and Android packages that need no React Native; a Python binding on PyPI for macOS, Linux, and Windows hosts; Rust crates on crates.io for gateways and full peers; and a no_std leaf profile for constrained devices. One Rust core runs under all of them. See the developers page for installs and quickstarts.

How does telemetry work?

Telemetry is off until your app turns it on with a key from the developer portal. Once on, the SDK batches what the protocol did, with no message content and no identifier fields, and uploads it to the Offline Protocol ingest itself, where the portal turns it into dashboards. The stream covers deliveries, relaying, routing decisions, transport changes, and MLS session health.

What happens during outages?

Nothing changes for the mesh. Devices keep discovering, authenticating, and invoking each other over local transports, and state syncs opportunistically when a connection returns.

How large are the files the mesh can move?

Chunked transfer supports files up to 100MB across the mesh, with per-chunk acknowledgment and resume.

How do we evaluate this?

We run scoped evaluations of 4 to 16 weeks against your fleet, environment, and success criteria. Use the contact form to book one.

How do developers get started?

Install @offline-protocol/mesh-sdk from npm and sign up free at dev.offlineprotocol.com for API keys, hosted services, and analytics. The docs quickstart pairs two phones over the mesh, and the Offline Protocol CLI and MCP server give coding agents the same context.

How is Offline Protocol priced?

The mesh SDK is free under AGPL-3.0-only, the OfflineID and Proof of Location client packages are MIT or ISC, and local mesh traffic is never metered. Hosted services run on Free, Pro at $99 a month, Scale at $499 a month, and Enterprise on an annual agreement, each with included usage and published overage rates. A commercial license for the mesh SDK covers proprietary and App Store distribution.

The cloud is your system of record. Offline Protocol can become your system of local execution.

Scope an evaluation Start building