06-reference/research

self hosted managed agents data boundary

2026-11-19·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
claude-managed-agentsself-hosteddata-residencyzdrphdata

Self-hosted Managed Agents: what still reaches Anthropic, per inference provider

The question

"What do Anthropic's own docs say that the self-hosted Claude Managed Agents private beta (agent server, database, sandboxes, credentials and session history in the customer environment, selectable model provider) actually keeps on Anthropic's side, and which data-residency objections does it resolve when the model provider is Anthropic's API versus Bedrock, Google or an internal gateway?"

Context: the only vault evidence was a newsletter blurb. This brief replaces it with the primary docs, which turned out to be publicly readable even though the software itself is gated.

Evidence labels used below: [P] = read in Anthropic's own docs or announcement on 2026-11-19. [S] = secondary source only. [I] = my inference, not stated by any doc.

What we already know (from the vault)

What the web says

What crosses to Anthropic, by configuration

Item Claude API Amazon Bedrock Google Cloud Microsoft Foundry Own gateway
Server connects to Anthropic Yes [P] No [P] No [P] No [P] No, unless the gateway forwards there [P]
Prompts, tool inputs, tool results To Anthropic [P] To AWS [P] To Google [P] To the Foundry resource [P] To the gateway [P]
Session, agent, environment ID headers Sent, cannot be disabled [P] Never [P] Never [P] Never [P] Only via ANTHROPIC_BASE_URL proxy [P]
cma-server usage label Sent [P] Never [P] Never [P] Sent [P] Sent if Claude API format [P]
Credential check every 60s Yes [P] Not described Not described Not described Not described
Session history, agents, vault secrets at rest Customer [P] Customer [P] Customer [P] Customer [P] Customer [P]
Anthropic remote access to server or logs None [P] None [P] None [P] None [P] None [P]
Retention terms for model I/O Your Anthropic agreement, ZDR if you have it [P] Your AWS agreement [P] Your Google agreement [P] Your Microsoft agreement [P] Whoever the gateway forwards to [I]

Convergences and contradictions

Synthesis for RDCO

The honest one-line answer for a regulated client is: self-hosted Managed Agents moves the system of record, not the inference. Anthropic's side holds no session store, no credentials, no control plane and no remote access in any configuration. What Anthropic still sees depends entirely on the inference setting. With the Claude API it sees the full conversation on every turn plus non-content identifiers it uses to count usage; the residency story there is contractual (ZDR, and whatever model-specific retention terms apply). With Bedrock or Google, the docs say the server never connects to Anthropic and sends no Anthropic usage identifiers at all, so the conversation is governed by the client's existing cloud agreement. That is the configuration that answers "nothing goes to Anthropic" in a form a security reviewer can check against an egress log, which the docs explicitly invite.

So the objections sort into three groups. Resolved in every configuration: transcripts stored at a vendor, vendor-held credentials, vendor-operated control plane, vendor access to logs, and hosted Managed Agents falling outside ZDR. Resolved only off the Claude API: prompts and tool results transiting Anthropic, and Anthropic-side usage attribution by session. Not resolved by this product at all: the model still runs somewhere outside the client's own hardware, so in-region processing depends on the provider's region settings (the Bedrock default is a US cross-region profile, a detail that would fail an EU or single-region requirement if left untouched), and the client now owns server hardening, tenant separation by deployment, anomaly detection and upgrades. Microsoft Foundry sits in between: no Anthropic connection from the server, but the cma-server label is sent and the docs note Anthropic can use it "where a call reaches Anthropic." The docs read here do not say whether Foundry-served calls reach Anthropic, so that row should not be presented as equivalent to Bedrock without checking Microsoft's and Anthropic's Foundry terms. [I]

For phData positioning this is a cleaner story than anything available before 2026-11-12: a client already approved for Claude on Bedrock or Google can run the same Managed Agents API and SDK with no new data processor added, and the agent definitions work unchanged across providers because the server translates model IDs. The costs to state up front are that it is a private beta with account-team gating, undisclosed pricing, a feature gap versus hosted (a "differences" page exists and was not read in full; cloud environments are confirmed absent), and a real operations burden. It is a fit for a client with a platform team, not a shortcut.

For the cert topic, the three-row hosting table is the thing to memorize, with one trap: self-hosted sandboxes do not change where transcripts live or ZDR coverage; only self-hosted Managed Agents does, and choosing a non-Anthropic provider is what removes the Anthropic connection. Note this beta postdates most study material, so an exam item written earlier may treat "self-hosted harness on your infrastructure with a ZDR org" as the only answer.

Why this is in the vault

It gives the phData regulated-client conversation a doc-backed, per-provider answer to "what does Anthropic still see?" for agent deployments, and it updates the self-hosted vs Anthropic-hosted distinction used in cert study now that a third hosting option exists.

Open follow-ups

Related

Sources