GCRI · Digital Public Infrastructure
Dependencies and consequences
Digital public infrastructure depends on electricity, telecommunications, cloud computing, cryptography, skilled staff and public trust, and a growing range of services depend on it in turn. This page maps those links, shows how failures in DPI travel into social and economic harm and names the platforms across the Consortium that study, govern or finance the connected systems.
- STEM methods
- 6
- Canonical methods this field applies
- Topics
- 8
- Subject pages in the field
- Counterparts
- 5
- Platforms in shared fields across the network
- Report series
- 2
- Reports series it contributes to
The layers underneath.
Power and connectivity
Data centres, networks and devices need power and telecommunications. Rural and low-income areas often have the least reliable access.
Cloud, software and cryptography
Hosting platforms, software suppliers and cryptographic keys. Compromise or loss of any of them can stop services. See Cybersecurity and Digital Resilience.
People and trust
Skilled public servants, clear legal mandates and public confidence. Systems fail when people distrust or cannot use them.
Field overview.
The screen a team would use to follow this subject: its measures, states and decisions. Names are examples and values are illustrative.
How failure travels outward.
Social protection increasingly relies on digital identity to verify eligibility and on digital payments to deliver transfers. An authentication failure or payment outage can delay benefits for people with no savings to fall back on. Health systems use identity and data exchange for records, prescriptions and insurance claims. Tax, licensing, land registration and voting registers may all draw on the same identity foundation.
Private services build on DPI too. Banks use digital identity for account opening; merchants rely on interoperable payments; lenders use consented data sharing. Failures therefore reach markets and livelihoods as well as public services. The financial transmission of payment failures is studied at Payments and Market Infrastructure and Financial Cyber and Operational Resilience at The Global Risks Alliance (GRA).
Typical chains of failure.
- 01
Identity outage
An authentication service fails, blocking access to benefits, health records and bank accounts at the same time.
- 02
Exclusion at enrolment
People without documents or with biometric difficulties cannot enrol, and lose access as paper alternatives are withdrawn.
- 03
Data breach
A breach of a central register exposes many people to fraud and erodes trust in every service that uses it.
- 04
Vendor lock-in
A proprietary platform raises prices or fails, and the state cannot migrate quickly because interfaces and data formats are closed.
How links are analysed, and who decides.
Dependency analysis uses data engineering, interoperability and stewardship and cybersecurity and cryptography, with stated assumptions. Decisions on DPI belong to governments and competent authorities; governance dialogue is convened at AI and Digital Governance at The Global Risks Forum (GRF).
Questions and answers.
Is a dependency map a forecast?
Why are paper alternatives part of resilience?
Are national systems assessed by name?
Contribute evidence from this page.
Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- EmailGateway GW-GCRISend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Bring a method, a dataset or a question.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.