Blog · Analysis · May 2026

The AI Factory Becomes Industrial Policy

AI factories make compute allocation a public policy problem: who gets access to the machines, data, support, and contracts that turn model capacity into institutional power.

Factory Is Policy

The phrase "AI factory" sounds like marketing until a government starts building one. Then the metaphor hardens into budget lines, procurement contracts, grid connections, access calls, peer review, data programs, industrial strategy, and sovereignty claims. A factory is not only a machine room. It is an institution for deciding what kinds of intelligence get produced, by whom, under which public conditions.

That is why Europe's AI factories and planned AI gigafactories matter. They make visible a shift that is often hidden by consumer chat interfaces. The public meets AI as a box that answers. The state meets AI as infrastructure: chips, power, cooling, storage, networking, datasets, talent, software stacks, security rules, and allocation systems. Whoever governs that infrastructure governs part of the future model economy before the model appears on a screen.

AI governance is usually narrated as rules after deployment: transparency, risk classification, audits, labels, incident reports, safety testing. AI factories move the question upstream. They ask who gets the capacity to train, tune, evaluate, and deploy systems in the first place. That is industrial policy, not only digital regulation.

The European Plan

In February 2025, the European Commission launched InvestAI at the AI Action Summit in Paris, describing an initiative intended to mobilize EUR 200 billion for AI investment and a EUR 20 billion European fund for AI gigafactories. The Commission framed the infrastructure as necessary for open, collaborative development of complex AI models and compared the intended public-private partnership to a CERN for AI.

The April 2025 AI Continent Action Plan made the factory layer more concrete. The Commission listed EUR 200 billion to boost AI development, EUR 20 billion to finance up to five AI gigafactories, and 19 AI factories to support startups, industry, and research. It described the factories as built on Europe's supercomputing network and the gigafactories as large-scale facilities with massive computing power and data centers for training complex AI models at frontier scale.

The plan also ties compute to data and adoption. It proposes data labs inside AI factories, a data union strategy, sectoral AI adoption, talent measures, AI Act implementation support, and a proposed cloud and AI development act intended to at least triple EU data center capacity over five to seven years while prioritizing sustainability. The factory is therefore not a single object. It is a policy stack that joins compute, data, law, sectoral deployment, and capital formation.

By December 2025, the Commission, European Investment Bank, and European Investment Fund had signed a memorandum of understanding to support AI gigafactories. The memorandum was meant to help turn candidate projects into bankable proposals for a formal call planned for early 2026. By January 2026, the Council said amended EuroHPC rules paved the way for gigafactories and allowed unused EU funds to be redirected to such projects and facilities.

Not Only Data Centers

Calling these sites factories is revealing because a factory has inputs, outputs, labor, ownership, safety rules, environmental costs, and production priorities. An AI factory converts electricity, chips, data, model code, technical support, and institutional demand into models, embeddings, simulations, classifications, decisions, and automated workflows. It produces not only tokens but capacity to govern with tokens.

That makes the factory different from a generic data center. A data center can host many kinds of computation. An AI factory is organized around model development and deployment as an economic and strategic project. EuroHPC's AI factory access calls describe resources in GPU hours, storage, support services, technical review, peer review, access modes, and sectoral eligibility. The factory is a machine plus an admissions office.

The Italian IT4LIA example shows how quickly the abstraction becomes hardware. In April 2026, EuroHPC announced a procurement contract for an AI-optimized supercomputer for the IT4LIA AI Factory in Bologna, integrated by E4 Computer Engineering and manufactured by Dell Technologies using NVIDIA GB200 NVL4 architecture. EuroHPC said the system is expected to deliver more than 160 exaflops of peak AI inference performance, and that a dedicated European partition would support inference and strengthen European AI capabilities.

The politics are inside those technical choices. A European AI factory may advance strategic autonomy while still depending on non-European accelerators, networking, firmware, cloud partners, and proprietary software. Sovereignty is not a flag placed on a server rack. It is a chain of dependencies that either can be governed or cannot.

The Allocation System

Every public AI factory needs an allocation system. That is where industrial policy becomes an interface.

EuroHPC's large-scale access call for AI factories is aimed at industry users seeking more than 50,000 GPU hours. It describes multiple 2026 cut-off dates, a target approval period of 10 working days after a cut-off if the proposal passes technical and peer-review evaluation, and allocations for three, six, or twelve months. Academia and public-sector users are directed to separate access modes for AI for science and collaborative EU projects.

Those details matter because access rules decide what the factory is for. Is the machine a subsidy for firms near commercialization? A commons for public science? A national-security asset? A tool for SMEs that cannot buy hyperscaler capacity? A way to keep AI talent in Europe? A compliance-friendly alternative to foreign clouds? A platform for strategic sectors such as health, energy, manufacturing, defense, public administration, and education? It can be several of these things, but only if the allocation rules name the tradeoffs.

