Sovereign AI infrastructure

This project compares how governments, universities, and public institutions define and operationalise AI sovereignty. Sovereignty is often invoked as a policy ambition, but it can refer to many different things: domestic cloud capacity, public compute, data governance, local model development, procurement autonomy, standards participation, or reduced dependence on foreign technology providers.

We study how these ambitions become infrastructure. A sovereignty strategy is not only a document or funding programme. It is expressed through contracts, facilities, standards, procurement rules, research partnerships, energy systems, and institutional capabilities. The project follows those material choices to understand what forms of autonomy are actually being built.

Research focus

The project compares different models of AI sovereignty. Some approaches emphasise national compute capacity and public investment in high-performance infrastructure. Others focus on trusted cloud procurement, open-source software, data spaces, sector-specific platforms, or regulatory alignment. Each model creates different dependencies and different forms of institutional capability.

We ask what is meant by sovereignty in each case, which actors are expected to provide it, and what technical arrangements support it. We also examine where sovereignty claims become ambiguous. A government may fund local infrastructure that relies on imported chips, foreign cloud software, external maintenance contracts, or global developer ecosystems. These dependencies do not necessarily make sovereignty impossible, but they need to be described precisely.

The project treats sovereignty as a gradient rather than a fixed status. Institutions can have more control over some layers of the AI stack and less over others. They may control data but not compute, procurement rules but not software maintenance, or research infrastructure but not deployment platforms. Mapping these layers makes the debate more concrete.

From policy ambition to operational control

Sovereignty language often compresses several goals into one term. It can mean strategic autonomy, economic competitiveness, national security, data protection, public-sector bargaining power, research independence, democratic accountability, or resilience against geopolitical disruption. These goals may overlap, but they are not identical. A strategy that improves one form of sovereignty may leave another untouched.

For example, a country may attract a major cloud region and describe it as sovereign capacity. That may improve latency, data-residency options, and local service availability. It may not provide control over hardware supply, software roadmaps, pricing, audit rights, or emergency access. Another country may invest in a public research cluster that offers stronger academic control but less commercial scalability. Both are infrastructure choices, but they solve different problems.

The project therefore asks institutions to define sovereignty in operational terms. What decisions should public actors be able to make? What systems must they be able to inspect? What services must they be able to continue if a vendor changes terms? What data must remain under specific legal or institutional controls? What expertise must be maintained internally rather than outsourced?

Method

Our research combines policy analysis, infrastructure mapping, and comparative case studies. We analyse national AI strategies, public procurement frameworks, cloud agreements, research infrastructure plans, standards initiatives, and public compute programmes. We also track how sovereignty language changes across policy domains, from economic competitiveness to security, education, research, and public-sector modernisation.

Interviews and document analysis help connect policy claims to operational details. We are interested in who makes infrastructure decisions, what constraints they face, how public institutions evaluate vendor dependence, and how technical requirements are translated into procurement and governance processes.

The project compares strategies across several institutional settings. National governments tend to frame sovereignty through competitiveness, security, and industrial policy. Universities and research infrastructures often focus on access, reproducibility, scientific autonomy, and long-term stewardship. Public agencies may prioritise procurement rules, data protection, service reliability, and accountability. Regional institutions may emphasise economic development, local capacity, and alignment with wider regulatory frameworks.

By comparing these settings, we can identify recurring patterns. Sovereignty claims often become more concrete when they reach procurement teams, infrastructure managers, legal departments, and research computing staff. These actors must translate broad ambition into contracts, access controls, staffing plans, service-level expectations, and budget lines.

Layers of sovereignty

The project uses a layered model of AI infrastructure. The compute layer includes chips, servers, clusters, data centres, cloud regions, and high-performance computing facilities. The data layer includes data governance, storage location, access controls, sharing agreements, and sector-specific data spaces. The software layer includes operating systems, orchestration tools, model-serving frameworks, monitoring systems, and security tooling.

The model layer includes foundation models, fine-tuned models, evaluation methods, documentation, safety systems, and licensing terms. The procurement layer includes vendor selection, contract duration, exit rights, auditability, switching costs, and compliance requirements. The expertise layer includes the public-sector capacity to evaluate systems, negotiate contracts, maintain infrastructure, and respond to failures. The governance layer includes accountability mechanisms, standards participation, public oversight, and institutional decision-making.

