Community
Install the public React Native SDK and build a working prototype under the AGPL community license.
- Current SDK from npm
- iOS and Android
- Documentation and developer guides
- AGPL terms apply
Start building free. License when you ship.
Evaluate Offline Protocol under the AGPL community license, move to a commercial license for proprietary production use, or run a supported pilot against your real fleet and conditions.
Commercial
Ship Offline Protocol inside proprietary or commercial software with licensing sized to your deployment.
- Commercial SDK license
- Production deployment rights
- Integration support available
- Pricing based on deployment
Pilot
Run a supported 6 to 10 week evaluation against your devices, conditions, and agreed success criteria.
- Scoped technical evaluation
- Hands-on integration support
- Telemetry and results review
- Production plan if criteria are met
How production licensing works
Four capabilities, each priced on the axis that fits how you use it. Mix what your deployment needs. You are not buying a fixed bundle.
Mesh SDK
Commercial licenseA commercial license to ship the SDK — transport (DORS), service discovery, and file transfer — in your production app, sized to your deployment.
How it works →Service Discovery
Per devicePriced per device that advertises or invokes capabilities across the mesh. Scales with your fleet, not with call volume.
How it works →OfflineID
Per verificationPriced by verification volume: the offline identity checks your app performs. You pay in proportion to the trust decisions you make.
How it works →Telemetry
Per observability clusterPriced per observability cluster you stream mesh telemetry into. Add clusters as you scale fleet observability, not per event.
How it works →Not sure which you need? The pilot is the fastest way to size it. We scope the mix against your fleet before any production number.
A scoped 6 to 10 week evaluation
1
Scope
We agree the environment, the fleet, and the success criteria up front, so the pilot measures what actually matters to your deployment.
2
Integrate
You get the SDK and hands-on integration support. The protocol runs against your real devices and conditions, not a demo rig.
3
Evaluate
Over 6 to 10 weeks you measure transport, identity, and telemetry against the criteria, with our engineers alongside you.
4
License
If the pilot meets its criteria, we move to a production license sized to your deployment. No lock-in during the pilot.
What a pilot includes
The SDK
The offline-first SDK: a TypeScript API over a Rust core, the same surface on iOS and Android, with transport, identity, and service discovery in place.
Integration support
Direct engineering support to wire the protocol into your app and run it against your hardware and environment, not a ticket queue.
Telemetry evaluation
An opt-in telemetry sink so you can measure protocol events, transport-state transitions, and routing decisions on your own fleet during the pilot.
The point of the pilot is a grounded decision. You run the platform against your own hardware and environment, measure it against criteria you set, and leave with real data on how it performed. See how the mesh works to understand what you would be evaluating.
Who a pilot is for
Pilots suit teams building for the disconnected edge, where connectivity is contested, saturated, or simply absent: defense and public safety, robotics and autonomous systems, logistics, high-density venues, and critical infrastructure. If your product has to keep working when the network does not, the pilot is the shortest path from claim to proof.
The protocol already runs in production across 350,000+ devices in 80+ countries, on 10,000+ active clusters. A pilot is how you find out what that looks like on your fleet, not ours.
Developers can start with the public package today. Tell us what you are building when you need a commercial license, integration support, or a pilot measured against your fleet.
Pricing FAQ
How much does Offline Protocol cost?
Each capability is metered on the axis that tracks its value: a commercial license for the Mesh SDK, per device for Service Discovery, per verification for OfflineID, and per observability cluster for Telemetry. We do not publish fixed rates because the numbers depend on your fleet and scale, so engagements start with a scoped pilot and production is quoted against what it actually uses.
How is it metered — per device, per seat, or per call?
It depends on the capability. The SDK is a commercial license. Service Discovery is per device across your fleet. OfflineID is per verification volume. Telemetry is per observability cluster. You combine only what your deployment needs rather than buying a fixed bundle.
How do pilots work?
A pilot runs 6 to 10 weeks. We agree the success criteria up front, give you the SDK and integration support, and run the protocol against your real environment and hardware. You evaluate transport, identity, and telemetry on your own devices, and we review the results together before discussing production licensing.
Can I evaluate the SDK before a pilot?
Yes. Developers can install the Mesh SDK from npm and evaluate it under the AGPL community license. Shipping proprietary or commercial software requires a commercial license. Teams that want engineering support and measurements against their own fleet can start with a scoped pilot.
What happens after a pilot?
If the pilot meets its criteria, we move to a production license sized to your deployment. Nothing is locked in during the pilot, and you leave it with real data on how the protocol performed against your environment either way.
Who is this for?
Teams building for the disconnected edge: defense and public safety, robotics and autonomous systems, logistics, high-density venues, and critical infrastructure. If your product has to keep working when the network does not, a pilot is the fastest way to prove it.