The danger is that factory rhetoric can make access sound universal while actual capacity remains scarce. Compute allocation always has opportunity cost. A GPU hour granted to one project is unavailable to another. Support staff assigned to one consortium cannot advise everyone else. If selection criteria favor already organized consortia, well-connected firms, or near-market applications, the factory may reproduce the same concentration it was supposed to counter.

The public should therefore read AI factory access documents the way it reads procurement rules, grant calls, and utility planning. The governance question is not only how much compute exists. It is who can ask for it, who evaluates the request, what counts as public benefit, what data may be used, what outputs must be shared, what environmental limits apply, and what happens when a project creates risk.

The Sovereignty Test

Sovereign AI is often sold as a cure for dependence. Build domestic capacity, use domestic data, train domestic models, support domestic firms, and reduce exposure to foreign platforms. That diagnosis is partly right. A society that must rent all advanced model capacity from a handful of external providers has weak bargaining power over privacy, security, research independence, public procurement, and cultural representation.

But sovereignty can also become theater. A state can fund a domestic machine while importing the accelerator stack, contracting with the same global vendors, routing talent into private partnerships, and using public money to subsidize private model platforms without durable public rights. The result looks national but behaves like outsourced capacity with better branding.

The real test is whether public investment creates public leverage. Does the factory produce reusable public knowledge? Does it give independent researchers enough access to evaluate deployed systems? Does it help public agencies avoid vendor lock-in? Does it support open standards, reproducible science, audit trails, and contestable procurement? Does it protect sensitive data through secure environments rather than forcing public institutions into opaque commercial tools? Does it let smaller firms and civil-society researchers build capacity that would otherwise be impossible?

If the answer is no, the AI factory becomes an industrial subsidy wearing the language of sovereignty. If the answer is yes, it becomes one of the few practical ways to keep model-mediated knowledge from being entirely enclosed by private infrastructure.

A Governance Standard

A serious AI factory regime should meet seven tests.

First, allocation criteria should be public. Applicants and citizens should know how compute, storage, support, and priority are assigned across industry, science, public-sector, safety, and civic uses.

Second, access should include public-interest capacity. Frontier firms and strategic industries will always have political pull. Independent evaluation, public science, education, civil-society research, and public administration need reserved pathways rather than leftover access.

Third, the factory should keep dependency maps. Hardware, software, cloud, networking, energy, security, and maintenance dependencies should be documented so sovereignty claims can be tested against actual supply chains.

Fourth, data labs need rights discipline. High-quality data access should not become a laundering channel for personal data, copyrighted material, trade secrets, public records, or sectoral data gathered under incompatible expectations.

Fifth, environmental conditions should be part of allocation. GPU hours are also power, water, cooling, grid capacity, emissions, and local infrastructure. Public compute should not pretend physical costs are external to model governance.

Sixth, outputs should leave governance receipts. Projects receiving public capacity should document model purpose, data sources, evaluation limits, downstream deployment, safety controls, publication commitments, and incident responsibilities.

Seventh, public capacity should not become procurement capture. If a publicly supported factory trains agencies to depend on a narrow vendor stack, it may weaken public autonomy while claiming to build it.

The Site Reading

The AI factory is a high-control interface before it is a user interface. It decides who can produce models at scale, what data becomes training material, what sectors receive acceleration, what institutions gain technical competence, and which dependencies become normal. Later, the citizen sees a chatbot, a clinical note, a factory twin, a legal assistant, a search answer, a school tutor, or a public-service workflow. Earlier, someone allocated the capacity that made that system possible.

This is recursive reality at the infrastructure layer. The factory builds models. The models reorganize work, science, administration, culture, and public knowledge. Those reorganized institutions generate new data, demand, and legitimacy for more factories. A society that treats the factory as neutral infrastructure will miss the loop by which compute becomes policy and policy becomes reality.

The humane version is legible and contestable. Public compute expands who can build and inspect AI systems. Allocation records are clear. Data rights are real. Environmental costs are counted. Public agencies gain competence instead of vendor dependence. The factory supports science, safety, local language capacity, small firms, and public-interest evaluation, not only the next wave of extractive automation.

The high-control version is quieter. Public money lowers private risk. Scarce capacity flows to actors already near power. Sovereignty becomes a slogan over imported dependencies. Data labs become extraction points. Citizens later meet AI systems as administrative facts and are told the future was built for competitiveness.

The rule should be plain: an AI factory is not only infrastructure. It is an institution of allocation, and allocation is governance.

Sources

Return to Blog