01 Digital public goods

Digital public goods websites and portals

A digital public goods website has to speak to ministers, system integrators, developers and funders at once. Tailwebs builds these platform websites: clear explanations of what the platform does, adoption and partner pages, routes into documentation and community, multilingual content and accessible design. We built MOSIP's brand website and Marketplace, and eGov's brand websites (egov.org.in, with help on egov.global).

Book a callWhat the DPG Standard asks of your site
The eGov Foundation website home page

02 Four audiences

One open-source platform website, four audiences

Each audience gets its own route from the home page, so a minister and a developer both find what they came for without reading pages meant for someone else.

Illustrative · generic labels
Home pageWhat the platform does, in one sentence, then a route for each audience
  • Governments and ministriesWhat the platform does, where it is adopted, and how it is governed
  • System integratorsThe partner programme and the implementation guides
  • DevelopersDocumentation, repositories, releases and community
  • Funders and civil societyImpact, openness and who is accountable

Many platform sites start as developer sites. The route map adds what decision makers need without burying the docs.

03 The DPG Standard

What makes a platform a digital public good?

An open-source product, such as software, data, an AI system or a content collection, with an open licence, that meets the Digital Public Goods Alliance's DPG Standard. The Standard has nine indicators, and each one gives your website something to show.

  1. SDG relevance

    In plain terms
    The product shows how it advances the Sustainable Development Goals.
    What your website shows
    An impact page that names the goals and the evidence.

  2. Open licensing

    In plain terms
    It is released under an open licence.
    What your website shows
    The licence, named, with a link to the repository.

  3. Clear ownership

    In plain terms
    Who owns the product and its assets is clear.
    What your website shows
    Who owns and governs the platform, on a governance page.

  4. Platform independence

    In plain terms
    It does not lock users into a closed component.
    What your website shows
    An architecture page: what runs where, and what can be swapped.

  5. Documentation

    In plain terms
    Others can use and deploy it from the documentation.
    What your website shows
    A route into the documentation from every audience page.

  6. Non-PII data extraction

    In plain terms
    Non-personal data can be taken out in usable formats.
    What your website shows
    Where data export is explained, and in which formats.

  7. Privacy and applicable laws

    In plain terms
    It respects privacy and the laws that apply to it.
    What your website shows
    A privacy page for the site itself, and a plain page on how the platform treats data.

  8. Standards and best practices

    In plain terms
    It follows relevant open standards and good practice.
    What your website shows
    The standards the platform follows, named on its technical pages.

  9. Do no harm by design

    In plain terms
    Data privacy and security, and protection from harmful content and harassment.
    What your website shows
    A trust and safety page, linked from every page footer.

The accuracy rule we write by

Your site explains your status and links to your entry in the DPG Registry. It never implies that a deployment, a partner or the website itself is endorsed. Tailwebs claims no relationship with the Digital Public Goods Alliance.

Read the full DPG Standard on the Alliance's own site.

04 Adoption, partners and docs

How do we show adoption and keep it current?

Build the living parts of the site from structured data your team edits once, so country, partner and deployment pages stay in step as adoption grows.

  • Adoption pages

    What it does

    One page per country or state, with its deployment and status, drawn from the same records.

  • Partner directory

    What it does

    A filterable directory of partners and system integrators, by country and by capability.

  • Deployment maps

    What it does

    A map drawn from the same records as the adoption pages, so the two always agree.

  • Documentation portal

    What it does

    Connected through shared navigation and design, whether the docs live in a separate tool or in the same site.

  • Events and community

    What it does

    Event pages, community calls and routes for new contributors, each kept by a named owner.

  • Microsites

    What it does

    A new module or campaign gets its own pages, inside the same design and navigation.

The build is custom software development, and every template is designed by our UI/UX design team. To score your current site first, take the research website checklist.

05 What we have built

Websites for digital public goods organisations

Brand websites for two organisations behind digital public goods, and the MOSIP Marketplace. Our work lifted engagement by 30% for MOSIP and 50% for eGov.

  • 01/03

    MOSIP

    The MOSIP brand website, for an ecosystem that serves countries

    Engagement up 30%

    The full brand-website process: information architecture, strategy, content planning, design, development and launch.

  • 02/03

    MOSIP Marketplace

    A live portal where adopting countries find compliant devices and software

  • 03/03

    eGov Foundation

    eGov's brand websites

    Engagement up 50%

    We built egov.org.in, live at egov.org.in, and helped on egov.global.

Read what MOSIP said about working with us in our Clutch reviews. More sites for organisations that publish research and policy work: research website design.

06 Scope and budget

What a DPG website costs, in short

The research website range applies.

  • The Research Website range: ₹6–20 lakh ($8,000–25,000) over 8–16 weeks, depending on page types, languages and integrations.
  • Accessibility, the planning method and phasing a build to a grant cycle are on policy and research.
  • Apps, chatbots and portals for government, beyond the website, are on government and digital public infrastructure.

07 FAQ

Questions about DPG websites.

How is a website for a digital public good or digital public infrastructure different from a company website?
Its main buyers are governments rather than customers, so it has to explain adoption, governance and openness, not sell features.
Does the DPG Standard apply to our website?
The Standard is written for the core product; its scope is on digitalpublicgoods.net/standard. Your site should still explain your status, link to your entry in the DPG Registry and never imply an endorsement.
Can you link our main site with our DPG documentation portal?
Yes, we connect the two through shared navigation and design, whether docs live in a separate tool or in the same site.
Can adoption and partner pages update automatically?
Yes, we build them from structured data your team edits once, so country and partner pages stay in step.
Do you build or contribute to the DPG software itself?
This service covers the websites and portals that present a digital public good, not the DPG software itself.
How much does a DPG website cost?
It follows our research website range: ₹6–20 lakh ($8,000–25,000), depending on page types, languages and integrations.