Jump to content

Wikimedia Enterprise/FY26-27

From Meta, a Wikimedia project coordination wiki
Wikimedia Enterprise
Building new opportunities for both revenue generation and free knowledge dissemination through partnerships and earned income.
enterprise.wikimedia.com
Project
Technical

FY26-27 Commercial Partnerships Division

[edit]

Since the end of 2025 (annual plan), the Wikimedia Enterprise and Technology Partnerships teams have started operating as a single division called Commercial Partnerships. This repositioning of our division was done because our scope over the past four years has expanded. We no longer solely offer paid services to a few large-scale reusers; we also manage technology partnerships with SMEs, non-profits, and other organizations. By bringing these functions together under Advancement, we can better coordinate our commercial and technical relationships. The external product name will remain Wikimedia Enterprise.

Wikimedia Enterprise is a service for high-volume re-users of Wikimedia content. Enterprise provides tools for high-volume data access to companies, mission-aligned reusers, and community developers. It offers dedicated customer support, service level guarantees (SLAs), and professional consulting to partners who've signed commercial agreements. The Wikimedia Enterprise service is developed and maintained by the Commercial Partnerships division, comprising the Wikimedia Enterprise team and the Technical Partnerships team.

FY26-27 is a pivotal year for the Commercial Partnerships division. At this point, after five years of working on the Enterprise product, Commercial Partnerships has become profitable and has paid back its initial investment in full. It has also secured buy-in and trust from both Wikimedia Foundation stakeholders and community stakeholders, which is an important reversal in both internal and external perceptions compared to when Enterprise first launched five years ago. The importance of Enterprise as a service that ensures the sustainability of the Wikimedia projects is widely understood. It's against this backdrop that Enterprise is taking FY26-27 as an important year to expand its user base into the mid-market segment and to position itself more firmly as an integral part of the Wikimedia Foundation's strategy to achieve the WMF mission.

Objective 1: Ensure a seamless path from community infrastructure to Enterprise APIs for commercial reusers

[edit]

Key results

[edit]
  1. Ease of Migration: Reduce the volume of known out-of-policy commercial public dependencies by 95%
  2. Infrastructure Accommodation: Decrease cost per use by 5% for each additional user.

Our first objective for the year, tied to this increased positioning of the Enterprise service as part of the Wikimedia Foundation's core offering, is to ensure a seamless path from community infrastructure to Enterprise APIs for commercial reusers. Many commercial entities currently rely on public, out-of-policy dependencies. This creates an unnecessary load on community resources. We'll be working with Product and Technology to develop a Unified Developer Front Door so that any reuser can easily understand what APIs and services best fit their user case. In parallel, Commercial Partnerships will redevelop the Enterprise website to ensure developers coming from the Unified Front Door understand the Enterprise APIs as part of the overall Wikimedia Foundation offer, while still differentiating the Enterprise services as commercially focused. Migration and onboarding documentation will be expanded, and our SDKs will be updated to serve more developers working in specific tech stacks. In FY26-27 we're also executing a full Enterprise website redesign: this will refresh the branding to exude legitimacy and trust through relational clarity and specialist skills. The redesigned visual identity for Wikimedia Enterprise is also a prime opportunity for a rework of the 'product packaging' for Enterprise: Commercial Partnerships will reconsider how the APIs and their features are presented, and what features are available at different pricing tiers. Pricing will also become more transparent, allowing leads to understand more quickly what price point their use case falls into, streamlining the contract process.

The reworked website and product packaging will be supported by a new outbound marketing campaign directed at the mid-market customer segment. This marketing campaign will highlight the features that make Wikimedia Enterprise services the better choice over consuming third-party dumps or web-scraping Wikimedia projects.

