yente
Berlin, Germany
What it is
Yente is an open-source API for searching, retrieving, and matching people, companies, and other entities against watchlists. It uses the OpenSanctions database by default and can work with company registries or custom watchlists. Operators can add datasets, choose which OpenSanctions data to index, and set custom scopes through a manifest; custom datasets use line-based JSON feeds of FollowTheMoney entities. Yente checks for OpenSanctions updates hourly by default and reindexes when a new build is available. It can run on premises, with query data staying within the deployment context, and supports Elasticsearch and OpenSearch. The project provides Docker containers and example deployment configurations for Docker Compose and Kubernetes. Its 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 match limits are 100 entities per batch and 500 results per query. Yente is MIT-licensed. Commercial use of OpenSanctions data requires a data license; eligible non-commercial and exempt users may use the civic manifest. It provides health endpoints and supports OpenTelemetry metrics and traces.
For and against
For
- Searches and matches custom datasets and watchlists.
- Can run on premises within the deployment context.
- Supports Elasticsearch and OpenSearch backends.
- Includes health endpoints and OpenTelemetry support.
Against
- Commercial OpenSanctions data use requires a license.
- Match batches default to at most 100 entities.
- Match queries default to at most 500 results.
- Documented infrastructure includes substantial memory and disk needs.
The verdict
Yente offers configurable, self-hostable entity screening through an API, with deployment and monitoring options. Its default limits, infrastructure requirements, and OpenSanctions licensing terms are important considerations.
Who it suits
Yente may suit organizations building watchlist screening into API-based workflows or seeking an on-premises deployment. Teams should account for infrastructure needs and the data licensing conditions for commercial OpenSanctions use.
On the record
- API functions
- The API supports searching, retrieving, and matching FollowTheMoney entities.yente.followthemoney.tech · read 8 Oct 2026
- API limits
- Default configuration accepts at most 100 entities per match batch and returns at most 500 results per match query.yente.followthemoney.tech · read 8 Oct 2026
- Commercial data licensing
- The documentation says commercial use of OpenSanctions data requires a license subscription; non-commercial users and users exempt from commercial licensing may use the civic manifest.yente.followthemoney.tech · read 8 Oct 2026
- Commercial data use
- Commercial use of the OpenSanctions dataset requires a data license; the documentation says non-commercial users and exempt users can access OpenSanctions data directly.yente.followthemoney.tech · read 8 Oct 2026
- Custom datasets
- Users can add datasets, limit which OpenSanctions data is indexed, and define custom scopes through a manifest file.yente.followthemoney.tech · read 8 Oct 2026
- Data format
- Custom datasets must be line-based JSON feeds of FollowTheMoney entities.yente.followthemoney.tech · read 8 Oct 2026
- Data source
- By default, Yente fetches the OpenSanctions database, and it can also use other datasets such as company registries and custom watchlists.yente.followthemoney.tech · read 8 Oct 2026
- Data sources
- Yente provides access to OpenSanctions data by default and can also search and match company registries or custom watchlists.yente.followthemoney.tech · read 8 Oct 2026
- Data updates
- By default, Yente checks for updated OpenSanctions data hourly and reindexes when a new build is available.yente.followthemoney.tech · read 8 Oct 2026
- Deployment
- The project provides pre-built Docker containers and example Docker Compose and Kubernetes configurations.yente.followthemoney.tech · read 8 Oct 2026
- Infrastructure requirements
- The documentation estimates 800 MB of memory per Python service and 4–16 GB of memory plus 10–30 GB of disk for the Elasticsearch index.yente.followthemoney.tech · read 8 Oct 2026
- License
- Yente is released under the MIT License.yente.followthemoney.tech · read 8 Oct 2026
- Monitoring
- Yente provides /healthz and /readyz health endpoints and supports OpenTelemetry metrics and traces.yente.followthemoney.tech · read 8 Oct 2026
- On-premises
- Yente can run on-premises so customer query data stays within the deployment context.yente.followthemoney.tech · read 8 Oct 2026
- Privacy
- The documentation says an on-premises deployment can keep customer data from leaving the deployment context.yente.followthemoney.tech · read 8 Oct 2026
- Purpose
- Yente is an open-source screening API for searching, retrieving, and matching people, companies, and other entities against watchlists.yente.followthemoney.tech · read 8 Oct 2026
- Search backend
- Yente supports Elasticsearch and OpenSearch backends.yente.followthemoney.tech · read 8 Oct 2026
- Search backends
- Yente supports Elasticsearch and OpenSearch backends.yente.followthemoney.tech · read 8 Oct 2026
