Messaging
Offline peer-to-peer messaging
Device-to-device chat that relays up to 8 hops with acknowledgment, retry, and dedup, MLS-encrypted by default.
await protocol.sendMessage({ recipient, content })
Start building onOffline Protocol
Log in or sign up to build on Offline Protocol’s infrastructure stack.
What you can build on the offline stack.
One SDK install exposes transport, identity, messaging, and observability. A few things developers ship with it.
Identity
Sign users in with OfflineID
OfflineID gives your app email code sign-in, usernames, and connections between users, with one provider and a few hooks for React and React Native.
const { loginWithModal } = useAuth()
Location
Tamper-evident field capture
Proof of Location adds witness-attested location evidence, signed on the device and verifiable after it syncs.
await pol.location.verify({ claim })
Transfer
File sync over the mesh
Move files up to 100MB peer-to-peer with chunked transfer and progress events that survive a transport switching mid-send.
await protocol.sendFile({ recipient, fileData })
Agents
Build with your agent
Give your coding agent the Offline Protocol packages, integration skills, and scaffolding over MCP, so it writes against the real SDK APIs.
$ offline mcp serve
And everything to run it, in one console.
The control plane behind those calls: authenticate, create applications, issue credentials, and watch the network you deploy to.
Applications and members
Group work into applications, set allowed domains per application, and give each member a role: owner, admin, developer, billing, analyst, or read-only viewer.
Scoped API keys
Create keys per application, limit each one to OfflineID, Mesh SDK, or Proof of Location, set read or write access, and revoke a key at any time.
Application insights Live
Active devices, transport mix, delivery success, and live events from opt-in telemetry, per application.
CLI and MCP access
Authorize the CLI from the browser in one click. It uses the same applications and keys as this console, and its local MCP server gives your coding agent the SDK packages and skills.
The same account, from your terminal.
offline login authorizes through the browser with your console session and stores an API key for the application you choose. The CLI works with the same applications and keys as the console, editor to production.
Browser-callback authScoped keysLocal and hosted MCP
Terminal
# Install and log in (browser callback)
$ npm install -g @offline-protocol/cli
$ offline login
✓ Successfully logged in as [email protected]
# Scaffold a mesh app and check your setup
$ offline create nearby-chat --name field-ops --platform react-native --mesh
$ offline doctor
# Connect your coding agent to the local MCP server
$ claude mcp add offline-protocol -- offline mcp serveFive native targets, one shared core.
LinuxmacOSWindowsiOSAndroid
The same Rust core under every binding, shipped in SDK v0.28.0: React Native on npm, Python on PyPI, Rust on crates.io, and native Swift and Android packages in preview. Build, ship, and run the mesh SDK for free under AGPL-3.0-only; the OfflineID and Proof of Location client packages are MIT or ISC. Proprietary apps, closed firmware, and App Store releases use a commercial license.