AI Solution

Claude with EU data residency and full control

Your people want Claude. Your security team wants to know where the data goes. Claude Desktop in third-party (3P) mode answers both: Chat, Cowork and Code run on your laptops, and the model runs at the cloud provider and in the region you choose, including EU regions on Amazon Bedrock and Google Cloud. We design and roll out that setup so that you decide the region, the exit point, who can sign in and what gets logged. That control is what we mean by sovereignty.

What is Claude on 3P?

Claude on 3P is Claude Desktop in third-party mode. Chat, Cowork and Code work as usual, but every model request goes to an inference provider your organization chooses, such as Amazon Bedrock, Google Cloud or your own gateway, instead of Anthropic’s API. Conversations stay on the user’s device.

Anthropic built it for organizations whose security, regulatory or contractual rules prevent them from sending data through claude.ai or the Claude API. Pricing is token-based and billed by your cloud provider, with no seat licence. Settings are usually pushed through your device management tool, such as Intune or Jamf.

Where the model runs depends on the provider you pick.

Amazon Bedrock. AWS runs the model and processes the data in the region you select. EU regions are available.

Google Cloud. Google runs the model and processes the data in the region you select. EU regions are available. This is the service many people know as Vertex AI; Anthropic’s documentation calls it Agent Platform.

Microsoft Foundry. Anthropic operates the models, on Azure infrastructure or its own, and acts as an independent processor. Anthropic documents only global and US deployment types, so Foundry is not a route to EU residency today.

Your own gateway. A gateway you operate, such as LiteLLM, sits in front of one of the providers above. Data handling follows whatever it routes to.

Anthropic’s API. It works in 3P mode, but Anthropic then processes the data under your agreement with it, and inference cannot be pinned to the EU.

The app sends prompts, responses, files and tool outputs only to the endpoint you configure. It still contacts Anthropic to download its sandbox components when a session starts. Crash reports, usage analytics, update checks and the model catalog are separate, carry no prompt or response content, and can each be switched off in the managed settings.

Can we get EU data residency for Claude?

Yes, if Claude runs through Amazon Bedrock or Google Cloud with an EU region selected. Anthropic’s own API cannot do this: its inference location setting accepts only global or US, and Anthropic stores commercial data in the US. EU residency therefore means using a cloud provider as the route to the model.

Three settings decide where your data actually lives.

The region. On Bedrock, use an EU regional inference profile and avoid the global one. A global profile can send requests to any region that has capacity. A regional profile keeps them in the geography, and it is currently priced about 10 percent above global routing. On Google Cloud, choose an EU region for the endpoint.

The device. Conversation history is stored on the user’s laptop, so residency follows the device as well as the cloud region. A laptop that leaves the EU takes its history with it. The app does not encrypt the session record, which makes full disk encryption on the laptop part of the design.

What still reaches Anthropic. With telemetry, update checks and the model catalog switched off, the only traffic left to Anthropic is the download of the sandbox components. Tool servers you connect are separate destinations, and each one needs its own review.

Where have we done this?

A European energy company wanted Claude Desktop for its business teams. Its rules were strict: conversation data stays in the EU, none of it goes to the model vendor, and every request passes through the company’s own gateway.

We designed and delivered the rollout on the company’s managed laptops. Claude Desktop runs in 3P mode and reaches Claude, hosted by a major cloud provider in an EU region, through that gateway. People sign in with their company account and receive short-lived access. Membership of one access group decides who gets the app and its locked settings. Budgets per person keep spending predictable, and usage shows up in the monitoring platform the company already had.

The gateway behind it serves more than 500 people across more than 100 business units. The design went through the company’s internal security and data protection reviews before go-live.

We use the same pattern inside Docktape for our own sensitive work, so we run day to day what we build for clients.

Pain points

We can help you if you face:

  • People already using Claude on personal accounts, with company data
  • A rule that conversation data has to stay in the EU
  • A security team asking where prompts go, and nobody able to answer
  • AI spend spread across credit cards and teams, with no limits
  • A managed laptop fleet where every app must be packaged and locked down
  • A Claude pilot that works for ten people and has no path to five hundred

Our offering

Our offering includes

3P readiness assessment A fixed-scope review of which provider and region fit you, what your gateway and sign-in need, the questions your security and data protection teams will ask, and a rollout plan.
Gateway and EU routing One controlled exit to Claude in the EU region you choose, built on LiteLLM or the Claude apps gateway, running in your own cloud account.
Single sign-on Sign-in through your identity provider and access that expires within hours, with no long-lived API keys on laptops.
Managed desktop rollout Claude Desktop packaged for your device management tool, with locked settings, access by group and app versions you approve.
Spend limits and audit trail Budgets per person and per team enforced at the gateway, with usage and cost in the monitoring platform you already run.
Tools with user identity Your internal APIs published as tools Claude can call, where each call is made as the signed-in person and never through a shared account.

Want Claude on your laptops with the data staying in the EU? Book a free consultation and we will map your route, region and rollout.

FAQ

Your questions answered

Arnold Gálovics

CEO

Contact

Ready to start your own success story? Let us know.

Docktape Contact