Skip to main content
Back to timeline
Claude 产品博客Source publication:

Claude Managed Agents can now run entirely inside a company's own perimeter, control plane, sandboxes and credentials included

Synopsis

Anthropic released a self-hosted version of Claude Managed Agents in private beta, moving infrastructure that previously ran on the Claude Platform into a company's own cloud or on-premise environment. Teams that wanted agents to touch internal code and systems previously had to build the platform themselves, or host only the sandbox locally. Now the harness, sandboxes, credentials and session history all run on the customer's side, model requests can go to Anthropic, a cloud provider or the customer's own gateway, and developers keep the same core APIs as the hosted service.

Source-provided article image: Operate Claude Managed Agents inside your security perimeter
Claude 产品博客

Interpretation

A company can now run the whole Claude Managed Agents service in its own cloud or on-premise environment, not just the sandbox. The hosted version originally had Anthropic running all infrastructure on the Claude Platform, and self-hosted sandboxes were later added for teams that needed code to stay in their own environment; putting the entire service inside that environment previously meant building the platform themselves. The self-hosted version covers the harness, sandboxes, credentials and session history, with the customer operating the Managed Agents server, its database and the workers that run shell and file tools.

The agent loop and the sandbox that executes code are separated by design, so code runs in the sandbox while the agent loop, session history and vault secrets stay outside it. That separation means an agent does not depend on one sandbox surviving its whole run, sandboxes start only when a tool needs them, and session history lives outside the sandbox as an event log. For MCP tools and supported API calls, a proxy outside the sandbox adds the credential to the request; when self-hosting, credentials can also be stored in the customer's own secrets manager.

Each environment can be limited to a list of allowed hosts, and requests to any other host are blocked. For an agent that fixes broken builds, that list might contain only the company's git host and package registry. When the customer hosts the sandbox, the same limits are set in the customer's own firewall.

Perspective

The release is in private beta, with access requested through an Anthropic account team; the described scope is the component split of a self-hosted deployment, credential handling, network limits and how session records are exported.

The source does not state how widely the private beta is open, the performance or operational burden of a self-hosted deployment, or any real deployment case or comparison data.