Enlighta Sanctions Screening vs yente
Enlighta Sanctions Screening
enlighta.comyente
yente.followthemoney.techSide by side
| Figure | Enlighta Sanctions Screening | yente |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Linux | — | Yes |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 0 | 0 |
| Spec score · Sanctions Screening Software | 7.6 (#7) | 7.0 (#18) |
| Headquarters | San Ramon, California, United States | Berlin, Germany |
| Purpose | Enlighta Spice automates sanctions and politically exposed person (PEP) screening to support regulatory compliance and reduce third-party risk. | Yente is an open-source screening API for searching, retrieving, and matching people, companies, and other entities against watchlists. |
In their own words
Enlighta Sanctions Screening
Enlighta Sanctions Screening automates sanctions and politically exposed person screening for enterprise vendor and third-party risk programs. It checks individuals, entities, and countries against global watchlists, including UN, EU, DFAT, and OFAC lists plus other law-enforcement sources. Built-in verification addresses Anti-Money Laundering and Counter-Terrorist Financing compliance. Results can enter vendor-risk workflows to update vendor status and risk assessments, trigger alerts, identify expired certifications, and preserve an auditable evidence trail. The platform supports ongoing monitoring and connections through REST APIs, SOAP APIs, or custom scripts. Named integrations include SAP Ariba, Coupa, Salesforce, Oracle, ServiceNow, Workday, Microsoft, and Jira. Assessments and workflows can be tailored without code. Security descriptions include end-to-end encryption, multi-tenant data separation, native, LDAP, and SSO authentication, access restrictions, backups, high availability, and uptime SLAs. It runs through web and API access. Pricing is on request.
yente
Yente is an open-source API for searching, retrieving, and matching people, companies, and other entities against watchlists. It uses OpenSanctions data by default and can work with company registries or custom watchlists. Operators can add datasets, choose which OpenSanctions data to index, and set scopes in a manifest; custom datasets must be line-based JSON feeds of FollowTheMoney entities. By default, Yente checks for updated OpenSanctions data hourly and reindexes when a new build is available. It can run on premises, keeping customer query data within the deployment context, and supports Elasticsearch and OpenSearch. The project provides Docker containers and example Docker Compose and Kubernetes configurations. Documentation estimates 800 MB of memory per Python service, plus 4–16 GB of memory and 10–30 GB of disk for the Elasticsearch index. Default matching limits are 100 entities per batch and 500 results per query. Yente is released under the MIT License. Commercial use of OpenSanctions data requires a data license subscription; non-commercial and exempt users may access the civic manifest. It provides health endpoints and supports OpenTelemetry metrics and traces. The project welcomes issue reports and contributions on GitHub.