Nobody can tick a flow green. It has to earn it.
The residency map lists every system and vendor that holds or receives payment and identity data. Each flow's status is worked out from what Onshore actually sees, so remediation tracks itself.
A spreadsheet of data flows is out of date the day it's finished, and it says whatever the last person typed. An auditor wants to know what really happened.
Flows appear by themselves
When a pipeline or route sees traffic to a new host, it goes on the map, matched against a catalogue of vendors.
Declare what we can't see
Add a warehouse in a foreign cloud through a short builder. It's labelled as declared, everywhere it appears.
Fix it, with proof
A flow turns green only when Onshore is protecting it for a clean week, or it's shown to stay in Nigeria.
Status from evidence
Leaking, Watch only, Protected, Verified, In Nigeria, Accepted risk or Unverified. No API or screen can set one by hand.
No grace on regressions
One unprotected detection takes a verified flow back to leaking, and the 30-day clock restarts.
Never guessed from an IP
Until you confirm a vendor's region or declare a location, a flow counts as offshore. An IP lookup is only a hint.
Two scores
Share of flows that are safe, and share of data volume, so one big leak can't hide behind many small clean flows.
Exceptions that expire
Accepting a risk needs a second person and an end date. The score always shows the figure without it.
Ready for GRC tools
Signed report pages, and CSV or JSON exports with stable IDs and a signed manifest.
Early access: the vendor catalogue comes from public information, so confirm each vendor's region for your own account. Timing rules have been tested with backdated evidence, not yet over real weeks.
Start with one leak.
Tell us which flow worries you most. We'll show you what it would take to keep it onshore.