What is shipped, and what is next

An honest view of the platform. Everything under shipped is in production today, on a network that has reached 350,000+ devices across 140+ countries. Everything else is where we are heading, stated plainly, with no promised dates.

Read the changelog See the platform
ShippedIn production today
Mesh SDK
OfflineID
Embedded
Developer tools
Developer platform
Apps and hardware
In developmentBeing built now
Mesh SDK
  • Swift and Android packagesEarly release
Capability Exchange
  • Capability ExchangeComing soon
Gateways
  • Reticulum reference gatewayEarly testing
ExploringUnder investigation
Mesh SDK
  • More platform bindings
Network
  • Wider mesh bridging
Ecosystem
  • Broader integrations

Shipped means published and running on real devices. We do not publish dates for anything else.

350,000+devices reached to date
140+countries with a live install
11,500+local networks active this month
50,000concurrent mesh sessions at peak

Shipped in the world

First-party apps and hardware put the protocol on hundreds of thousands of devices before the SDK was public. Every install is a relay for every other app built on it.

Three Fernweh App Store screens: connected even offline, private by design, find people nearby
FernwehMessenger

The offline messenger that grew the network. Direct and group conversations that keep working when the internet does not, end-to-end encrypted.

Learn more
Three MINE App Store screens: stay connected even offline, mine while you sleep, watch your mesh grow
MINERelay app

Turns an everyday phone into a mesh node. Every install adds a relay for every other app on the protocol. At peak, 50,000 concurrent mesh sessions.

Learn more
The IntelligenceMesh relay on a wrist beside its app answering a first-aid question with no internet
IntelligenceMeshHardware and app

A pocket-sized relay and a companion app that runs a small language model on the phone: answers with no internet, offline emergency guides, and a signed SOS that hops phone to phone.

Shop the hardware

In production today

What each shipped capability does, grouped by product. Every row opens the page that explains it.

Mesh SDKOne library for iOS, Android, desktop, and Rust

CapabilityWhat it doesAvailable
Transport switchingOne switch over Bluetooth LE, WiFi Direct, internet, Reticulum, and Nostr, with automatic failover, multi-hop relay, retry, and deduplication.Since launchEnd-to-end encryptionEvery session encrypted with MLS by default, so payloads move between authenticated peers and never in the clear.Since launchService discoveryAdvertise, discover, and invoke capabilities across the mesh with no server and no DNS in the path.Since launchEdge syncDocuments that merge deterministically after offline edits, exchanged as compact deltas inside encrypted spaces.August 2026TelemetryOpt-in telemetry the SDK collects, queues, and uploads on its own, with identifiers scrubbed and the queue sealed on disk.September 2026Restart-safe deliveryMessages waiting on a slow handshake survive an app restart, and a message that arrives twice is still one message.September 2026Python on PyPIThe Python binding installs with pip, from prebuilt wheels for macOS, Linux, and Windows hosts.October 2026HTTP frontA program that does not use the SDK calls a service on another device with one plain HTTP request, carried inside an end-to-end encrypted message by the Python service on each box.October 2026

OfflineIDIdentity that works with no connectivity

CapabilityWhat it doesAvailable
Device-owned identityA key that lives on the device, verifiable device to device with zero connectivity, bound to an account through a signed challenge and an issuer-signed credential.Since launch

EmbeddedThe protocol on microcontrollers

CapabilityWhat it doesAvailable
Embedded leaf profileA small Rust profile for constrained parts: a Cortex-M33 image under 450 KiB that joins encrypted sessions beside your radio stack.August 2026

Developer toolsThe CLI and MCP for coding agents

CapabilityWhat it doesAvailable
Offline Protocol CLIThe offline command on npm: sign in to the portal, wire a project, add packages, plan an app, and manage organizations, apps, and keys.September 2026MCP serverPackage, API, and integration guidance for Claude Code, Codex, Cursor, and other MCP clients, run locally through the CLI or hosted.September 2026

Developer platformThe developer portal

CapabilityWhat it doesAvailable
Telemetry dashboardsPer-app views in the developer portal over the events the SDK uploads, with metering that reconciles against what each device reports.September 2026Self-serve billingMetered usage for OfflineID, relay, telemetry, and location verification with plan tiers in the developer portal.September 2026

What comes next

In development means the code exists and is being finished. Exploring means we are working out whether and how.

In development

Mesh SDKNative packages with no React NativeWhere it stands
Swift and Android packagesPublished from the same bridge sources as the React Native module, with an API that is not settled yet. On iOS, a public entry point that wires storage and transports is next.Early release
Capability ExchangeA marketplace for machine capabilitiesWhere it stands
Capability ExchangeA signed provider directory, evidence-based routing with failover, independent probes, a hosted MCP surface, and prepaid clearing.Coming soon
GatewaysBridging meshes over long-range backbonesWhere it stands
Reticulum reference gatewayA self-hosted gateway that connects attached devices and bridges zones over a Reticulum backbone.Early testing

Exploring

AreaWhat we are looking atPart of
More platform bindingsExtending the one-surface SDK model to further platforms and runtimes beyond React Native, Python, Swift, Kotlin, Java, C, Ruby, Flutter, Rust, and the browser.Mesh SDK
Wider mesh bridgingExtending the bridging model that connects adjacent meshes so more independent networks can interoperate.Network
Broader integrationsDeeper interoperability with the storage, identity, and agent tooling teams already run alongside the mesh.Ecosystem

We do not publish dates or version numbers for unreleased work. Priorities follow what teams building at the edge actually need. If something here matters to your operation, tell us.

Building at the disconnected edge? Tell us what you need next.

Talk to us Start building