OpenCheck
Customer due diligence risk checks powered by the Legal Entity Identifier (LEI), open data and open standards - including the Beneficial Ownership Data Standard (BODS).
Try the demo at https://opencheck.world/
What is OpenCheck?
You paste in a Legal Entity Identifier. OpenCheck queries GLEIF first, derives every cross-source identifier it can (UK Companies House number, Norwegian organisation number, Irish company registration number, Finnish Y-tunnus, Latvian registration number, Lithuanian entity code, Estonian registry code, Czech IČO, Polish KRS number, Austrian Firmenbuchnummer, Slovak IČO, French SIREN, Dutch KvK number, Swedish organisation number, Swiss UID, Canadian corporation number, Belgian enterprise number, Danish CVR number, New York DOS ID, Croatian MBS, Maltese registration number, Moldovan IDNO, Serbian matični broj, Hong Kong Business Registration Number, Singapore Unique Entity Number, Brazilian CNPJ, New Zealand company number, Australian ACN/ABN, Indian CIN, OpenCorporates ID, Wikidata Q-ID, and more), and uses those bridges to fan out across 52 national and international corporate data sources.
Everything maps into BODS v0.4. Cross-source links and risk signals are computed deterministically, and the whole bundle is one click away from a downloadable export (JSON / JSONL / XML / CSV / Excel / ZIP, plus Senzing JSON entity records for entity resolution, FollowTheMoney entities for OpenSanctions / OpenAleph investigative workflows, a BigQuery property-graph package queryable with GQL, Google AML AI input tables, a Neo4j Cypher script, and BODS RDF as TriG for linked-data and SPARQL workflows).
The structural risk signals report the elements due-diligence standards use to judge ownership complexity — intermediate ownership layers above the subject, trusts and arrangements on the chain, nominees, and entities in FATF- or EU-listed high-risk jurisdictions — plus an advisory where withheld parties meet layered ownership. They assert no regulatory threshold; docs/risk-signals.md maps them to the EU AMLA customer due diligence standards (final draft, September 2026) and other frameworks.
Status
Latest: Phase 418 — The Estonia RDF demo queries answer the same questions as the release's Cypher file and assert the 25 October 2026 dataset's figures.
→ Full development history
Quick start
The backend ships with cache-first dispatch: in stub mode (no API keys, no OPENCHECK_ALLOW_LIVE) every adapter returns deterministic placeholder data. Live mode is opt-in per source via env vars.
Docker
cp .env.example .env
docker compose up --build
Local (without Docker)
Backend:
cd backend
uv sync
uv run uvicorn opencheck.app:app --reload --port 8000
Frontend:
cd frontend
npm install
npm run dev
The BOVS icons and country-flag SVGs are committed under frontend/public/, so the dev server needs no extra build step.
Documentation
| Page | Contents |
|---|
| How it works | Step-by-step lookup flow, per-adapter detail, Open Ownership BODS bundles, API surface, project structure |
| Dates | The four date clocks, which sources supply a declaration date, how precision is recorded |
| Sources | Full adapter table — active sources plus inactive bulk-only adapters, license, entry point, description |
| Risk signals | All signal codes: source-derived, structural complexity (with regulatory crosswalk), FATF / EU jurisdiction, state-controlled/SOE, cross-source name match, ICIJ Offshore Leaks |
| Subsidiary network | Lazy GLEIF Level-2 reveal — direct + ultimate children mapped to BODS, graph (small) or table + export (large) |
| Configuration | Environment variables, Render deployment, running the test suite |
| Datasets | Bulk releases — Estonia, MEIP, the Azerbaijani Laundromat — and how to rebuild them |
| Development history | All phases |
Licensing
OpenCheck's own code is MIT-licensed. Data retrieved from third-party sources is licensed under each source's own terms — see ATTRIBUTIONS.md. Downloaded exports include a LICENSES.md listing every source that contributed data, with re-use guidance for the most-restrictive licence in the bundle; the RDF export additionally stamps each statement with its source's canonical licence URI (bods:license), so the licensing information is machine-readable and travels with the data itself.
The frontend renders ownership graphs with Cytoscape.js (MIT). It re-uses the Beneficial Ownership Visualisation System design tokens (CC BY 4.0) and the BOVS entity/person icons and country-flag SVGs from Open Ownership's visualisation library (Apache 2.0) — both © Open Ownership. The committed assets live under frontend/public/bods-dagre-images/, a directory name retained from their original source.
Roadmap
- A "complex offshore" demo subject that fires every structural-complexity chip simultaneously.
- BODS RDF / SPARQL backbone via Oxigraph — load the assembled BODS bundle into a triple store, expose
/sparql for the published Open Ownership red-flag queries.
Open issues and discussion live in the GitHub repo.
Related projects
