01 · Product name
Aleph Pro
OCCRP's archive. Access is an application.
Published by OCCRP.
In short
The page at aleph.occrp.org on 18 Oct 2026 titles the product Aleph Pro. It says reporters follow the money through government records and databases, and that a short application is reviewed one by one, with access typically granted within 72 hours if approved. Accredited journalists can also reach an archive of leaked evidence. The alephdata/aleph README says the open-source project is being sunset and that core-team maintenance ended after 31 December 2025. The GitHub license field is MIT. A hit in the archive is a lead, not a finding.
Product pricing strategy
02
Free and paid
The Aleph Pro page opened on 18 Oct 2026 does not print a dollar, euro, or pound price. The public step is an application. The page says requests are reviewed individually and that access, if approved, is typically granted within 72 hours. It separates the public-records archive from leaked evidence, which it limits to accredited journalists. Do not invent a seat fee from that distinction. The open-source README does not print a price either. It says core-team maintenance of that repository ended after 31 December 2025 and points organisations to Aleph Pro. MIT in the SPDX field describes the published repository. It does not mean the hosted archive is a free login. If a later contract prints a number, cite the contract.
Utility and features
03
Aleph Pro's public page describes a hosted archive for investigative reporting. It says the platform brings together current and historic databases, documents, leaks, and investigations, and that OCCRP regularly fetches public records from over 200 online sources and structures them for search. The same page says you can be notified when new data is added, sketch connections in an investigation, upload your own documents, and share them with colleagues. The door on that page is an application form, not an open search box. This listing did not submit the form and did not open a workspace.
- Application, not a public box. The 18 Oct 2026 page says fill out a short form. Review is individual. The 72-hour line is the page's, for approved requests.
- Public records and leaks. The page says public records are fetched from over 200 sources. Leaked evidence is described as a further archive for accredited journalists.
- The MIT tree is sunset. alephdata/aleph is MIT in the SPDX field. The README says core-team maintenance ended after 31 December 2025.
The GitHub repository alephdata/aleph, default branch develop, still describes Aleph as software for indexing documents and structured data and for cross-referencing entities against watchlists. The README warning says involvement with that open-source project is being sunset, maintenance of that version ended after December 2025, and the team rewrote the codebase to launch Aleph Pro. It points questions to aleph-pro@occrp.org and to an FAQ on occrp.org. The SPDX field on the repository is MIT. The develop branch is marked unreleased. A self-hosted copy of the old tree is not the hosted Pro workspace, and this listing did not install either one.
- 1
Read the Aleph Pro page and note whether you need the public-records archive or the journalist leak archive.
- 2
If you self-host, read the sunset notice before you pin a commit on develop.
- 3
Keep a hit as a lead until the cited source is opened.
Caveats
04
An application is not an account. This listing did not receive access, so it does not describe the search screen, a dataset count inside the workspace, or a leak file. The phrase over 200 online sources is the page's. It was not recounted here. The README's sunset date is 31 December 2025. A fork that still runs is someone else's maintenance, not a promise from the core team.
Leaked evidence and public records are different piles on the page. Do not describe a public-register row as a leak, or a leak as a current filing. A name match in an archive is a lead. Confirm it in the source the row cites. The develop branch is the README's name for unreleased code. Do not treat a commit on that branch as the hosted product.
Potential use cases
06
- A newsroom wants the hosted archive. Open aleph.occrp.org and read the application, not an old screenshot of a search box. On 18 Oct 2026 the page titled the product Aleph Pro and said approved access is typically granted within 72 hours. It separates public records from leaked evidence for accredited journalists. Do not describe a workspace this listing did not open.
- An engineer wants to pin the MIT repository. Read the sunset notice on alephdata/aleph before you choose a commit. The README says core-team maintenance ended after 31 December 2025 and that the develop branch is unreleased. MIT in the SPDX field describes that tree. It does not grant a login to the hosted archive. Questions go to the address the README prints.
- A hit from an older Aleph export is about to be briefed as current. Keep the dataset name and the date of the export. The public page says OCCRP fetches records from over 200 sources. That count is the page's. A name in a leak archive is not a Companies House filing and not an LEI. Open the source the row cites before you write the sentence.
Hard cases
The case where the first result is easy to over-read.
The MIT tree is called the product
The hosted page and the GitHub README are different sentences. Aleph Pro is the application page that loaded on 18 Oct 2026. alephdata/aleph is the repository whose README says maintenance ended after 31 December 2025. Do not tell a reader that cloning the repository opens the journalist archive. Do not tell them the application printed a price. It did not.
Practitioners using it
Posts on X from people describing a concrete use. The quote is the post. Likes and reposts are the counts saved with it, not a live total. A label marks a creator, a maintainer, a vendor, a partner, a data partner, or an investor.
Creator
We've made the @HindsightFiles release of documents from Cambridge Analytica publicly searchable on @OCCRP Aleph: https://t.co/1nhroT9ccZ #leaks
Here, @jlstro , @OCCRP chief data editor, explains how to use their Aleph tool, which consolidates data from millions of documents — including corporate registries, financial records, leaks, & legal filings — and makes them searchable and cross-referable. https://t.co/qhUY1Z4NO3
Detailed guide to the use of https://t.co/h47zwGMDJq for investigations related to Russian-Ukraine conflict: - list of russia related datasets; - instructions for using the Aleph interface; - recommendations for selecting keywords for searches. https://t.co/KEDEvGdLOz pic.twitter.com/4mbQYSEeDs
Using R with google drive or OCCRP Aleph to scrape and OCR databases of PDF files to make them searchable is mega useful, that's how I got this story: https://t.co/5IBk6acwZ0
Questions
Is Aleph Pro free?
The page opened on 18 Oct 2026 does not print a price. Access is an application. The open-source repository's SPDX field is MIT, and that README says core-team maintenance ended after 31 December 2025.
Is the public site still the open search box?
The host aleph.occrp.org loaded an Aleph Pro page with an application form. This listing did not open a search workspace.
Citations
07
Titled sources. These public pages are what the quotes on this listing come from.
Product
Aleph Pro
https://aleph.occrp.org/Documentation
Aleph repository
https://github.com/alephdata/alephDocumentation
Aleph Pro frequently asked questions
https://www.occrp.org/en/announcement/aleph-pro-frequently-asked-questions-on-the-future-of-occrps-investigative-data-platform/