Digital Public Goods: Definition & Recognition

Updated 4 November 2026 · Standard formula, shown below

Digital public goods are open-source software, open data, open artificial intelligence models, open standards, and open content that adhere to privacy and other applicable laws and best practices, do no harm, and help attain the Sustainable Development Goals. Recognition as a digital public good is granted through an assessment process against a defined set of standards, most notably by the Digital Public Goods Alliance. This article explains what qualifies, how the recognition process works, and why it matters.

Background: The Shift Toward Open Digital Infrastructure

The term “digital public good” gained prominence in 2017 when the United Nations Secretary-General’s High-Level Panel on Digital Cooperation recommended a definition to guide global digital cooperation. The panel proposed that digital public goods be open-source software, open data, open AI models, open standards, and open content that respect privacy and do no harm. This definition was designed to encourage digital solutions that can be freely used, adapted, and shared, particularly to address challenges in developing countries.

The concept builds on the older idea of public goods in economicsâ€”goods that are non-rivalrous and non-excludable, such as clean air or public parks. Digital public goods extend this idea to the digital realm, where the marginal cost of sharing is near zero. The Digital Public Goods Alliance (DPGA), a multi-stakeholder initiative launched in 2019, operationalizes the definition by maintaining a registry of recognized digital public goods and promoting their use.

What Qualifies as a Digital Public Good?

To qualify, a project must meet the DPGA’s nine indicators, which are grouped into three categories:

Open-source software: The source code must be publicly available under an approved open-source license (e.g., MIT, Apache 2.0, GPL). The project must also have a public repository, clear documentation, and a mechanism for community contributions.
Open data: Data must be released under an open license (e.g., CC BY, ODbL), be machine-readable, and have clear metadata. It must also respect privacy and security, with no sensitive personal data included.
Open AI models: Model weights, training code, and evaluation metrics must be openly available. The model should be documented with datasheets, and any biases or limitations should be disclosed.
Open standards: Standards must be developed through an open, consensus-based process and be freely available for implementation.
Open content: Content (e.g., educational materials, health guides) must be licensed under an open license and be available in accessible formats.

Additionally, all digital public goods must adhere to the following principles:

Do no harm: The project must not facilitate violence, terrorism, or illegal activities, and must respect human rights.
Privacy: The project must comply with applicable privacy laws and best practices, including data minimization and user consent.
Contribute to the SDGs: The project must explicitly map to at least one of the 17 Sustainable Development Goals, such as quality education (SDG 4), good health (SDG 3), or decent work (SDG 8).

How Recognition Works: The DPGA Assessment Process

Recognition is not automatic; it requires a formal application and review. The process, managed by the Digital Public Goods Alliance, involves the following steps:

Submission: The project owner submits a nomination form on the DPGA website, providing details about the project, its license, and its alignment with the SDGs.
Screening: The DPGA secretariat conducts an initial screening to ensure the submission is complete and the project is actively maintained.
Technical review: A team of reviewers (including DPGA staff and external experts) evaluates the project against the nine indicators. This includes checking the license, repository, documentation, and community governance.
Decision: The DPGA makes a decision to approve or reject. If approved, the project is added to the public registry of digital public goods.
Monitoring: Recognized digital public goods are reviewed periodically to ensure they continue to meet the standards. If a project becomes inactive or violates the criteria, it may be removed.

The review typically takes several weeks. The DPGA publishes the registry online, and anyone can search it by name, category, or SDG.

Common Misconceptions and Challenges

One common misconception is that “open source” automatically means “digital public good.” While open source is a prerequisite, it is not sufficientâ€”the project must also meet the do-no-harm, privacy, and SDG contribution criteria. For example, a surveillance tool that is open source would not qualify because it could cause harm.

Another challenge is that many projects fail the privacy indicator. Even if a project is open source, it may collect excessive user data or lack a clear privacy policy. The DPGA requires evidence of compliance with privacy laws like GDPR or equivalent standards.

Sustainability is also a recurring issue. Many projects are maintained by small teams or volunteers, and the DPGA requires evidence of long-term maintenance plans. Projects that are abandoned or have no clear governance structure are often rejected.

Why Recognition Matters: Benefits and Use Cases

Recognition as a digital public good provides several tangible benefits:

Visibility: The registry is used by governments, NGOs, and international organizations to find vetted digital solutions. For example, the UN and its agencies often reference the registry when procuring technology.
Funding: Many donors and foundations prioritize funding recognized digital public goods. The DPGA itself has a fund to support scaling.
Collaboration: Recognition facilitates partnerships with other organizations, including the private sector and academia.
Trust: The DPGA’s assessment provides a seal of approval that helps users trust the software or data.

Concrete examples of recognized digital public goods include:

OpenMRS: An open-source electronic medical record system used in over 70 countries.
Kolibri: An offline learning platform for low-resource environments.
OpenStreetMap: A collaborative open map of the world.
TensorFlow: An open-source machine learning framework (though its recognition is debated due to corporate control).

Alternatives and Related Concepts

Digital public goods are often confused with other concepts:

Open-source software: This is a subsetâ€”all digital public goods are open source, but not all open-source projects are digital public goods.
Public digital infrastructure: This refers to large-scale systems like identity, payments, and data exchange platforms that are built on digital public goods. Examples include India’s Aadhaar or the Modular Open Source Identity Platform (MOSIP).
Digital commons: A broader term that includes any shared digital resource, not necessarily meeting the DPGA’s criteria.

Frequently Asked Questions

What is the difference between open source and a digital public good?

Open source is a licensing and development model. A digital public good is an open-source project that also meets specific standards for privacy, do-no-harm, and contribution to the Sustainable Development Goals. For example, an open-source game may be open source but not a digital public good if it doesn’t contribute to the SDGs.

Who can apply for recognition?

Any individual, organization, or company can apply, as long as the project is publicly available and actively maintained. There is no fee for the assessment, but the project must meet all nine indicators.

How long does recognition last?

Recognition is not permanent. The DPGA reviews listed projects periodically, typically every one to two years. If a project changes its license, becomes inactive, or violates the criteria, it can be removed from the registry.

Can proprietary software be a digital public good?

No. By definition, a digital public good must be open source, meaning the source code is freely available for use, modification, and distribution. Proprietary software does not meet this requirement.

Does recognition guarantee funding or government adoption?

No. Recognition is a mark of quality, but it does not guarantee funding or adoption. It increases visibility and credibility, which can help secure funding and partnerships, but the project still needs to demonstrate its value and sustainability.

How to Get Your Project Recognized: Practical Steps

If you want to get your project recognized, follow these steps:

Review the criteria: Read the DPGA’s nine indicators and ensure your project meets each one. Pay special attention to privacy and do-no-harm.
Prepare documentation: Ensure your repository has a README, contributing guidelines, and a license file. Document how your project contributes to specific SDGs.
Submit the nomination: Fill out the online form on the DPGA website. Be thorough and provide evidence for each indicator.
Respond to feedback: The review team may ask for clarifications. Respond promptly and make any necessary changes.
Maintain the project: After approval, continue to update the project and report any major changes to the DPGA.

Common reasons for rejection include missing license, lack of privacy documentation, or unclear SDG alignment. Address these before applying to avoid delays.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.