The transport, identity, and coordination layer for the disconnected edge

An offline mesh networking platform in three layers, all shipped, all running on 350,000+ devices across 80+ countries. One offline-first SDK surface: Rust core with a React Native binding for iOS and Android.

Book a pilot Read the docs

Three independent primitives. One application surface.

Diagram of three interoperable offline networking primitives converging on one application: DORS transport, OfflineID identity, and Service Discovery coordination. The primitives work independently and together rather than passing application data through a linear stack.

Service Discovery
Advertise, discover, and invoke capabilities across the mesh with no server or DNS.
OfflineID
Verify Ed25519 identities device-to-device, with rotation and revocation anchored on-chain.
DORS
Route over BLE, WiFi Direct, internet, Reticulum, and Nostr with real-time switching, relay, retry, and MLS encryption.
Your application Fleet coordination · agent runtimes · field apps · messaging

Figure 1. DORS, OfflineID, and Service Discovery are individually usable primitives on one SDK surface. Data does not pass through them as a fixed three-stage pipeline.

DORS

DORS, the Dynamic Offline Relay Switch, runs BLE, WiFi Direct, internet, Reticulum, and Nostr concurrently and scores each transport on live signal, congestion, energy, and reliability to pick the best. Multi-hop relay with a reliability layer of acknowledgment, retry, deduplication, and TTL built in, plus chunked file transfer. Sessions are encrypted with MLS (RFC 9420) by default. How peer-to-peer mesh networking works →

8-hoprelay TTL across the mesh
Sub-secondfailover across transports
100MBchunked file transfer with resume
Battery-awarerelay promotion on capable devices

Demonstration of transport failover on the offline mesh networking stack: a field unit whose internet link is down stays connected to a fleet dashboard over an active Bluetooth LE mesh link, with WiFi Direct on standby.

BLE · ACTIVE
WIFI DIRECT · STANDBY
INTERNET · DOWN
10:32●●● 84%
fleet-opsUNIT-07
CONNECTIVITY
InternetDOWN
Mesh5 PEERS
TRANSPORTS
ble✓ active
wifi directstandby
internetdown
SESSION
2HOPS0.8sFAILOVER0DROPS
ops.offlineprotocol.com/fleet
Fleet overviewLIVE
U-04 U-12 U-19 U-07 · LIVE
5UNITS LIVE0.8sFAILOVER3HOPS MAX

OfflineID

Ed25519-based self-sovereign identity, verifiable device-to-device with zero connectivity, anchored on-chain for rotation and revocation. Trust-on-first-use pairing. Keys never leave the device. 300,000+ issued. How offline identity verification works →

Verify anywhere. Two devices in a jammed environment authenticate each other with no lookup, no CA, no round-trip.
Rotate and revoke. On-chain anchoring gives operators a revocation path that propagates when any node touches the internet.
Sign observations. Field data is signed at capture, making records tamper-evident end to end.

Demonstration of offline identity verification: a phone holding an Ed25519 OfflineID authenticates against a gate access panel device-to-device with zero connectivity, and access is granted offline.

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✓ Revocation listsynced
ACCESS GRANTED · OFFLINE

Service Discovery

The offline internet. Devices advertise capabilities, others discover them through multi-hop routing and invoke them with a request/response pattern. No server, no DNS, no infrastructure. A device five hops away is invocable like an API endpoint. How serverless service discovery works →

This is the only discovery-and-invocation primitive in production that survives losing the internet.

1

Advertise. A device announces a capability, a sensor feed, a compute service, a data store, to its neighbors.

2

Discover. Peers up to 8 hops away learn about the capability through multi-hop routing.

3

Authenticate. Caller and provider verify each other with OfflineID, no lookup required.

4

Invoke. Request and response travel over the mesh with acknowledgment and retry, like calling an API endpoint.

Demonstration of serverless service discovery on the offline mesh: a phone discovers a thermal camera service advertised three hops away and invokes it request/response, streaming imagery with no server and no DNS.

DISCOVER → INVOKE · REQ/RES
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

Telemetry, opt-in by design

The protocol emits nothing until your app installs a sink. Then a single stream carries protocol events, MLS lifecycle, transport-state transitions, routing decisions, and device-capability changes. Read about offline telemetry →

One SDK surface

An offline-first SDK for React Native: a TypeScript API over a Rust core, same surface on iOS and Android. Start building →

IOS ANDROID REACT NATIVE RUST CORE

OfflinePay, offline-capable payments on the mesh, is in development.

Compose the platform around what your product needs

Start with one primitive or combine all three. Each capability below is part of the shipped platform surface and links to its implementation context.

Transport

Multi-transport routing

Run BLE, WiFi Direct, internet, Reticulum, and Nostr with automatic failover.

→ Transport

Multi-hop delivery

Relay ordered payloads across peers with acknowledgment, retry, and deduplication.

→ Identity

Offline authentication

Verify Ed25519 identities locally when no authority or registry is reachable.

→ Identity

Rotation and revocation

Anchor identity lifecycle on-chain and propagate updates when a node reconnects.

→ Coordination

Capability advertising

Publish what a device can do directly onto the mesh without DNS.

→ Coordination

Discover and invoke

Find a provider multi-hop and call it request/response like a local API.

→ Observability

Opt-in telemetry

Install a sink and receive protocol events in-process, push or pull, with identifiers scrubbed by default.

→ SDK

One developer surface

Use the same TypeScript API over a Rust core on iOS and Android.

→

See the platform against your fleet. Pilots run 6 to 10 weeks.

Book a pilot Read the docs