What screens today, what is shipping next, and what is still on the roadmap — described honestly, so you can plan around it.
Defensive transparency is the brand. Every capability on the following pages is marked with one of three states — and the state is never softened to make the product look further along than it is.
In the product right now. Test access is open today; commercial launch is planned for summer 2026. If a slide marks something shipped, you can screen against it this week.
Actively in development, with a working first layer or a defined design. Useful enough to demo, not yet complete. Confidence scoring and the EAR99 fallback are the lead examples.
Committed direction, not yet started or early. Sequenced behind the items above. We will not pre-sell these as if they exist.
No timeline on this roadmap is a contractual commitment. Dates and sequencing reflect current intent and can move as regulatory sources and customer priorities change.
Six capability areas are live in the product. Each produces a source-linked, reviewer-taggable result that lands in a case — the audit trail is not a roadmap item, it is the foundation everything else extends.
The platform grows outward from a stable core. Each horizon adds reach without changing the contract: source-linked results, reviewer sign-off, and a defensible audit trail.
The export-control candidate layer is already live — the layer that separates a TARIC calculator from a compliance platform. The following slides go into how it works and where it still defers to a human.
PEP screening is live and runs on its own logic — separate from sanctions. A sanctions hit stops a transaction; a PEP match raises an enhanced-due-diligence signal for the reviewer to weigh. The two are never conflated.
A Wikidata primary layer plus an official EU-27 and European Parliament (MEP) layer. Official sources override Wikidata, and the official coverage keeps growing.
PEP status is a due-diligence input, not a verdict. The platform surfaces it with evidence and an as-of date — the reviewer decides what it means for the relationship.
Available now through the MCP / API tool screen_pep and on the entity screening result card.
Goods sanctions are close to binary: one code, one prohibition. Export controls are not. A single customs code can carry dozens of possible control outcomes — the answer depends on what the product actually is.
The same CN code can resolve to any of the following, depending on product characteristics:
Radiation hardening, performance grade, temperature range, presence of encryption, military design, end-use and destination. None of that is in the customs code.
CN ↔ ECCN is not one-to-one. A multi-level pipeline is required — and the final call always needs a human. That pipeline is the candidate layer the platform now runs.
Each level narrows the answer and raises confidence. Levels 1–2 run today; level 3 is on the roadmap; level 4 always hands the final call to a human — never the other way round.
Quick screen — is this potentially dual-use or military at all?
Semantic matching of the product description against Annex I and the Military List.
Technical parameters — performance, encryption, end-use, destination — tested against rule conditions.
An analyst confirms a status — cleared with rationale, review required, or licence required — with an evidence pack.
Levels 1–2 (the candidate layer) and the level-4 analyst review workflow are live today. Level 3 — rule-based legal classification — is the roadmap item. The final decision is always the customer's export-control analyst.
The export-control layer is part of the same result card you already get for classification and goods sanctions. It is presented as possible review required, never as a final licence decision.
EU Dual-Use Annex I and the EU Common Military List as official EUR-Lex / CELLAR artifacts, an ECICS chemical reference for CAS / CUS / EC lookups, plus US EAR CCL, US ITAR USML and the UK Strategic Export Control List as candidate-evidence sources.
Every candidate carries source evidence, a score and a confidence level — but it stays a review signal until an analyst confirms the technical classification. The card says “possible export-control review required”, not “classified”.
Live now through case-item evidence and the MCP / API tool search_export_control_candidates. US / UK coverage is candidate evidence — the EAR99 fallback and final ECCN classifier remain roadmap.
Payment screening is live and goes well beyond a yes/no on a message. Every run is a durable case with the raw message, the participants, and a report a reviewer can open and defend.
A payment decision has to be defendable months later. Keeping the raw message, the participant results and the enrichment warnings together turns a transient check into a durable audit record.
The platform screens the message and flags what it finds — it does not release or hold the payment. The release decision stays with the customer's payment operations.
Live now across the web cabinet, the REST API and the MCP connector.
One view of the whole product. Read a row left to right to see how far a capability extends today and where it is heading.
| Capability | Now | Next | Later | Notes |
|---|---|---|---|---|
| HS / CN / TARIC classification & dutiesBy description or numeric code, EUR-Lex linked | Shipped and stable | |||
| RU / BY goods sanctionsReg. 833/2014 & 765/2006 | Shipped and stable | |||
| Entity & UBO screening17 source codes, as-of-date history | Shipped and stable | |||
| PEP / EDD screeningWikidata + EU-27 & European Parliament | Live — official coverage growing | |||
| ISO 20022 payment screeningPaymentCase, XSD validation, signed reports | Shipped and stable | |||
| EU export-control candidatesDual-Use Annex I, Military List, ECICS | Live · beta — candidate layer | |||
| US / UK export-control candidatesEAR CCL, ITAR USML, UK Strategic List | Candidate evidence live; UX expanding | |||
| Analyst review workflowDecision statuses, rationale, evidence | Live — deepens toward licence workflow | |||
| Rule-based final classificationSpecs & end-use tested vs. rules | Roadmap — not pre-sold | |||
| Multi-regime & end-use controlsWassenaar, MTCR, NSG, Australia Group | Roadmap — not pre-sold |
Every layer extends reach without weakening the contract: a source-linked result, a reviewer who signs off, and an audit trail that defends the decision later.
Customs classification and duties are table stakes. Export controls are the layer that separates a TARIC calculator from a compliance platform — and that layer is already live.
In electronics, chemicals, optics, aerospace and encryption, export-control screening is a legal requirement, not a nice-to-have. The roadmap follows that obligation.
Export-control violations carry multi-million fines and personal liability for company officers. Evidence and review-required wording exist to keep the customer defensible.
Classification, sanctions, PEP, payments and export controls reuse the same machinery — TARIC parsing, EUR-Lex reading, evidence and explainability. New layers extend the core; they are not separate products.
The platform is in pre-launch — commercial launch is planned for summer 2026, and test access is open today. What follows is what we will and will not claim while we get there.
Classification, duties, goods sanctions, entity / UBO screening on 17 source codes, PEP / EDD screening, ISO 20022 PaymentCase, the EU export-control candidate layer with US / UK candidate sources, and the analyst review workflow — all live across the web cabinet, the API and the MCP connector.
Stronger confidence and evidence quality, an expanded US CCL / USML / UK candidate experience, EAR99 fallback handling, and MCC-code coverage.
A candidate is a review signal — we will not call it a final dual-use, military or ECCN classification. We do not yet claim a rule-based classifier, an EAR99 fallback or a full licence-decision workflow. The licence decision stays with the customer's analyst.
Not affiliated with the European Commission. Does not replace official sources or licence decisions by competent authorities. No date on this roadmap is a contractual commitment.