Infrastructure for the disconnected edge
Offline Protocol is the software and network layer that keeps apps and devices communicating, authenticating, and coordinating when the internet is unavailable. We build the offline mesh networking platform, identity, service discovery, and reliability primitives that make this possible on ordinary devices.
How we got here
We started by shipping fernweh, a messenger that keeps working when the internet doesn't, and watched the live network underneath it grow to 350,000+ devices across 80+ countries on product pull alone. That network turned out to be the product: a transport, identity, and coordination layer that survives losing the internet. Today we build that layer for the teams whose systems operate at the disconnected edge, and for the developers whose apps extend it.
What we believe
Coordination should not depend on a tower or a server. Four beliefs shape everything we build.
It works when your network does not
The most important moment for a network is the moment the internet goes down. We start from that moment and design backward, so coordination survives losing the tower and the server.
See the platform →No single point of failure
Infrastructure that funnels through one tower, one data center, or one provider has one thing to break. A mesh has no chokepoint to grab and no off switch to flip. Traffic finds another path.
How mesh networking works →Devices coordinate directly
Phones and hardware advertise, discover, and invoke each other over BLE and WiFi Direct with no server and no DNS. A device several hops away is reachable like a local endpoint.
How service discovery works →Privacy by architecture
Sessions are encrypted with MLS by default and keys never leave the device. Privacy is a property of how the system is built, not a policy layered on top of it.
How offline identity works →Investors
