Containerized Claude Code, curated.

back2base.net  ·  chat  ·  oss  ·  releases  ·  security

back2base runs Claude Code inside a hardened Docker container with a curated MCP bundle, an outbound egress firewall, and prompt-cache–optimized image layering. A single binary, a single container, and no host-level dependencies — your Claude subscription, sandboxed.

The CLI plus a managed backend, so your Claude Code environment follows you across machines.

• Cross-device session memory backed by R2
• Configuration and MCP profiles synchronized across devices
• Browser client at chat.back2base.net — same memory stack, no install required
• Managed claudeproxy gateway with shared rate limits and observability
• Auth0 sign-in linked to your Claude Pro, Max, Team, or Enterprise subscription

# macOS
brew install back2base/back2base/back2base

# Linux (Debian/Ubuntu)
curl -fsSL https://back2base.github.io/apt-back2base/public.key \
  | sudo gpg --dearmor -o /usr/share/keyrings/back2base.gpg
echo "deb [signed-by=/usr/share/keyrings/back2base.gpg] \
  https://back2base.github.io/apt-back2base stable main" \
  | sudo tee /etc/apt/sources.list.d/back2base.list
sudo apt update && sudo apt install back2base

back2base login      # Auth0 device flow + Claude subscription link
back2base            # launch Claude Code in the current project

The same container runtime, firewall, and MCP bundle, without the hosted services. No account required. Builds from source and runs anywhere Docker runs.

git clone https://github.com/Back2Base/oss-back2base
cd oss-back2base && go build -o oss-back2base .
./oss-back2base

• Curated MCP bundle. memory, sequential-thinking, brave-search, context7, lsmcp, git, fetch, sqlite, terraform, buildkite, datadog, and github.
• Network egress firewall. iptables rules restrict the container to Anthropic and an allow-listed set of endpoints.
• Prompt cache optimization. Image layers are sequenced for Anthropic's 5-minute cache TTL.
• Subscription-based auth. Pro, Max, Team, and Enterprise accounts via claude setup-token; no API keys required.

The hosted-platform source resides in the private back2base repository by design; the build and release pipeline runs from there, and artifacts are published to the public repositories above. Contributions to the open-source runtime are welcome directly in oss-back2base.

• Hosted platform: discussions and issues
• Open-source runtime: oss-back2base issues

_{MIT licensed. back2base.net. Maintained by @ramseymcgrath.}