Sites that run without backhaul
A multi-hop mesh across crews, vehicles, equipment, and sensors underground, offshore, and beyond the last access point. Coverage advances with the work face, sensor reads come back across the site, and safety workflows keep working in exactly the moments infrastructure fails.
A control room dashboard invokes a vibration sensor read over an offline industrial mesh network, relayed through crew devices on the plant floor with no plant WiFi and no cloud round trip.
The control room reads a sensor three hops into the plant through the crew devices on the floor.
Heavy industry runs where networks were never built
RF is hostile by design. Rock, steel, and interference kill radio. Leaky feeder and fixed WiFi cost heavily per metre and end exactly where the work face moves next.
Coverage moves with the crew. Worker devices, vehicles, and gateways relay for each other over BLE and WiFi Direct. Coverage advances deck by deck and drift by drift, with no cable pulled.
Safety cannot depend on backhaul. Mustering, lone worker check-ins, and evacuation coordination verify device to device with OfflineID and relay through whatever is in range.
Three environments, one mesh
What breaks today in each, and what the mesh does instead.
What you can build
Each of these runs on the shipped SDK primitives.
Crew coordination that advances with the work face, routed multi-hop across worker devices, vehicles, and gateways over BLE and WiFi Direct.
A control room tablet invokes a vibration read from a sensor deep in the plant, and chunked transfer brings payloads up to 100 MB back over the mesh.
A check-in authenticates device to device with OfflineID and relays through whatever crew devices are in range, in the conditions that take fixed infrastructure down.
Customer stories
How an evaluation runs
- Integrate
- The SDK goes onto certified worker devices, vehicle compute, and site gateways. Devices join the mesh and authenticate with site-provisioned OfflineIDs.
- Exercise
- A defined offline scenario underground, offshore, or at a remote site: crew coordination, sensor reads, and mustering running mesh-only.
- Measure
- Success criteria agreed before week one, evaluated against the opt-in telemetry record: delivery rates, hop counts, coverage at the work face, sync completeness at the uplink.
- Timeline
- 4 to 16 weeks, scoped up front, no open-ended commitments.
The primitives behind it
- DORS
- A mesh that moves with the crew, with automatic failover and transport switching that does not flap. How mesh networking works.
- Service discovery
- Any device gets a request and response interface to any capability within 8 hops, including equipment on the floor and across vessels. How service discovery works.
- OfflineID
- Every worker and contractor carries an Ed25519 identity verifiable device to device, with MLS-encrypted messaging between them. How offline identity works.
- Telemetry
- The operational record buffers on-device through the disconnected shift and flushes to your historian in order. How telemetry works.
- Your devices
- A React Native binding over a Rust core, on the certified handhelds and tablets the site already issues. Start building.
Industrial and energy FAQ
What is an underground mine communication system that does not need leaky feeder?
A device-to-device mesh. DORS routes multi-hop over BLE and WiFi Direct across worker devices, vehicles, and gateways, up to 8 hops, so coverage advances with the crew and the work face instead of ending at the last cable extension.
Does the mesh work underground and inside plants?
Yes, that is the operating assumption. Routing is multi-hop over BLE and WiFi Direct, so coverage follows the crew and their devices rather than fixed infrastructure. Every worker device, vehicle, and gateway extends the mesh up to 8 hops.
Does this replace our satellite link offshore?
No. Satellite remains your backhaul when you have it. The mesh handles local coordination on the platform or vessel, deck to deck and crew to crew, without a round trip through the link. When the backhaul returns, buffered data syncs.
Can vessels coordinate with each other at sea?
Vessels within radio range of each other, or bridged by devices between them, form a mesh directly. Service discovery lets systems on one vessel invoke capabilities on another, request/response, with no shore infrastructure in the loop.
Can we run this on intrinsically safe or certified devices?
The SDK ships as a React Native binding over a Rust core. It runs on the certified Android devices and gateway compute your site already approves; the protocol does not change your device certification requirements.
How is site data secured between devices?
Sessions are encrypted end-to-end with MLS (RFC 9420) by default, and every device and worker carries an Ed25519 OfflineID verifiable device-to-device. Muster checks and access decisions authenticate with zero connectivity.
How does an evaluation work?
A 4 to 16 week scoped evaluation against your site, your conditions, and success criteria we agree up front. Contact us to scope it.
How do lone worker check-ins work with no signal?
Over the mesh, not the backhaul. A check-in authenticates device-to-device with OfflineID and relays through whatever crew devices and gateways are in range, so the safety workflow keeps functioning in exactly the conditions that take fixed infrastructure down.
