The Layer Europe Can Keep
Two weeks ago I wrote that someone else holds the off-switch: a single directive out of Washington disabled Anthropic's models for every foreign national on Earth, eleven days after Europe was first let in to test one. The lesson was that the frontier is borrowed, and the defensible ground is the layer one step behind it — applied systems, governance, sovereign deployment, the parts you can actually own. A model you rent can be switched off by memo. The layer above it cannot.
This is the case for that layer, and what it looks like when it ships. We build it. It is called Ingram Cloud, and it runs today.
Sovereignty is not where the data centre sits
The comforting version of AI sovereignty is a map with a server on it. Build a data centre in Frankfurt, the story goes, and the problem is solved. The off-switch proved that wrong in an afternoon. The model was withdrawn by the company that controls it; a data centre in Frankfurt would have sat there holding nothing. Hosting matters, but it is the floor, not the building.
Real sovereignty is freedom from coercion: the ability to choose which model runs, to substitute a provider without rebuilding your work, to keep your data under your own law, and to prove afterwards what the system actually did. That is not an infrastructure problem. It is a software problem — a control and assurance layer that sits above the model, and it is exactly the part of the stack Europe has not been building while it argued about champions and logins.
So we built it. Here is what it has to do, and how we do it.
1. Choose any model. Swap it without a rewrite.
The fastest way to be coerced is to marry your business logic to one provider's proprietary surface. Then a price change, a deprecation, or an export-control memo lands on a system you cannot move.
Ingram Cloud is standards-first by construction. You talk to it over the OpenAI-compatible API, the same contract most of the industry already speaks; tools connect over the Model Context Protocol. Your model keys are yours — bring your own, point them where you like. Because the design of an agent is held separately from the model that runs it, swapping providers is a configuration change, not a migration. You can run the best American model on Monday and refuse to be its hostage on Friday. When the next memo arrives, you change a line; you do not rebuild a quarter.
2. European hosting, European jurisdiction.
Ingram Cloud runs on European infrastructure, under European law. Your data, your run state, and the orchestration around it stay within EU jurisdiction — inside the GDPR and the EU AI Act, not adjacent to them. Each end-user runs as an isolated tenant with its own memory and connections, so isolation is the default rather than a configuration you have to remember to switch on.
This is the floor done properly: not a sovereignty claim painted over an American backend, but the actual substrate held where your regulator can reach it and a foreign directive cannot.
3. Prove what happened.
A regulated institution cannot deploy what it cannot account for. Under the EU AI Act and an ISO/IEC 42001 management system, "the model decided" is not an answer; you need evidence of what ran, under which configuration, on whose data.
Ingram Cloud records the run. Every execution leaves a trail of events; an agent's published design is versioned and each running instance keeps its own revision history, so a model swap or a policy change is a dated, inspectable fact rather than a story you reconstruct later. The audit trail your risk function asks for is a property of the platform, not a spreadsheet someone keeps on the side.
4. Decide what the agent may do — in the moment.
Governance that only exists in a policy document is theatre. Ingram Cloud enforces it at runtime: agents act through scoped tools, and sensitive actions can pause for human approval before they execute, riding the standard tool-call channel rather than a bespoke side protocol. You decide what an agent is permitted to do while it is doing it, and that decision is recorded with the rest.
The honest part
We do not train the frontier, and we are not asking Europe to. That is the capital bonfire the off-switch piece argued Europe should stop trying to win. What we own — and what you can own through us — is the layer that makes any frontier model, American or European, open-weight or hosted, usable inside a real institution without surrendering control of it. Many models, many fallbacks, all of it under European jurisdiction, all of it accountable.
A memo can switch off a model. It cannot switch off the layer above it. That layer is the one worth keeping, and it is the one we built.
Jerome Leclanche
CEO, Ingram Technologies
About Ingram Technologies
Ingram Technologies is a European AI research and development lab, founded in 2022 and based in Brussels. We build applied, agentic AI systems and advise on AI governance and ISO/IEC 42001 compliance, with a focus on responsible, sovereign AI for European organisations. Ingram Cloud is our platform for deploying and governing AI agents under European jurisdiction.
Media enquiries: press@ingram.tech
Get in touch