Sensing
The Sensing stage collects GPS pings, carrier API status events, and active weather alerts into a single stream. Each signal is scored against the shipment’s estimated transit time so that only events crossing the configured severity threshold — by default fifteen percent — generate an in-app alert. The result is a continuous picture of the lane without a dispatcher asking for it.
Negotiating
The Negotiating stage translates a sensed disruption into a single scored reroute recommendation per shipment. A lane rate is requested for the top three candidate paths, scored on cost, transit time, and confidence, and presented to the on-call planner as a choice rather than a pending question. This is the layer where autonomous supply chain resilience becomes a decision rather than a notification — one click either accepts the recommendation or overrides it with a reason that is fed back into the engine.
Self-healing
The Self-healing stage is what closes the loop: every accepted reroute is logged as a rerouting event so that the next disruption on the same lane benefits from yesterday’s outcome. Carrier reliability scores and corridor weather baselines update quietly in the background, and the threshold itself adapts to the fleet’s baseline ETAs. The platform does not stop being autonomous between disruptions — it gets more accurate.
See it on a real lane
Both pricing tiers run the same autonomous disruption pipeline on your real fleet — pick the depth and keep the engine.