Skip to content

GCRI · Digital Public Infrastructure

Public cloud and concentration

Many public digital systems run on commercial cloud platforms or a few national data centres. This brings scale and capability, and it creates dependence on a small number of providers, questions of jurisdiction over data, and shared points of failure. This page sets out how hosting choices shape the risk of public digital infrastructure, how concentration is measured, and what evidence serves the governments and regulators who make these choices.

01رجسٹر

Public cloud and concentration on the record.

02The question

Public cloud and concentration: how the risk develops.

Vendor dependency and continuity. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.

طریقۂ کار

A few providers host much

Cloud markets are concentrated, so many public services depend on the same providers and regions.

طریقۂ کار

Jurisdiction follows the provider

Foreign providers may be subject to laws that compel data access, raising sovereignty concerns for sensitive public data.

طریقۂ کار

Exit is hard

Proprietary services and data transfer costs make it difficult to move systems between providers or back in-house.

طریقۂ کار

Concentration is a shared vulnerability

An outage or compromise at one provider or region can disrupt many public services at once.

03نگرانی

DPI service health.

وہ اسکرین جو ایک ٹیم اس موضوع کی پیروی کے لیے استعمال کرے گی: اس کے پیمانے، حالتیں اور فیصلے۔ نام مثالیں ہیں اور اقدار توضیحی ہیں۔

DPI service health

Public cloud and concentration · Payment switch · Today

  • Transactions today
    3,217,1006فعال
  • Authentication success, %
    98.1معمول
  • Availability, % this month
    99.60معمول
  • Grievances open
    562نگرانی کریں
All rails operationalGCRI · Digital Public Infrastructure

Throughput

Rails

Identity verify1380.8معمول
Instant payment5670.4معمول
ڈیٹا کا تبادلہ3651.1Degraded
Offline fallbackلاگو نہیںلاگو نہیںStandby
DPI service health: the screen's structure, terms and states for Public cloud and concentration.Example names and illustrative values; a design, not a record or a live system.
04Across the domains

Concentrated cloud services are a common mode for public services.

Findings are designed for the Strategic Systems series. DORA (2022) introduced oversight of critical providers to finance; the Global Centre for Risk and Innovation (GCRI) rates no provider.

  • Dependency maps under terms.
  • Exit plan evaluations.
05Methods and evidence

How public cloud and concentration is modelled, measured and tested.

The model, its assumptions, its data and its uncertainty, in the form a scientist or engineer would check. Structures follow published methods. The values drawn are illustrative, not findings.

Datasets and provenance

The data classes behind public cloud and concentration and what is recorded about each before it is used.

Data classProvenance recordedResolution statedLicence checked
Satellite imagery, optical and radarsensor, processing level, acquisition datepixel size and revisitper scene
Reanalysis and climate model outputmodel, experiment, member, versiongrid and time stepper release
In-situ sensors and gaugesstation, instrument, calibration recordpoint and sampling rateper network
Population and asset exposuremethod, vintage, input sourcescell size and unitper release
Boundaries and reference geographyproducer, edition, datescaleper edition
نسب
W3C PROV record from source to figure
اصول
FAIR: findable, accessible, interoperable, reusable
Gaps
shown as missing, never filled silently
Data classes and the provenance fields recorded for each; a dataset is listed by name only once its licence admits the use.
FAIR guiding principles · GO FAIR and FORCE11W3C PROV · World Wide Web ConsortiumGuidance on consistent treatment of uncertainties · IPCCCEOS Analysis Ready Data · Committee on Earth Observation Satellites
06اشاریے

What is measured, and how well.

Each indicator carries its unit, its cadence, the kind of source behind it and the evidence label a value would carry. No values are shown: a programme supplies them under its own authority.

IndicatorUnitCadenceSource typeلیبل
Public workloads by hosting typepercent of workloadsper assessmentGovernment inventoriesDECLARED
Share of public cloud spend with the largest providerpercentannualProcurement dataمشاہدہ شدہ
Critical systems with tested exit planspercentper assessmentExit plan recordsرپورٹ شدہ
Sensitive data hosted under domestic jurisdictionpercent of sensitive datasetsper assessmentData classification recordsDECLARED
Provider outages affecting public servicescount and hoursannualIncident recordsمشاہدہ شدہ
Sovereign cloud offerings availablecountper assessmentMarket reviewرپورٹ شدہ
07ماخذات

Where the evidence comes from.

Named public datasets and institutional records, each with its licence class. Sources by agreement are used only under their terms and never republished.

ماخذWhat it givesLicence class
Government cloud strategies and procurement frameworksPolicies and contracts for public cloudPublic records, licence per government
Competition authority cloud market studiesMarket concentration and switching barriersPublic records, licence per authority
Public procurement data portalsSpending by supplierOpen data, licence per portal
EU Data Act provisions on cloud switchingRules on switching and egress chargesPublic, EU terms
Provider status historiesRecords of outagesPublic, terms per provider
08Decisions

