Lynxaris

Trade Risk Intelligence

Decide if a trade can proceed, and show why

Lynxaris connects sanctioned entities, controlled goods and trade routes into one picture, and shows the source and the timestamp behind every number it puts on screen.

In development. Access is granted case by case, and there is no open sign-up yet.

A globe centred on Europe, Africa and Asia. Trade routes follow great-circle geometry from Rotterdam to Shanghai by way of Gibraltar, Suez, Bab el-Mandeb and Malacca, with the alternative around the Cape of Good Hope drawn as a dashed line, plus transatlantic, transpacific and Gulf routes. The chokepoints are marked at their real coordinates.

The foundation

Every number carries its source and its timestamp.

A compliance decision you cannot explain is a compliance decision you cannot defend. Lynxaris refuses to display a figure that does not carry where it came from, when the underlying data was captured, and which method produced it. When a value cannot be computed honestly, the interface shows a gap, never a placeholder number.

as_of · source · methodology: enforced, not promised

The differentiator

Three regulated domains, one decision.

Screening, export control and route exposure are usually three separate tools and three separate answers. Lynxaris keeps them in one model, so the question stops being "is this name on a list?" and becomes "can this shipment move?".

Routes

Route intelligence

Maritime corridors and chokepoints, with geopolitical events mapped to the legs they actually affect, not to a country-wide colour. Routes follow great-circle geometry, so a distance on screen is a distance at sea. Where geometry is unknown, it is declared; where a corridor is legally blocked, arithmetic does not override the block.

This is the part nobody else joins up. Screening an entity is a solved problem. Knowing that the entity, the commodity classification and the leg through a strait are the same decision is not.

Chokepoints modelled
  • Strait of Hormuz26.57 N · 56.25 E
  • Bab el-Mandeb12.58 N · 43.33 E
  • Suez Canal30.50 N · 32.35 E
  • Bosphorus41.12 N · 29.07 E
  • Strait of Malacca2.40 N · 101.83 E
  • Panama Canal9.08 N · 79.68 W
  • Strait of Gibraltar35.90 N · 5.30 W
  • Cape of Good Hope34.40 S · 18.50 E
  • Strait of Dover51.00 N · 1.50 E
Entities

Sanctions screening

Screening against official public sources (OFAC, UN, EU, UK and Canada) with fuzzy and phonetic matching for transliterated names, and auditable reason codes behind every match.

Goods

Export controls

Dual-use classification against EU Annex I of Regulation 2021/821, plus tariff and destination logic. What the goods are, not only who is buying them.

Evidence

Cases and audit trail

Append-only audit log, evidence chains and exportable briefs. Built so a decision can be reconstructed months later by someone who was not there.

Worked example

It does not score in silence.

An assertion needs converging evidence from independent lineages. Two restatements of the same article count as one source, not two. Below is the shape of a single call: the same shape the product exports when a decision has to be defended.

Assertion Entity A is listed

A counterparty appears on a consolidated list under an ownership relationship, not by direct designation.

Lineage 1 Official list record

The designation itself, with its legal basis and programme.

EU Financial Sanctions Files · OFAC SDN
Lineage 2 Corporate registry

The ownership chain that carries the designation across to the counterparty.

GLEIF LEI relationship records
Verdict Converging · REVIEW

Two independent lineages agree, so the call stands. Had one been missing, the answer would be "not established", never a quiet zero.

  • A missing signal is shown as missing. A zero that means "we could not measure" is never displayed as a zero that means "no risk".
  • Provenance cannot be hidden: not in exports, not in screenshots, not in presentation mode.
  • A legal block outranks the arithmetic: if a corridor is blocked, no favourable scenario turns it green.
  • The platform supports the decision and shows the reasoning. It does not issue legal verdicts.

Reach

A corridor is only as open as the water it crosses.

Routes are drawn with great-circle geometry: the same calculation the platform runs server-side, not straight lines on a flat map. The chokepoints are marked at the coordinates the risk model actually evaluates.

Europe–Asia · via Suez Rotterdam → Shanghai
Europe-Asia corridor via Suez, with the state of three chokepoints Illustrative operating state drawn on real geometry. The route runs Rotterdam, Strait of Dover, Strait of Gibraltar, Suez Canal, Bab el-Mandeb, Strait of Malacca and Shanghai. Gibraltar is clear, Suez is under review, Bab el-Mandeb carries active risk. Coastline from Natural Earth 1:110m, public domain; chokepoint coordinates are the nine canonical ones the product uses; the line follows great-circle geometry. Rotterdam GibraltarCLEAR SuezREVIEW Bab el-MandebRISK Malacca Shanghai
Clear Under review Active risk Illustrative state · real geometry · Natural Earth 110m

Provenance

Where the data comes from.

There are no customer logos to show yet. What can be shown is every dataset behind a decision, by name, with its licence and its official link. Only sources actually integrated and cleared for commercial use are listed.

Sanctions lists

Export controls & tariffs

Maritime & ports

Natural hazards & weather

Corporate & open intelligence

Access

Talk to the person who built it.

Lynxaris is developed by SatData Solutions. If sanctions exposure, export control or route risk is part of your work, get in touch and describe the decision you are trying to defend.

Where the product stands today

Lynxaris is built and in active development, and is not yet generally available. This page deliberately carries no customer testimonials, no certification badges and no uptime figures, because none of those would be true today. When they are, they will appear here with the evidence attached, the same rule the product applies to itself.