TL;DR. On 1 June 2026, OpenAI broke ground on a 1-gigawatt data center in Michigan under the Stargate programme, according to the official announcement. The same day, its frontier models and Codex became available on AWS. AI compute is consolidating on American soil — and the window for European leaders to act is narrowing.
What just happened
On 1 June 2026, OpenAI began construction on a 1-gigawatt data center in Michigan, according to its official announcement. The project operates under Stargate, a programme whose stated aim is to expand AI access, create jobs, and support local American communities. On the same day, OpenAI announced that its frontier models — including Codex — are now generally available on AWS, integrated directly into the cloud environments, controls, and procurement workflows enterprises already use, per the official release. A third document published the same day outlines OpenAI's approach to AI policy and political advocacy, specifying that no outside political group speaks on the company's behalf, according to the published text.
Why this matters for European businesses
A 1GW data center is not an operational detail. It is a geopolitical decision. When OpenAI deploys capacity of that scale on American soil and distributes it via AWS — infrastructure itself subject to US jurisdiction — European companies relying on those services expose their data and workflows to a legal framework that is not their own. The EU AI Act, progressively in force since 2024, imposes traceability, governance, and documentation requirements that are directly conditioned by where processing physically takes place. The AWS integration described in the official announcement lowers the friction of adoption — which is precisely the mechanism through which dependency deepens. Ease of access is the lock-in instrument.
Three immediate opportunities for European and Belgian leaders
- Map critical dependencies. Identify exactly which business processes rely on American models or infrastructure, and assess continuity risk in the event of regulatory or geopolitical access restrictions.
- Evaluate documented European alternatives on a real use case. Actors such as Mistral AI offer models deployable on European infrastructure. Leaders who run a concrete evaluation now will have an empirical baseline before the choice becomes urgent.
- Elevate data localisation to a governance decision. EU AI Act compliance requires knowing where inference and training data are processed. That conversation belongs at board level, not only within technical teams.
Three risks if Europe stays passive
- Structural dependence on American compute. As Stargate and AWS consolidate the frontier offering, European alternatives have less commercial surface area to reach critical mass. Lock-in arrives gradually, not suddenly.
- Exposure to US export controls. American technology export regulations already govern certain transfers. A policy shift — even a partial one — could affect European access to frontier models without adequate lead time to pivot.
- Cross-compliance pressure. European companies using AWS-OpenAI services will need to navigate the EU AI Act, GDPR, and American contractual terms simultaneously — constraints that can enter direct tension without either party being obliged to resolve the conflict.
What the timing of three simultaneous announcements signals
Three publications in a single day — Michigan infrastructure, AWS availability, public policy statement — do not reflect an editorial calendar. They signal a company explicitly positioning itself as a systemic actor, aware that its infrastructure decisions carry political and regulatory weight. For a European executive, reading these three texts together is more instructive than reading them in isolation: the infrastructure builds dependence, the AWS distribution accelerates it, and the policy document begins to legitimise it.
Three levers to activate this week
- Run a ten-line AI inventory. List active AI services in the organisation — models, providers, data location — and flag processes that depend on infrastructure outside the EU. Ten lines are enough to start.
- Test a documented European model on one real, bounded use case. Choose a non-critical process, deploy a European alternative, measure the performance gap. A concrete evaluation outweighs any theoretical sovereignty debate.
- Put the question on the agenda of the next leadership meeting. Ask explicitly: on what infrastructure does our AI run, and what are our contractual rights if access is restricted? The answer must come from legal and technical leadership together.
Where, specifically, does your AI compute sit?
If this analysis speaks to you, I publish a piece of this calibre every day on digital innovation and enterprise AI. 👉 Get the next one straight in your inbox — sign-up takes ten seconds, and each edition is read before 9 a.m. by leaders of European SMEs, mid-caps and public institutions.
Sources
- Building the infrastructure for the Intelligence Age in Michigan (OpenAI News)
- OpenAI frontier models and Codex are now available on AWS (OpenAI News)
- Our views on AI policy and political advocacy (OpenAI News)