Works with the stack you already run
Offline Protocol is a layer, not a framework you have to build your product around. It runs on the platforms your app already targets, speaks the language your team already writes, and sits alongside the storage and tooling you already use.
Platforms, languages, and runtimes
One SDK surface across the platforms and frameworks your team already uses, all backed by the same Rust core.
iOS
The full protocol runs on iOS from the single SDK surface, no separate implementation to maintain.
Android
The same surface runs on Android, including the rugged handhelds field crews already carry.
React Native and Expo
The SDK is delivered as a React Native binding, so it drops into a React Native or Expo project directly.
TypeScript API
You build against a TypeScript API. One idiomatic surface across both platforms, fully typed.
Rust core
Every binding sits on the same Rust core, so behavior is consistent wherever the protocol runs.
IntelligenceMesh relays
Hardware relays join the same mesh as your software nodes, bridging and extending coverage.
Sits alongside what you already have
No imposed database, no all-or-nothing framework. Adopt the primitives you need and connect telemetry to the tools you already run.
Works with your existing storage
The protocol does not impose a database. It runs alongside the storage or database you already use, and you decide where records land. No migration, no lock-in.
Telemetry flushes to any sink
Opt-in telemetry emits nothing until you install a sink. Then protocol events, transport-state transitions, and routing decisions stream to the sink you connect, buffered offline and flushed in order on reconnect.
Composes with the primitives you need
Transport, identity, and coordination are independent primitives on one surface. Adopt one or combine all three, alongside the rest of your stack, without adopting an all-or-nothing framework.
Bridges mesh hardware
IntelligenceMesh hardware relays extend and bridge the mesh, connecting adjacent networks into one interoperable fabric that your software nodes join directly.
Integrations FAQ
What platforms does the SDK run on?
iOS and Android, from one SDK surface. It ships as a React Native binding over a Rust core, so the same TypeScript API runs on both platforms.
Does it force a particular database or storage layer?
No. The protocol does not impose a storage engine. It runs alongside whatever storage or database you already use, and you keep control of where data lands.
How does telemetry get into my existing tools?
Telemetry is opt-in and emits nothing until your app installs a sink. Once installed, the stream flushes protocol events, transport transitions, and routing decisions to any sink you connect, in order, when a link returns.
Can I use it with React Native and Expo?
Yes. The SDK is delivered as a React Native binding and works in a React Native or Expo project through the TypeScript API.
How does hardware fit in?
IntelligenceMesh hardware relays join the same mesh as your software nodes, bridging and extending coverage where it is needed. Devices running the Rust core interoperate directly.
