FinScan vs yente
FinScan
finscan.comyente
yente.followthemoney.techSide by side
| Figure | FinScan | yente |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Linux | — | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Sanctions Screening Software | 7.4 (#10) | 7.0 (#18) |
| Deployment | The product supports SaaS, on-premise, and hybrid deployment options. | The project provides pre-built Docker containers and example Docker Compose and Kubernetes configurations. |
| Headquarters | FinScan lists its headquarters at 790 Holiday Drive, Pittsburgh, Pennsylvania 15220-8127, United States. | Berlin, Germany |
| Purpose | FinScan provides AML and sanctions screening with KYC checks, data quality tools, and precision matching. | Yente is an open-source screening API for searching, retrieving, and matching people, companies, and other entities against watchlists. |
Plans
In their own words
FinScan
FinScan is an AML and sanctions-screening platform for organizations that need KYC checks, data quality controls, and precision matching. It screens sanctions, politically exposed persons, adverse media, payments, and watchlists. Before screening, its data-quality tools identify missing, inconsistent, or duplicate customer information. FinScan says its matching technology can reduce false positives by up to 80%. Deployment options include SaaS, on-premise, and hybrid setups. Processing supports real-time screening and batch work involving hundreds of millions of records. An open API can send results to web-services-enabled applications. Payment screening covers SWIFT, ISO 20022, SEPA, FedNow, Fedwire, ACH, and instant-payment flows. The product supports API access, batch screening, transaction screening, PEP screening, ongoing monitoring, and custom list management. Listed controls include AES-256 encryption at rest, TLS 1.3 in transit, role-based access control, and immutable audit logs. FinScan identifies banking, insurance, fintech, healthcare, real estate, wealth management, and government among its industries. It runs through API, self-hosted, and web platforms. Pricing is on request, with a demo required.
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.