From a messenger to a network
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.
The network grew on product pull alone
Then the network kept growing. Today it spans 350,000+ devices across 80+ countries, organized into 10,000+ active mesh clusters. 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.
The network turned out to be the product
Somewhere along the way, the framing flipped. 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.
That layer is now the Offline Protocol platform, in three shipped parts. DORS, the mesh transport, runs BLE, WiFi Direct, and internet concurrently with automatic failover and MLS (RFC 9420) encryption by default. OfflineID provides self-sovereign 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 350,000+ device network fernweh grew, 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.
What this means if you are building
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. Around 5,000 developers validated the SDKs 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 80+ 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.