Wikidata Platform
| Group: | Product |
| Team: | Amy Tsay (Director of Product) Brandon Tracy (Lead Product Manager) |
| Since: | August 19th, 2025 |
The Wikidata Platform team is shaping the future of how users access and query Wikidata at scale. Our goal is to maintain stable, reliable and sustainable data access for Wikidata now and into the future.
Mission
[edit]Our mission is to sustain, develop, and evolve the query platform for Wikidata, one of the world’s largest linked open knowledge graphs. Wikidata facilitates much of the structure of Wikipedia content and contributor activities, making an impact on billions of users across 300+ languages. It also is a critical resource for libraries, universities, and other technology platforms. We enable this global knowledge ecosystem through robust data access capabilities that serve both our internal teams and the public. This includes access to data for editing workflow support, research, feature development, and advancing artificial intelligence responsibly.
What we do
[edit]The Wikidata platform and the Wikidata Query Service (WDQS) are fast approaching the upper limits of their technical capacity. As the number of users, requests, and datapoints in the knowledge graph increase, the need for more robust data access capabilities grows. To protect and improve upon the experience members of the Wikidata and Wikimedia communities have become accustomed to, the Wikidata Platform team will strive to improve and maintain the performance and stability of the service. We do this through:
- Delivery, development, and maintenance of Wikidata query platform products and services.
- Defining and driving a technical architecture that can maintain stable, reliable and sustainable query systems.
Currently, the primary means of querying Wikidata is via the Wikidata Query Service, where editors, reusers, toolbuilders, and researchers can query Wikidata using SPARQL. In taking on the above mentioned responsibilities, we support the Wikimedia movement by promoting the distribution of all the world's knowledge. We organize our efforts through a prioritization model that evaluates criteria such as impact and alignment with strategic objectives.
Who we serve
[edit]We support the Wikimedia movement and open-knowledge communities at large. We believe this can be represented in three high-level categories:
- Wikidata Contributors & Consumers - As we deepen our understanding of our users and improve our reporting telemetry, we expect this list to grow. Distinct personas within this category include:
- Mission-aligned reusers using Wikidata’s data to build applications, services, and AI models.
- Contributors to Wikimedia Foundation projects, including editors of Wikipedia, Wikifunctions, etc.
- Researchers and other academic users
- Technical contributors of Wikidata
- Wikimedia Deutchland (WMDE) - WMDE is responsible for the end-to-end user experience of Wikidata, building capabilities for their users on the Wikidata Platform. This includes community governance and software development for Wikibase and the Wikibase Cloud. It includes building custom views for WDQS that are tailored to their communities' needs, and more broadly building applications and APIs on the Wikidata Platform to enable their users to interact with, retrieve and edit items and statements on Wikibase instances. As a main consumer and audience of the Wikidata Platform, WMDE's product needs help to guide prioritization for our team. Above all, we share a goal to support the growth and stability of Wikidata and collaborate closely to ensure this goal is met on behalf of the broader community.
- Wikimedia Foundation (WMF) - Across the Wikimedia Foundation, teams such as Wikimedia Enterprise, Core Experiences, and Abstract Wikipedia have dependencies on the Wikidata platform and/or query service. These teams engage with us on existing and proposed collaborations. We consider product requirements of established and potential use cases as we make platform improvements, understanding that we serve the same mission and many of the same customers.
Team
[edit]Here you can find a list of our team members, their roles, and areas of expertise.
Our team is still growing; this page will be updated as new members join.
Product
[edit]-
Amy Tsay (Director of Product) -
Brandon Tracy (Lead Product Manager)
Engineering
[edit]-
Gabriele Modena (Technical Lead)
-
David Santamaria (Engineering Manager)
Communications
[edit]-
Benedict Udeh (Movement Communications Specialist)
Program Management
[edit]-
Zaree Singer (Program Manager)
Meeting Schedule
[edit]The Wikidata Platform team and key partners across WMF and WMDE meet regularly to share updates, host discussions, and align on work plans. Our team spans many time zones, so we rely on asynchronous work to supplement our schedule of face-to-face touch points. Many recurring mechanisms, such as sprint planning, retrospectives, and engineering stand ups, will begin in 2026 when more members are brought into the team. A full list of our meetings, along with the series status (Upcoming, Live, Paused), is maintained in our meeting schedule.
How to contact us
[edit]Before reaching out to the team through one of the below mechanisms, review our user stories to make sure you're going through the correct channels.
- Wikidata Platform team Phabricator board (see our Best Practices before submitting a request).
- If you think you found a bug and want input from the community and WDP team before opening a request on Phabricator, use our Report a technical issue page.
- (starting in January 2026) For a more open-ended forum for discussion, attend our Office Hours.
Upcoming
[edit]Check out our team page again in the coming weeks for the following additions:
- FAQs for common problems
- Sprint retrospective archives
- Roadmaps and team product strategy