From a messenger to a network

TL;DR

Offline Protocol began with Fernweh, a messenger whose every install deployed a mesh node, and the mesh grew to 350,000+ devices in 140+ countries with zero marketing spend. Its transport, identity and coordination layer is now an SDK whose apps relay for each other.

Offline Protocol did not start as a platform company. It started with Fernweh, a messenger built on one promise: it keeps working when the internet doesn’t.

Every Fernweh install did something quietly important. It deployed a mesh node. Phones running the app discovered each other over BLE and WiFi Direct, connected peer to peer, and relayed messages for each other, up to 8 hops, with no tower or router involved. The messenger was the visible product. The mesh underneath was, at first, just how it worked.

Offline Protocol network growth to 350,000+ devices

The network grew on product pull alone: it has reached 350,000+ devices across 140+ countries, organized into 11,500+ active mesh clusters, and that growth came from zero marketing spend and zero token incentives. People installed Fernweh because they wanted a messenger that survives blackouts, shutdowns, and dead zones, and every install extended coverage for everyone nearby.

That growth pattern taught us something about mesh networks that no whitepaper captures: coverage is the fleet itself. A mesh network’s reach is the union of every device’s radio range, so adoption is not just users, it is infrastructure. Density in a stadium, a neighborhood, or a disaster staging area translates directly into throughput and reach. The live network map makes this visible in real time.

Offline Protocol platform: DORS, OfflineID and Service Discovery

What we had built and battle-tested was not a messenger with an unusual transport. It was a transport, identity, and coordination layer that survives losing the internet, with a messenger as its first application. Somewhere along the way, the framing flipped.

That layer is now the Offline Protocol platform, in three shipped parts. DORS, the mesh transport, routes over BLE, WiFi Direct, internet, Reticulum, and Nostr with automatic failover and MLS (RFC 9420) encryption by default. OfflineID provides device-owned identity that verifies peer to peer, with no certificate authority round-trip. Service Discovery lets devices advertise, find, and invoke each other’s capabilities with no DNS and no registry server.

None of it is speculative. Every layer runs in production on the same network Fernweh grew to 350,000+ devices, through real disasters, real blackouts, and real shutdowns. When Bankless covered the Fernweh 2.0 release, what they were covering was also, without the name, the network’s first proof at scale.

Building on the Offline Protocol SDK

The platform is available the same way Fernweh’s transport always worked: as an SDK. One npm install gives developers all three layers, a TypeScript API over a Rust core, on iOS and Android through React Native. The SDK passed 12,000 npm installs this year.

And the growth loop that built the network still runs. Every app shipped on the SDK deploys nodes that relay for every other app on the mesh, and their nodes relay for yours. New apps do not start from zero coverage; they start from 140+ countries of it.

We went from a messenger to a network by shipping something people wanted and paying attention to what actually grew. If your systems operate at the disconnected edge, the network is already out there. Talk to us about building on it.