Hop-level route identity
Ports, handlers, and border crossings recorded against each shipment so disputes do not devolve into email archaeology.
Structure
Leg · node · regime
Trade & export corridors
Every hop logged. Every regime mapped.
Ophanim for trade corridors
Routes are not neutral. Document them like the assets they are.
Trade desks, ports, and export agencies get continuous views of corridor exposure: which legs, which jurisdictions, which policy rules can strand or re-price a cargo.
Corridor policy scoring
Export controls, sanctions, and partner rules scored on the path — not only on origin country labels in a BL.
Risk
Path-aware scores
Re-route decision support
When a leg becomes high-risk, see which alternate corridor structures still satisfy buyer and regulator proof needs.
Action
Comparable path options
What sets us apart
Corridor intelligence. Booking decisions made defensible.
Treat logistics as compliance surface
Custody and regime risk do not stop at the mine gate — they live on every transfer and warehouse.
Coordinate shippers and traders
Shared passport and corridor views reduce handoff friction when title and responsibility change mid-route.
Protect trusted trader programmes
Documented paths and exceptions support higher-trust status with customs and border counterparts.
Spot stranded-route risk early
Policy shocks on a single port or land crossing surface against live bookings, not after demurrage starts.
Inside the platform
Corridor network and live shipment path in one place.
See active corridors, risk heat, and hop history without stitching TMS exports by hand.
View products- 01Network map of designated mineral corridors
- 02Per-shipment hop timeline with custody proof
- 03Regime alerts tied to nodes and borders
- 04Export packs for customs and buyer review
FAQ
Questions teams in this sector ask first.
01Do you require full TMS integration day one?+
No. Start from booking and milestone events you already track; deepen connectors as the programme matures.
02Can free-trade-zone and bonded workflows be modeled?+
Yes. Zones and temporary storage are first-class nodes so regime and custody context does not disappear in the grey zone.
03Who owns the record — shipper or trader?+
Identity can be multi-party with scoped edits. The point is continuous path truth, not single-company capture.
04How is this different from track-and-trace?+
Track-and-trace answers where. We also answer why a path is compliant or exposed, with citations to the rules that apply at each leg.
Ready when you are
Score a live corridor with us.
Share origin, destination, and typical hands. We’ll sketch hop structure and the first policy heat map.
Request a demo