To incentivize switching to Wikimedia Enterprise, Commercial Partnerships will roll out new features and APIs that have been highly requested by different stakeholders, contributing both to growing revenue and to ensuring a seamless path from community infrastructure to Enterprise APIs. Pageviews APIs will be launched in FY26-27, providing essential insights for reusers into user and content trends across Wikimedia projects, strengthening the suite of credibility signals reusers have at their disposal to work on the integrity of the content coming through Enterprise APIs. Structured Contents continues to be recognised as a big value-add for using Enterprise APIs: Structured Contents features will continue to be prioritised, and its access will be expanded to Batch and Realtime endpoints. Commercially relevant historical lookbacks will also be released in FY26-27, a service that partners have repeatedly requested. Wikimedia Commons, another hotly requested dataset, will become available for ingestion through Wikimedia Enterprise in FY26-27. Lastly, a way to query Wikimedia project content through an Enterprise Search API will also get rolled out in FY26-27, adding another dimension to how reusers can discover and access Wikimedia project data.

We'll deem this objective successful if we can measure at least 80% adherence to the new pricing model across all new contracts.

Objective 2: Ensure reuse works for our people, platforms, and partners

[edit]

Key results

[edit]
  1. Increase Value of Content Reuser Partnerships: Establish baseline net reuser value for top 5 strategic partners
  2. Implement a process or platform to disseminate strategic insights between partners and WMF teams at regular intervals
  3. Measurably increase the reuse value of 2 strategic partners through cross-departmental planning and prioritization of projects

Our second objective focuses on ensuring reuse works for our people, platforms, and partners. We need a clear way to quantify the value of these relationships. We will establish a baseline 'net reuser value' for our top five strategic partners. This value should determine the impact of a reuser on the Wikimedia ecosystem: e.g. is this reuser diverting pageviews (and derived contributions) away from Wikimedia project, or are they contributing to referral traffic/pageviews? Taking these and other factors into account into the 'net reuser value' will allow Commercial Partnerships to make more informed decisions towards pricing and partnership strategies. Here, too, Commercial Partnerships will only work more closely with other teams in WMF in FY26-27: we will implement a process or platform to disseminate strategic insights between partners and WMF teams at regular intervals. Success for this objective will be achieved when we measurably increase the reuse value of 2 strategic partners through cross-departmental planning and prioritization of projects.

Objective 3: Grow revenue to resource the future

[edit]

Key Results

[edit]
  1. Reach $18.5M annual contracts
  2. Ensure all of Commercial Partnerships requirements are integrated into the new policy
  3. Execute a new outbound marketing campaign focused on customers 50k and $1M
  4. Achieve 80% adherence to the new pricing model for all new contracts

Our final objective is to grow revenue to resource the future, with a target of reaching $18.5M in annual contracts. An important incentive to switch from foundational APIs to Enterprise infrastructure will come from our cross-departmental initiative to put more focus on appropriate commercial reuse. Across the “Unified Developer Front Door” work and the Legal team's revisiting of WMF's terms and policies, in FY26-27 we're figuring out how to tweak our narrative towards reusers. Commercial Partnerships is an important stakeholder in the Legal Team's FY26-27 review of WMF's current licenses and legal policies to ensure we have the right standards and structures to protect the knowledge commons from exploitation. This includes checking throughout the project that the Enterprise principles and free access guarantees for mission-aligned partners are safeguarded.

Of course, all of the work mentioned above to improve the Enterprise product and services, and to streamline the journeys from community infrastructure to Enterprise APIs also contribute to this revenue objective. Lastly, Commercial Partnerships is keen on exploring the expansion of its services beyond Wikimedia project datasets, to external datasets that share similar data structures, face similar infrastructure strain challenges, and are mission- and vision-aligned. With many projects that contribute to the open knowledge ecosystem looking to Wikimedia Enterprise as a solution to the need for access-based business models that ensure the content itself stays in the public domain, Commercial Partnerships wants to seize this opportunity to explore how partnerships with these external platforms can be mutually beneficial.

These OKRs outline our practical steps for the coming year: migrate heavy commercial users to supported APIs, measure the value of our partners accurately, and expand our offerings to meet our revenue targets.