Different strategies strengthen different layers. A public compute programme may improve the compute and expertise layers while leaving software dependencies unresolved. A trusted cloud procurement framework may improve compliance and contractual governance while maintaining dependence on commercial platforms. An open-source model strategy may improve adaptation and transparency while still requiring external compute and maintenance capacity.

Tensions and trade-offs

Sovereign AI infrastructure involves trade-offs. Full domestic control over every layer may be unrealistic, slow, or prohibitively expensive. Complete reliance on global cloud providers may be efficient in the short term but can weaken bargaining power, auditability, and resilience. Hybrid models can be pragmatic, but they need clear governance so that dependencies are visible rather than hidden behind sovereignty branding.

Cost is one tension. Public infrastructure requires long-term funding for hardware refreshes, facility operations, security, staffing, and software maintenance. A one-time capital investment may produce a strong announcement but weak operational capacity if ongoing budgets are missing. Another tension is expertise. Institutions cannot exercise meaningful control over infrastructure they do not understand, even if contracts assign them formal rights.

There is also a tension between openness and security. Public institutions may benefit from open-source systems and shared research infrastructure, but some applications require restricted access, compliance controls, or national-security considerations. The project does not assume that one model fits all cases. Instead, it asks which form of control is appropriate for each use case.

Procurement as infrastructure policy

Procurement is one of the most important sites where AI sovereignty becomes practical. Contract terms can determine whether public institutions can audit systems, move workloads, access logs, control data flows, understand subcontracting arrangements, or maintain services during disruption. Procurement can also shape markets by rewarding interoperability, transparency, and public-interest requirements.

Yet procurement teams often work under pressure to deliver services quickly, control costs, and comply with complex legal frameworks. They may not have the technical support needed to evaluate AI infrastructure dependencies. The project studies how procurement processes can be improved without turning every acquisition into an unrealistic exercise in full-stack self-sufficiency.

We pay particular attention to exit rights, portability, documentation, data access, model governance, and security responsibilities. These details are easy to treat as legal boilerplate, but they determine whether sovereignty claims survive contact with operational reality.

Policy relevance

AI sovereignty is becoming a key term in European and national policy debates, but vague use of the term can obscure difficult trade-offs. Building everything domestically may be unrealistic or inefficient. Depending entirely on external providers may create unacceptable risks. Public institutions therefore need sharper language for describing which capabilities matter, which dependencies are acceptable, and which require intervention.

This project helps separate symbolic sovereignty from operational sovereignty. Symbolic sovereignty appears in announcements and labels. Operational sovereignty depends on whether institutions can inspect systems, switch providers, govern data, maintain expertise, negotiate contracts, and sustain infrastructure over time.

The work is relevant to public agencies, universities, research infrastructures, and policy teams that need to make decisions about cloud procurement, model deployment, open-source adoption, and compute investment. It provides a way to evaluate infrastructure choices before they become long-term dependencies.

Working framework

The project is developing a practical framework for assessing sovereignty claims. The framework asks which layer of the AI stack is being controlled, which actor holds that control, what evidence supports the claim, what dependencies remain, and what mechanisms exist for accountability. It also asks what would happen under stress: vendor withdrawal, price increases, geopolitical disruption, security incidents, hardware shortages, or regulatory change.

This stress-test approach is useful because infrastructure autonomy is most meaningful during constraint. A system that works only when markets are stable and vendors are cooperative may still be useful, but it should not be described as a robust sovereign capability. Conversely, a smaller system with clear governance, skilled operators, and realistic continuity plans may provide more meaningful autonomy for specific public tasks.

Outputs

The project will produce comparative reports, policy briefs, and a layered framework for analysing AI sovereignty. The framework will describe sovereignty across compute, data, software, models, standards, procurement, expertise, and governance.

We will also publish short case studies showing how sovereignty is operationalised in different institutional settings. These cases will identify practical patterns, recurring constraints, and opportunities for public-interest infrastructure that is accountable, maintainable, and technically realistic.

Later outputs will include a procurement checklist, a glossary of sovereignty claims, and a set of diagrams that help public institutions distinguish ownership, access, control, resilience, and accountability.