Who decides, and what the evidence serves.

Digital Public Infrastructure prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.

کون فیصلہ کرتا ہےThe questionEvidence this page serves
Government digital and procurement agenciesWhere to host which systems and under what termsDependency maps; exit assessments
Competition and data regulatorsWhether concentration or transfers need interventionConcentration and jurisdiction evidence
Security agenciesWhich data must stay under domestic controlData classification reviews

Outputs this topic produces

  • Hosting dependency maps for public services
  • Concentration analyses of public cloud spending
  • Jurisdiction and data classification reviews
  • Exit and portability assessments
09Core questions

What experts ask.

Public services must continue regardless of the commercial fortunes or policy choices of any one supplier. When many government functions depend on the same provider, a technical failure, contract dispute, price change or legal order affecting that provider can disrupt services across the state. Concentration also affects bargaining power and the state's ability to change course.

  • Which public services depend on which cloud and software providers, and how concentrated are those dependencies?
  • Can a service be moved to another provider or run on-premises if necessary, and how long would that take?
  • Which laws apply to data held by a provider, and could foreign legal orders affect access?
  • What contractual terms protect continuity, data return and exit?
10Mechanisms

Drivers and processes.

Concentration risk has technical, commercial and legal dimensions.

Technical

Shared failure

Outages at a major provider affect all services hosted there. Architecture across regions or providers can reduce but not remove this risk.

Commercial

Lock-in

Proprietary services and data formats make migration costly. Pricing and terms can change after dependency has grown.

قانونی

Jurisdiction

Providers are subject to the laws of the countries where they are based and operate, which may conflict.

The most common weakness is not the choice of cloud but the absence of a tested way out. Exit plans that exist only on paper, data held in formats only one provider can read and skills concentrated in a supplier's staff all leave the state dependent. Building portability in from the start is cheaper than recovering it under pressure.

11Methods and data

How the evidence is built, and its limits.

  1. 01

    Dependency inventories

    Registers of providers behind public services. Often incomplete, especially for software components.

  2. 02

    Exit testing

    Practical tests of migration and data return. Rarely carried out, so exit plans are often untested.

  3. 03

    Contract analysis

    Review of continuity, data and exit clauses. Standard terms may give governments little leverage.

  4. 04

    Architecture analysis

    Assessment of designs for portability and resilience, applying high-performance, cloud and edge computing.

12طریقے

How it is studied, and what the methods cannot say.

  1. High-performance, cloud and edge computingCapacity planning for peaks · Multi-site and multi-provider hosting · Portability engineeringApplied here
  2. Cybersecurity and cryptographyThreat modelling DPI components · Protecting identity databasesApplied here
  3. Data engineering, interoperability and stewardshipSecure data exchange layers · Common data models · Consent-based sharingApplied here
13Where this page's references

اس صفحے کے حوالے کہاں لے جاتے ہیں۔

وہ ادارے اور دستاویزات جن کے تناظر میں یہ صفحہ پڑھا جاتا ہے۔ حیثیت اور ایڈیشن بدلتے رہتے ہیں؛ ہر لنک جاری کرنے والے ادارے تک جاتا ہے۔

14سوالات

سوالات و جوابات۔

What is sovereign cloud?
Cloud services designed so that data and operations stay under a particular country's jurisdiction and control, with various technical and legal arrangements.
Why is cloud concentration a risk for governments?
Because many public services may depend on the same few providers, so an outage, compromise or contract dispute can affect many at once.
What is cloud exit?
The ability to move a system and its data away from a cloud provider within acceptable time and cost.
Should governments avoid commercial cloud?
Not necessarily. Commercial cloud can improve security and reliability. The aim is to keep dependency manageable through portability, exit plans and diversified critical services.
Does the platform assess providers?
No. It studies concentration and dependency and does not assess, rate or recommend providers.
How can exit be made realistic?
Through open standards, data portability terms, documented architectures and periodic tests of migration for critical services.
رپورٹیںحصہ ڈالیں

اس صفحے سے شواہد فراہم کریں۔

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.

GCRIڈیجیٹل عوامی بنیادی ڈھانچہحکمت عملی کے نظامتیزی سے بڑھتی ٹیکنالوجی
ڈیجیٹل عوامی بنیادی ڈھانچہ

Bring a method, a dataset or a question.

معلومات اور استفسارات آج کھلے ہیں۔ استفسار کو ایک حوالہ نمبر ملتا ہے اور اگلے مرحلے کی نشاندہی ہوتی ہے؛ درخواستیں، ادائیگیاں، کمپیوٹنگ کی تخصیص اور رجسٹریشن صرف اس وقت کھلتی ہیں جب ان کی ٹیم، شرائط اور جائزے کی استعداد موجود ہو۔