Self-Hosted Environments for Claude Code (Public Beta)
Claude Code sessions run on your company's own servers instead of Anthropic's, for Team and Enterprise organizations.
Details
- Sessions execute inside your network, so Claude can reach internal services, databases, and package registries while source code and build artifacts stay on machines you control
- You deploy long-running processes called runners that pick up queued sessions, either as a fixed pool or an on-demand pool that starts and stops as work arrives
- Each session gets its own isolated copy of the code, and sessions started from web, mobile, or desktop all route to the same environment
- You can preinstall compilers, SDKs, and internal command-line tools per environment so Claude has the same setup your engineers do
- Off by default for Team and Enterprise organizations, unavailable on zero-data-retention plans, and it needs a dedicated platform team to set up and maintain
- Anthropic positions it alongside the hosted version rather than as a replacement, and recommends hosted for teams without special network or compliance needs
Best for
Teams whose source code, databases, or internal tools are not allowed to leave their own network
When to use it
Compliance rules block sending code to an outside vendor, or Claude needs internal services it cannot reach from the public internet
Who benefits
Platform and developer-experience teams at Claude Team and Enterprise organizations
Join the newsletter to get ahead with AI.
I share strategies, new modules, free guides, and tools to get you better at using AI in your work.
Leading a team? See team programs →

