High
Anthropic Self-Hosted Managed Agents — run the full Managed Agents service on your own infrastructure
What changed
Previously, Managed Agents had one self-hosting option — self-hosted sandboxes, where you run tool execution but Anthropic runs the agent service, session storage, and agent loop. Today Anthropic launched the other end of the spectrum: self-hosted Managed Agents, where you run the entire service — the API, agent loop, agents, sessions, and session history — on your own infrastructure, while model calls go to whichever inference provider you configure.
TL;DR
Anthropic's Managed Agents service (cma-server) is now deployable on your own infra (Linux/macOS, PostgreSQL 16+), with model calls routable to Bedrock, Google Cloud (Google-managed), Microsoft Foundry, or your own model gateway instead of Anthropic's API.
Developer signal
To request access to the cma-server download, contact your Anthropic account team. Once you have access: run cma-server alongside a PostgreSQL 16 database; create environments with the cma-server-admin CLI; run workers with ant beta:worker poll or the Python/TypeScript/Go SDK workers. Your applications and the ant CLI connect to your server's URL rather than api.anthropic.com — the API surface is identical, so existing code requires only a URL change. The inference credential (the API key / cloud credential your server uses for model calls) lives only in cma-server's config — it never reaches your applications or workers. Sandbox platform providers (Cloudflare, Daytona, E2B, Modal, Vercel, AWS Lambda, Fly.io, GKE) have published guides for running workers on their platforms. Important limitations: self-hosted Managed Agents is not eligible for ZDR (Zero Data Retention), does not support HIPAA, and some features available on the hosted service differ (see the Differences from the hosted service page). The agent's bash tool runs with the worker process's permissions — isolation is your responsibility; run workers in disposable containers or VMs.
Affects you ifYou build Managed Agents-based products and need agents, sessions, or session history stored on infrastructure you control; you need model calls routed to Amazon Bedrock, GCP (Google-managed), Microsoft Foundry, or your own gateway; your compliance requirements require data-residency guarantees that Anthropic's hosted service cannot provide.EffortSignificant (stand up cma-server, configure PostgreSQL, generate environment keys, wire an identity provider for the console, run workers in isolated sandboxes)