Self-hosted Claude Managed Agents, your server

What changed

You host the service, the sandboxes and the database, while the model can still run at Anthropic or at a provider you choose. Anthropic’s docs say the server stores agents, sessions and each session’s history, and sends model requests to Anthropic by default.

Both the hosted and self-hosted versions share the same API, so the SDK and the ant CLI work with your server.

What you run

• A server (cma-server) that serves the API and runs the agent loop, plus a PostgreSQL 16 or later database. Without a database, a restart erases the data.
• Workers that run the agent’s shell and file tools in your sandboxes. The docs warn that the bash tool is a real shell, so isolation comes from the container or VM the worker runs in.
• A Console web page on your own server, where people sign in through your identity provider.

Who it is for

• Teams that must store agents, sessions and history themselves.
• Teams whose model calls must go to Amazon Bedrock, Claude Models on Google Cloud (Google managed), Microsoft Foundry or their own model gateway.
• If you only need tools to run on your infrastructure, Anthropic points you to self-hosted sandboxes instead.

What to do

1. Decide whether you need the whole service on your side or only the sandboxes.
2. To request access to the download, contact your Anthropic account team. It is not self-serve.
3. Read “Differences from the hosted service” first, because some features exist only on the hosted service. You also install each release yourself.