- Quickstart with DockerStart Who2Be on your own machine with two commands — Docker is the only requirement.
- Connect an agentConnect an MCP client such as Claude Code to Who2Be — with a regular Who2Be token, no OAuth setup.
- Access on your local networkReach Who2Be from other devices on your network without rebuilding the images.
- TroubleshootingThe most common stumbling blocks when self-hosting, and what helps.
Who2Be keeps your agents’ configuration in one place — personas, processes (playbooks), knowledge documents and agents — and delivers it at runtime through an MCP server. Every change starts as a draft and has to pass a review before it becomes active.
You don’t need a cloud for any of this — Who2Be runs entirely on your own system.
The complete technical documentation
These pages are growing step by step. Until then, the complete technical documentation lives in the repository:
- README (external site) — overview, features, quickstart
- Running on a server (external site) — Docker Compose, automatic HTTPS, backups, runbook
- Connecting agents via MCP (external site) — Claude Code and Claude.ai, over HTTP or stdio
- Architecture decisions (external site) — every decision with its reasoning
- Changelog (external site) — what changed in which version