Forward deployed
We built MacroView in public on open data and kept the record. We will build the same instrument inside your operation, on your flows.
People who judge an instrument on whether the count is right.
You judge a Hormuz count on whether it is right. So do we: coverage before calls, source credited, blind spots dated.
Tanker flow, AIS gaps, aircraft over chokepoints and port traffic fused with the regime tape, on your feeds and your clock.
A disruption score you can audit, with the baseline it was measured against and the days it could not see.
Funds come later, through the record.
Five steps, one question, a record at the end.
After the pilot: a retained forward-deployed engagement, scope agreed from what the pilot showed. Nothing is proposed that the pilot's own ledger did not earn.
Global Fishing Watch data on the public site is CC BY-NC and stays there. Pilot deliverables are built on your feeds and on sources licensed for commercial use.
Three things you can open right now.
Regime tape, transmission panel and six chokepoints, refreshed on their own schedules, open to anyone.
Open the terminal →The same data layer an agent can call. Seven MCP tools, three JSON routes, no key required today.
curl -s https://www.macroview.live/api/v1/chokepoint/hormuzRead the docs →
The worked case. Aircraft, quakes, events and AIS traffic fused into one disruption score with its coverage state; SAR vessels and port calls shown beside it.
See Hormuz →Scope a pilot
Tell us the flow you need to see and what you already have. We reply within one business day with a scope, not a deck.
Secure channel
Messages are delivered privately. One business day.
