AI agents · OpenClaw · self-hosting · automation

Quick Answer

Claude Code Self-Hosted Beta: What It Means (2026)

Published:

The Short Answer

In August 2026, Anthropic opened a public beta for self-hosted environments for Claude Code. Teams can now run agent sessions on their own infrastructure with custom tooling and compliance controls, rather than only on Anthropic-managed environments. It’s aimed squarely at enterprises with data-residency and security requirements.

What Changed

Claude Code has been terminal-native and cloud-backed. The self-hosted beta lets an organization host the session execution environment itself — the sandbox where the agent reads code, runs commands, and edits files — inside its own network and controls.

AspectBeforeSelf-hosted beta
Session environmentAnthropic-managedYour infrastructure
ToolingStandardCustom tooling allowed
ComplianceVendor defaultsYour compliance controls
ModelAnthropic frontier modelUnchanged (still Anthropic’s model)

Who It’s For

  • Regulated industries (finance, health, government) with data-residency rules.
  • Security-sensitive teams that can’t send repo contents through a vendor sandbox.
  • Large orgs with internal build tooling they want the agent to run inside.

What It Does Not Do

Self-hosting is about where the environment runs, not the model. Claude Code still calls Anthropic’s frontier models — Claude Opus 5 is the current top model (released July 24, 2026) and the default on Claude Max. You aren’t running the LLM locally; you’re running the agent’s execution and tooling layer on your own infrastructure.

Context: Anthropic’s August Enterprise Push

The self-hosted beta lands alongside other enterprise moves: skill and plugin security scanning (beta) that checks third-party uploads for malicious content on Enterprise plans, and Claude Cowork expanding to web and mobile. The theme is clear — Anthropic is hardening Claude Code and Cowork for regulated, at-scale deployment.

Should You Wait?

If you’re blocked today by compliance, join the beta and test with a non-critical repo — betas ship rough edges. If you’re not blocked, the managed environment remains simpler and is where new features land first.

Sources