Every vessel page now carries an ownership dossier

When an Overwatch analyst pulls up a vessel that''s been flagged for an STS rendezvous or a dark gap, the first question is rarely "where is it?" — the satellite trace makes that obvious. The hard question is "who actually runs this thing, and have they been running it the whole time?"

Until this week, the answer required four browser tabs, a spreadsheet, and a willingness to trust whatever ownership chain the AIS broker last refreshed. As of today, every vessel page in Overwatch carries a built-in ownership dossier that combines two evidence layers we''ve been collecting separately for months.

What the dossier shows

The new panel sits below the vessel header and renders two stacked timelines:

GLEIF corporate identity — for any registered owner, operator, or technical manager whose name matches a Legal Entity Identifier in the Global LEI Index, Overwatch now shows the LEI code, current legal status (active, lapsed, retired), incorporation jurisdiction, immediate parent company, and the date that record was last updated by the local operating unit. If the company has been renamed or absorbed, the LEI lineage exposes that automatically — you see "X was renamed to Y on 2024-03-15" instead of two unrelated entities.

Wayback Machine snapshots — for the same owner names, Overwatch surfaces historical snapshots of the company''s public website, captured by the Internet Archive. The dossier shows the snapshot dates and one-click links into the archived pages. Analysts use this to recover information that''s since been scrubbed from a live site: a roster of vessels under management that quietly shrank by twelve hulls last quarter, an "About Us" page that named the beneficial owner before it was edited to remove them, a port-call history that contradicts the operator''s current public posture.

Together those two sources turn a vessel page into a continuous record. You don''t just see who currently operates the ship — you see the ownership timeline, and for each name on that timeline, what the company looked like at the time.

Why we built it

We kept seeing the same pattern in investigations. An analyst would identify a suspicious behavior — a missed transit, a destination deception, a draft mismatch that doesn''t square with the declared cargo — and trace it back to a specific operator. They''d want to know whether that operator had been running the vessel for years, or whether the management contract had quietly switched a month ago to a shell company nobody had heard of.

The signal lived in two separate places. Corporate identity data sits in GLEIF, a regulator-grade registry that''s underrated as an intelligence asset because most analysts have never heard of it. Historical website state sits in the Wayback Machine, which has been quietly archiving the maritime web since 2001. Both are free, both are queryable, and almost nobody was pulling them in line with vessel context.

By joining them at the vessel level, Overwatch removes the discovery cost. The analyst doesn''t have to remember to check; the page just shows it.

A worked example

Take a vessel we''ll keep anonymous. Its current AIS broker lists Operator A as the technical manager. The dossier shows that Operator A was incorporated in 2024, has a single LEI record, and was the technical manager on this vessel for exactly seventeen days before the AIS broker updated its records.

Before those seventeen days, the technical manager was Operator B — incorporated in 2008, with a continuous LEI record, headquartered in a jurisdiction we''ll just say has been in the news a lot lately. The Wayback Machine has 144 snapshots of Operator B''s website spanning 2009 to last month. The snapshot from forty days ago lists this vessel under "fleet." The snapshot from yesterday does not.

That sequence — a long-tenured operator quietly replaced by a brand-new shell on the day a flagged transit occurred — used to take an hour of manual cross-referencing. The dossier surfaces it the moment the page loads.

What''s under the hood

The GLEIF side is straightforward: we maintain a local mirror of the LEI Index, refreshed nightly via the GLEIF concatenated file. The matching pass joins on legal-entity name and country, with fuzzy fallbacks for transliteration variants. If we can''t get a confident match, we don''t show the dossier — we''d rather show nothing than the wrong company.

The Wayback side is more interesting. We don''t snapshot anything ourselves; we query the Internet Archive''s CDX API for known operator domains, capture the snapshot index, and surface dates that fall meaningfully before or after the events Overwatch is showing on the vessel timeline. When an analyst is looking at a dark gap from six weeks ago, the dossier highlights the snapshots that bracket that date, because that''s when the operator''s public posture would have mattered most.

Both signals join the existing maritime knowledge graph as first-class evidence nodes. They show up in case files, they flow into the case-file investigation workflow, and they''re available via API. Nothing about this is a one-off panel.

What it changes

We think this is the kind of feature that''s invisible to anyone who isn''t doing the work. To an analyst running a case, it removes a category of question that used to take real time and now takes a glance. To someone who''s never investigated a vessel, it looks like a sidebar.

Both reactions are correct. The dossier doesn''t reveal anything that wasn''t theoretically already discoverable. It just collapses the discovery time from an hour to a second. That''s most of what investigative tooling is, when it''s done right.