Less idle time on the haul road.
Route your trucks on your own private site, no public map needed. When a haul road closes, a pit advances or a tip moves, we re-plan around 100 stops in about a millisecond, only the affected runs. The mathematics is solved, not guessed, so the answer holds. Every byte of site data stays on site.
What it does on a site
Routes your private roads
Bring your own site map, haul roads, ramps, tips, workshops. The engine is map-agnostic, so it needs no public map and works underground or in the open pit.
Re-plans the moment the site changes
A blocked haul road, an advancing face, a moved tip or a breakdown becomes a small cost change, we re-route only the affected runs, not the whole plan.
Runs on-site
Light enough to run on your own server or a control-room machine, offline. Routes and positions never have to cross your firewall.
Less idle, more cycles
Shorter, faster cycles for haul trucks, loaders and service vehicles, the kind of saving that shows up on a high-fuel, high-utilisation site.
Who it is for
How it deploys
How it deploys
Most operations run on the standard cloud subscription. For disconnected (DDIL) pits with no signal, a separate on-site edge bundle keeps re-routing alive, the same engine, sold as a bespoke add-on.
Cloud subscription
The default: call the API, we run the infrastructure. In-region routing computes on a local road graph, so route compute stays in-region with no per-call cloud round-trip.
DDIL edge bundle (separate add-on)
For disconnected pits: a site/vehicle edge container loads your site graph once and routes locally, so re-routing keeps working with no signal. Sold separately, like the military edge.
Less idle time on the haul road.
Route on your own private site graph, re-route instantly on a blocked haul road, cut idle time. Runs on-site; data never leaves.