Self-hosted Claude Managed Agents keeps agent credentials in your environment

Anthropic has released a self-hosted version of Claude Managed Agents, and companies can run the agent harness, sandboxes, credentials, and session history in their cloud or on-premise.

The option opened as a private beta on November 12, and customers request access through their Anthropic account team.

Model requests go wherever the customer points them: to Anthropic directly, to Amazon Bedrock, Google’s Agent Platform or Microsoft Foundry, or to the customer’s gateway.

The server, the database, and the firewall rules are now the customer’s to run, and so is the job of keeping them patched and set up correctly.

The change matters for agents that already work unattended inside corporate systems, fixing broken builds, testing releases, triaging alerts, and working through bug backlogs.

In the self-hosted setup, the customer operates three things: the Managed Agents server, its PostgreSQL database, and the workers where agents run their shell and file tools.

Self-hosted customers can keep those credentials in their own secrets manager, and each environment can be locked to a list of allowed hosts, and requests to any other host are blocked.

Anthropic ran everything else, including the credential handling and the record of what each agent did; developers build agents with the same core APIs as the hosted service.

The company’s reasoning is that a team can’t count on a person checking each step of an unattended agent, so

Anthropic limits that protection to MCP tools and supported API calls, so any other service an agent reaches is worth checking before the agent goes live.

They apply whether Anthropic hosts everything, the customer hosts only the sandbox, or the customer hosts all of it.

The log exports over OpenTelemetry, so security teams can pipe it into the monitoring tools they already run and look at agent activity next to everything else they watch.