The primitives behind the disconnected edge

Last updated August 2026

Offline Protocol is a small set of composable primitives — move bytes, know who sent them, prove where they came from, and see what the mesh is doing — each shipped in the SDK and callable today. Start anywhere; they interlock.

Want to build against them? See the developer overview and the guides, or read where they run across industries.

Network and transport

How bytes move device to device with no server in the path.

Mesh networking

Multi-hop mesh with DORS transport switching and automatic failover.

Service discovery

Advertise, discover, and invoke a capability with no server or DNS.

Reliability layer

Acknowledgment, backoff retry, deduplication, and an 8-hop TTL.

File transfer

Chunked, resumable files up to 100 MB across the mesh.

Identity and trust

Knowing who you are talking to, and where they were, offline.

Offline identity

Self-sovereign Ed25519 identity, verifiable device-to-device.

Proof of location

Zero-knowledge location attestation that survives GPS denial.

Observability

Seeing what the mesh is doing, without breaking the offline model.

Offline telemetry

One opt-in stream — metrics, transport, routing, and MLS — buffered through the outage.

Start building Developer overview