yente
yente.followthemoney.tech
- Free plan
- Linux
- Web
- API
- Self-hosted
What yente is
yente is an open-source API for screening people, companies, and other entities against watchlists. It searches, retrieves, and matches FollowTheMoney entities, using OpenSanctions data by default while also allowing company registries and custom watchlists. Operators can add datasets, select which OpenSanctions data to index, and set custom scopes in a manifest file. Custom datasets need to be line-based JSON feeds of FollowTheMoney entities. By default, yente checks for OpenSanctions updates 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 sample Docker Compose and Kubernetes configurations. 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. The MIT-licensed software is free; commercial use of OpenSanctions data requires a data license.
Who it suits
yente suits teams building watchlist screening into their systems through an API, including organizations that need PEP screening, batch screening, ongoing monitoring, or custom list management. Its on-premises option may fit teams that want query data to remain within their deployment context.
Good to know, and what to watch
- Searches and matches OpenSanctions and custom datasets
- Can run on premises
- Supports Elasticsearch and OpenSearch
- Includes Docker and Kubernetes deployment examples
- Provides health endpoints and OpenTelemetry metrics and traces
- Commercial use of OpenSanctions data requires a license
- Match batches default to 100 entities
- Match queries return at most 500 results by default
- Transaction screening is not included
The verdict
yente offers a configurable, self-hostable screening API with options for custom datasets and search backends. Teams should account for its documented infrastructure needs, default match limits, and OpenSanctions licensing requirements for commercial data use.
What the maker publishes
- API functions
- The API supports searching, retrieving, and matching FollowTheMoney entities. source
- API limits
- Default configuration accepts at most 100 entities per match batch and returns at most 500 results per match query. source
- 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. source
- 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. source
- Custom datasets
- Users can add datasets, limit which OpenSanctions data is indexed, and define custom scopes through a manifest file. source
- Data format
- Custom datasets must be line-based JSON feeds of FollowTheMoney entities. source
- Data source
- By default, Yente fetches the OpenSanctions database, and it can also use other datasets such as company registries and custom watchlists. source
- Data sources
- Yente provides access to OpenSanctions data by default and can also search and match company registries or custom watchlists. source
- Data updates
- By default, Yente checks for updated OpenSanctions data hourly and reindexes when a new build is available. source
- Deployment
- The project provides pre-built Docker containers and example Docker Compose and Kubernetes configurations. source
- Founded
- 2023 source
- Headquarters
- Berlin, Germany source
- 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. source
- License
- Yente is released under the MIT License. source
- Monitoring
- Yente provides /healthz and /readyz health endpoints and supports OpenTelemetry metrics and traces. source
- On-premises
- Yente can run on-premises so customer query data stays within the deployment context. source
- Privacy
- The documentation says an on-premises deployment can keep customer data from leaving the deployment context. source
- Purpose
- Yente is an open-source screening API for searching, retrieving, and matching people, companies, and other entities against watchlists. source
- Search backend
- Yente supports Elasticsearch and OpenSearch backends. source
- Search backends
- Yente supports Elasticsearch and OpenSearch backends. source
- Self-hosting
- Yente can run on premises as a KYC appliance so customer data stays within the deployment context. source
- Support and contributions
- The project welcomes issue reports and contributions on GitHub. source
Checked against the maker's pages on 8 Oct 2026.