EU-Hosted AI Agents: Keeping Every Model Call in Europe

"Is our data going to the US?" is now the first question a French or German SME asks about AI agents, often before asking what the agent does. The honest answer, on most platforms, is "partly": the platform may be hosted in Europe, but every request still goes to a model hosted in the United States, and a silent fallback can route it somewhere else again.

This guide explains where data actually travels when an AI agent runs, what "EU-only" should mean for an agent platform, and how Orkeste's EU sovereign profile works, including what it does not cover. If you are comparing EU options, the Orkeste vs Dust page covers a platform with EU data residency and a different focus.

Where your data goes when an agent runs

An agent run touches more places than its hosting page suggests. Take a support agent that answers a Zendesk ticket:

  • The platform stores the agent, its briefing, the run history and the encrypted connector tokens.
  • The model provider receives the ticket text, the briefing, the relevant help pages and the agent's draft. This is where most of the personal data goes.
  • Helper calls often go to a model too: extracting actions from the answer, scoring a test, rewriting a briefing, embedding documents for search.
  • The tools the agent works in (Zendesk, Gmail, HubSpot) hold the data in their own regions, under their own terms.

A platform can be "hosted in the EU" on point 1 and still send points 2 and 3 to the United States on every run. Fallbacks make it worse: when a provider is down, many routers silently retry on another provider, possibly in another region.

What an EU-only setting should guarantee

An EU-only setting for AI agents should keep every model call on EU-hosted models, with no exception for fallbacks, helper calls or personal API keys. In practice, that means five rules:

  • The agent's own model calls use an EU-hosted model.
  • Helper calls (action extraction, test judges, writing assistants) follow the same rule.
  • A fallback, when a provider fails, stays inside the EU or does not happen.
  • A personal API key for a non-EU provider is not used.
  • Multi-agent runs and tool loops inherit the setting, so no step escapes it.

How Orkeste's EU sovereign profile works

Workspace owners and admins switch it on under Settings, AI compliance. From then on:

The model chosen on each agent is kept. A non-EU model is replaced at run time by the EU model of the same tier, and the run's reasoning steps record the substitution, so you can see it in the run history. Turning the profile off restores the original model. In Agent Studio, non-EU models are greyed out while the profile is on.

Two EU-hosted models are available today: Mistral Small 4 for simple work and Mistral Medium 3.5 for the rest. Auto EU picks between them on each run according to the difficulty of the request.

A worked example: an accounting firm

A 15-person accounting firm uses two agents: one reads client emails in Outlook and drafts replies, the other reads Stripe and prepares payment reminders. Several clients have a clause forbidding transfers of their data outside the EU.

  • Before. The email agent uses Claude Sonnet 5.5; the reminder agent uses Auto. Both send client data to US-hosted models.
  • Switch. The managing partner turns on the EU sovereign profile. The email agent now runs on Mistral Medium 3.5, the reminder agent on Auto EU.
  • Check. In the run history, the first run of each agent shows a reasoning step: "EU sovereign profile: claude-sonnet-5-5 replaced by mistral-medium-3-5 (EU-hosted)".
  • Trade-off. Drafts on long, complex threads may be plainer than before. The firm keeps every draft behind approval, as before, and documents the setting in its GDPR records, together with the agent register exported from the same settings page.

What the profile does not cover

Being precise about the edges is the point of the exercise.

  • Your tools. Gmail, Outlook, HubSpot, Zendesk and every other connected service keep their own hosting and terms. The profile governs model calls, not where your CRM lives.
  • MCP servers. A server you connect runs wherever its owner hosts it (see the MCP guide).
  • Model quality. The strongest frontier models are not available in EU mode. For most drafting, triage and summarising work, Mistral Medium 3.5 is enough; for long, complex reasoning, expect a difference.
  • Platform hosting. Orkeste itself is hosted in the EU, as described on the security page. The profile adds the guarantee on model calls on top of that.

One related change applies to every workspace, with or without the profile: documents uploaded to an agent's knowledge are no longer sent to an outside embeddings service. Search ranks passages by text similarity inside Orkeste.

About DeepSeek

DeepSeek models are cheap and capable, and Orkeste offers them in an Auto Eco mode. The official DeepSeek API stores data in China, a country without an EU adequacy decision. For that reason DeepSeek is never a default, never a fallback, is shown with an "Outside EU (China)" badge, and is excluded entirely when the EU profile is on.

FAQ

Can AI agents run only on EU-hosted models?

Yes, on platforms that route every call, including helper calls and fallbacks, to EU-hosted models. In Orkeste, the EU sovereign profile does this for agent runs, swarms, tests and writing assistants, using Mistral models.

Does using an EU-hosted model make an agent GDPR compliant?

It removes one transfer outside the EU, which is often the hardest point to justify. GDPR compliance still depends on the rest: your legal basis, your data processing agreements, what you send to the model and how long you keep it.

Does the EU profile cost more?

The setting itself is free. Runs are billed in credits by the model actually used, so the cost of a run follows the price of the EU model that replaces the one configured.

What happens to agents set to GPT or Claude when I turn the profile on?

Their setting is kept, but each run uses the EU model of the same tier, and the substitution is recorded in the run's reasoning steps. Turning the profile off brings back the original model.

Is the EU profile the same as AI Act compliance?

No. The profile is about where data goes. The AI Act's transparency rules are about telling people they deal with an AI and marking generated content; Orkeste covers those separately, as explained in the AI Act guide.