Claude Cowork needs EU data residency / hyperscaler backend support for GDPR compliance

Resolved 💬 3 comments Opened Mar 29, 2026 by sdh07 Closed Mar 29, 2026

Summary

Claude Cowork currently routes all model inference through Anthropic's US-based infrastructure with no configuration option. This makes Cowork not deployable in German and broader EU enterprise environments subject to GDPR, unlike Claude Code CLI (which already supports AWS Bedrock and Google Vertex AI via environment variables).

This is a distinct regulatory issue from #32668 (which addresses corporate firewall filtering). The blocker here is data residency law, not network policy.

---

Problem

Under GDPR Art. 44–46, personal data may only be transferred outside the EU/EEA if appropriate safeguards are in place. Anthropic's current infrastructure stores all workspace data in the United States. While Anthropic provides a DPA with EU Standard Contractual Clauses, this does not satisfy the stricter requirements of many German and EU enterprise, public sector, and regulated-industry customers, who require:

  • Data processing guaranteed within EU territory, or
  • Deployment within a customer's existing cloud tenant (AWS Bedrock Frankfurt eu-central-1, Google Vertex AI europe-west1, Microsoft Foundry Sweden Central)

Claude Code CLI already solves this via environment variables (CLAUDE_CODE_USE_BEDROCK=1, CLAUDE_CODE_USE_VERTEX=1, CLAUDE_CODE_USE_FOUNDRY=1). Cowork has no equivalent.

Concrete regulatory contexts where Cowork is currently blocked:

  • German public sector (BSI requirements, DSGVO § 25 TTDSG)
  • Financial services supervised by BaFin
  • Healthcare with patient data (§ 203 StGB, DSGVO Art. 9)
  • Enterprises with Works Council agreements (Betriebsvereinbarungen) restricting US data transfers

---

Requested features (in priority order)

Option A — Hyperscaler backend support (preferred)

Mirror Claude Code CLI's existing backend configuration:

CLAUDE_COWORK_USE_BEDROCK=1 + AWS_REGION=eu-central-1
CLAUDE_COWORK_USE_VERTEX=1 + CLOUD_ML_REGION=europe-west1

Or via settings.json / MDM policy key:

{ "inferenceBackend": "bedrock", "inferenceRegion": "eu-central-1" }

Option B — Native Anthropic EU inference endpoint

https://api.eu.anthropic.com with data processing guaranteed within the EU — configurable in Cowork settings.

Option C — EU data residency for Claude.ai / Cowork Enterprise workspaces

Extend the API inference_geo option to Cowork and Claude.ai Enterprise.

---

Impact

  • EMEA is Anthropic's fastest-growing region. EU-resident inference directly unlocks enterprise and public sector customers currently blocked.
  • Cowork is the flagship product for non-developer knowledge workers — without EU data residency, the entire product category is off-limits for a large share of EU enterprise revenue.
  • The technical foundation already exists in Claude Code CLI. This is primarily a product/policy decision to expose it for Cowork.

---

Related

  • #32668 — Bedrock backend support for Claude Desktop / Cowork (network policy angle, 80 👍)

---

Current workaround

EU teams that need GDPR-compliant inference today can use Claude Code CLI with a hyperscaler backend as a stopgap:

# AWS Bedrock (Frankfurt)
export CLAUDE_CODE_USE_BEDROCK=1
export AWS_REGION=eu-central-1
export AWS_PROFILE=your-profile
claude

# Google Vertex AI (Belgium)
export CLAUDE_CODE_USE_VERTEX=1
export CLOUD_ML_REGION=europe-west1
export ANTHROPIC_VERTEX_PROJECT_ID=your-project
claude

This keeps all inference within the EU, but Claude Code is a developer-oriented CLI — it is not designed for the knowledge-worker workflows that Cowork targets (document collaboration, research, non-technical users). It requires terminal comfort, local setup, and lacks the UI affordances that make Cowork accessible to business users. This makes it a poor long-term substitute, but it is the only EU-compliant path available today.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