Workflows that kept running when the network did not
Every evaluation starts with one workflow and success criteria agreed up front, then measures the protocol against them on the operator's own devices and sites. These are the results, published as operators clear them.
Fernweh brings private messaging beyond internet coverage
Offline Protocol powers nearby message delivery in Fernweh, while encrypted history and search stay on the phone as connectivity changes
Read the story
Keep QSR orders moving through the rush, even offline
Offline Protocol connects the counter, drive-thru, kitchen, and handoff team around one shared order workflow, helping crews coordinate efficiently and keep service responsive.
Read the story
EV charging operations continue through cloud outages
Chargers and site controllers retain session state, resolve approved local commands, and return complete records to the existing charging platform after cloud outages
Read the story
Airline catering carries a complete record from kitchen to ramp
Production, quality, dispatch, and ramp teams share batch records and confirmed cart handoffs through cold-room and airside coverage gaps
Read the story
Fleet telemetry and field work stay connected beyond cellular coverage
Vehicle gateways and crew devices retain telemetry, assignments, and completion evidence locally, then reconcile with dispatch when a route becomes available
Read the story
Wind-farm technicians stay connected across brands and backhaul gaps
A shared local service layer gives technicians access to approved asset data and retains inspection evidence through backhaul outages, alongside existing SCADA and monitoring
Read the story
Secure offline coordination, built into OEM devices
A semiconductor integration packages a 449.5 KiB embedded runtime, gateway software, and qualification tools for smart-access and energy-device manufacturers
Read the story
Industrial inspection findings reach the lead without internet
A controlled two-phone demo connects defect capture to an on-site lead response, then reconciles both phones with a test backend
Read the storyWhat every study measures
The same five criteria, agreed before anything is installed, so results are comparable across sectors.
Did the work the operator cares about finish during the outage, not just after it.
Every retry and reroute accounted for, with nothing processed twice on reconnection.
How long it took for local results to land in the system of record once a link returned.
What the operations record covered through the gap, and what it would have lost before.
Bytes that stayed on the local mesh instead of crossing metered or scarce links.
