Sensing
In FlowSync’s three-step loop on /how-it-works, the Sensing stage watches the same incoming signal mix that both philosophies have to absorb: GPS pings, carrier API drift, and active weather alerts that overlap the lane’s bounding box. The difference is what each philosophy does with the stream once it lands. Reroute-on-incident scores every event against the shipment’s transit-time baseline and alerts only on those crossing the configured threshold (fifteen percent by default). Multi-carrier diversification spreads the fleet’s volume upstream so individual carrier-side disruptions are muted before they ever reach the alert queue. The operator consequence is concrete: reroute-first absorbs more lane noise at on-call time, while the hedge pays for that quietness in capacity booked ahead of the disruption.
Negotiating
AI freight rerouting vs carrier diversification is most visible at the Negotiating stage. The reroute branch takes a single ranked DisruptionEvent and asks the routing engine for one scored recommendation per shipment — a primary route plus the two next-best alternatives, priced from current spot, with confidence and SLA tradeoffs side by side. The hedge branch, by contrast, sustains a standing capacity roster so the on-call call becomes "which carrier do I lean on today" instead of "what do I replan?". What FlowSync actually runs is the reroute-first pattern with a calibrated hedge posture underneath, and a live rerouting outcome from that lane is walked on /proof — so the two compose rather than compete on the same corridor.
Self-healing
The Self-healing stage rewrites the lane baseline after every accepted reroute. Carriers that delivered cleanly on the reroute-after-disruption branch pick up a higher reliability score on the next event; carriers in the active hedge roster get fewer direct reroutes but keep the corridor warm. The fleet’s hedge posture — how much baseline diversification you pay for — is itself a tunable on the onboarding call, not a binary pickup at sign-up. The point both branches leave behind on the lane is the same: a quieter next disruption and a tighter reasoning chain on the reroute that follows it. Teams that want to see both branches running on their own fleet can begin with a Pilot that is free for 14 days, then $350/month — the operating entry point lives at /pilot.
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.