Digital Public Goods in the Global South: What the DPG Alliance Registry Says About Open-Source Adoption

The Digital Public Goods Alliance reported in its 2025 ecosystem report that more than 220 digital public goods (DPGs) had been verified, and that the Alliance itself had reached 50 members. For anyone studying open-source software in development, that registry is the closest thing to a canonical list. It is also easy to misread. A registry entry certifies that a product meets a technical standard. It does not certify that anyone in the Global South is using it.
That distinction matters because the registry is routinely cited as evidence of adoption. Reading it carefully shows what it measures, what it leaves out, and where the evidence on actual uptake has to come from somewhere else.
What the registry actually certifies
A DPG, in the Alliance’s usage, is an open-source product, or open data, open AI model, open standard or open content, that advances the Sustainable Development Goals. To be listed, a nominated product is reviewed by the Alliance’s technical team against the DPG Standard, which has nine indicators: relevance to the SDGs, use of an approved open license, clear ownership, platform independence, documentation, a mechanism for extracting data, adherence to privacy and applicable laws, adherence to standards and best practices, and do-no-harm by design.
Two features of the process shape how the registry should be read. First, the review is documentary. Applicants supply evidence, such as a public link naming an approved license, and the reviewers check it against the indicators. Second, the Alliance’s submission guide does not require evidence of deployment or adoption. A product can qualify on the strength of its license, documentation and governance without a single government having put it into production.
DPG status is also time-limited. It lasts one year from approval, after which the product goes through an automatic review against the current version of the standard. The registry is therefore a living list of products that have recently passed a compliance check, not a historical record of everything that has ever been deployed.
Where adoption evidence does exist
Adoption figures appear on individual registry entries and in the maintainers’ own reporting, and they vary widely in quality. The best-documented case is DHIS2, the health information platform maintained from the University of Oslo. Its registry entry, licensed under BSD-3-Clause, states that ministries of health use it in more than 80 countries, 74 of them at national scale. DHIS2 received DPG status in November 2020 and was most recently reviewed in January 2025.
Those are maintainer-reported figures, and other sources give different counts for the same platform, which is what one would expect when definitions of “in use” and “national scale” are not standardized. DHIS2 is nonetheless an instructive example because it is a case where adoption is deep, long-running and visible in country health systems, rather than an artifact of listing.
For most registry entries, comparable evidence is thin or absent. The registry is a catalogue of candidates. Researchers who want to know whether a given DPG has changed how a ministry works need national case studies, procurement records and implementation evaluations, the kinds of sources the ICT4D literature has long relied on.
The sustainability gap the Alliance itself names
The Alliance’s own commentary is candid about what happens after a product is listed. In a November 2025 post on sustaining DPGs, its research director argues that adoption alone does not sustain value, and that most financing efforts target initial deployments while neglecting upstream maintenance of the open-source core. The same piece observes that many governments lack the structures needed to contribute back systematically, such as open source program offices, procurement policies or developer training pathways.
This is a familiar finding in ICT4D. Software that is free to license is not free to run. Hosting, security patching, localization, training and integration with national systems all cost money, and donor funding has historically favored new deployments over long-term upkeep. The older literature on open-source software in development reached much the same conclusion about community-contributed code that nobody was funded to maintain.
The funding environment sharpens the concern. The Alliance’s sustainability material notes that official development assistance fell in 2024 and was projected to fall further in 2025, and the OECD’s preliminary data for 2025 later showed a 23% decline in ODA from 2024. Products that depend on donor-financed deployments are exposed to that contraction in ways that products with domestic budget lines are not.
How to use the registry in research
Treated carefully, the registry is useful in three ways.
As a sampling frame. It gives a bounded list of open-source products with documented licenses and ownership, which is more than most software-in-development studies have had. A researcher can draw a sample of entries and then investigate deployments separately from the registry.
As a proxy for openness, not impact. An entry shows that a product’s license, data-extraction mechanism and documentation passed review. Whether openness translated into lower costs, local adaptation or reduced vendor lock-in is an empirical question the registry cannot answer.
As a time series with caveats. Counts of verified DPGs will rise and fall with nominations, renewals and the Alliance’s own outreach campaigns. A growing number may reflect a more active nomination pipeline as much as a larger open-source footprint in practice.
Contested points remain. Advocates argue that standardized criteria raise the quality bar for open digital infrastructure, while skeptics note that a certification regime can favor products with well-resourced maintainers who know how to navigate the application process. Neither claim is settled by the registry’s own data.
The practical takeaway for a literature review or a donor appraisal is to pair every registry citation with a second source that speaks to use: a ministry deployment report, an evaluation, or a maintainer’s published country list with its definitions stated. The registry establishes that a product is open and documented. Everything about whether it is adopted, sustained and useful has to be shown separately.