Tool profile
Aleph
Document-led investigative research across public datasets
Claims and corrections are reviewed before public profile changes.
Official-page screenshot
OCCRP
Document-led investigative research across public datasets
Best for: Document-heavy public-records, company, procurement, sanctions-adjacent, and cross-border investigative research where source documents matter.
Signal summary
Trust / disclosure
How to read this profile
Editorial line
Editorial judgment and commercial context are kept separate on OSINT4ALL.
Review status
This profile has an editorial review date. Source checking does not mean the tool was hands-on tested.
Claims / submissions
Corrections and claim requests are reviewed before any public change is made.
Commercial context
No commercial relationship is disclosed on this profile.
Editorial verdict
Use case and fit
This is editorial guidance, not vendor copy.
Document-heavy public-records, company, procurement, sanctions-adjacent, and cross-border investigative research where source documents matter.
Best for serious due diligence and investigative work where source documents deserve more weight than summaries.
Best for document-heavy public-records research where entities, datasets, filings, and source documents need to connect.
Operational snapshot
Workflow, access, and coverage
Searching accessible investigative datasets and linking document evidence
Entity Name, Identifier, Search Text, Uploaded Document
Document Match, Entity Reference, Network Diagram, Cross Reference Candidate
Document Discovery, Evidence Organization, Entity Corroboration
Search only covers datasets accessible to your account on that Aleph instance. OCR and name matches can be wrong; inspect source documents and identifiers. Uploading documents transfers them to the chosen instance, so check its access and sharing settings first.
Begin with identifiers, inspect source documents, tag confirmed versus possible matches, then corroborate high-impact claims with official records and independent sources.
Cross-border datasets may include multiple languages, transliterations, and local naming conventions.
Limits
Strengths, caveats, and risk
Strong when the work depends on documents, datasets, and relationship clues rather than a single database field.
Entity matching can be noisy; dataset provenance and dates must be checked before drawing conclusions.
Not a live registry, not a universal leak search, and not proof that a named entity is the same person or company without corroboration.
False identity matches are a major risk when names, transliterations, companies, and jurisdictions overlap.
Sensitive public-record findings should be framed as evidence from named sources, not as legal or compliance verdicts.
Trust the underlying source trail more than the search result; record dataset origin, update date, access level, and match confidence.
Maintenance
Source status & suggest an update
Help keep this profile accurate. Update requests are reviewed and logged before publication.
Source checked: 2026-05-27
If something is outdated, please submit a correction or ownership update request. Claim requests are reviewed and do not grant editorial control.
Commercial or sponsorship requests use the separate partner workflow.