Self-hosting
Who2Be on your own machine
The same source code our cloud will run on. Docker is the only requirement — no Python, no Node, no config file.
- Free
- Every feature
- Your data stays with you
your machine · Docker
- Web interfacelocalhost:5173
- MCP serverlocalhost:8765/mcp
- REST APIlocalhost:8000
- Sign-inlocalhost:9999
- DatabasePostgres · 5432
Up and running in three steps
- 1
Start
The first start builds the images from source and takes a few minutes. You can also pull prebuilt images — with the second command from the guide in the repository.
git clone https://github.com/luetzey/who2be.git && cd who2bedocker compose up -d --wait - 2
Open
Open
http://localhost:5173and create an account — locally, it’s confirmed instantly without sending any email. You land in a workspace of your own. - 3
Connect an agent
Under Settings → Tokens, you create a token and copy the ready-made client configuration. The MCP server accepts this token — no OAuth setup needed. For Claude Code, you can also do it by hand:
claude mcp add --transport http who2be http://localhost:8765/mcp \ --header "Authorization: Bearer ***"Replace
***with your token. Running over stdio is covered in the docs.
If you want more
From another device on your network
The interface talks to the address it was loaded from. For sign-in and invitation links to work, set the same address for the backend as well:
WHO2BE_PUBLIC_URL=http://192.168.1.42:5173 docker compose up -d --waitOutside a trusted network, you need the hardened setup with TLS.
On a server
A ready-made setup with Docker Compose and automatic HTTPS — the foundation our cloud will run on, too.
- Automatic HTTPS
- Security headers
- Backup service
- Runbook for recovery and key rotation
What the license allows
Who2Be is licensed under the Functional Source License 1.1 with an Apache 2.0 future. Internal use — including in a company, including commercially — is free. What’s not allowed is selling Who2Be as a competing hosted service.
If you need a commercial license beyond that, you’ll find the contact address in the legal notice.
What you take care of yourself
Updates and backups
Including recovery when something fails.
Encryption
Of the database volume. The production setup describes how; setting it up is up to you.
Availability
There’s no guarantee from us, because it’s your server.
Too much to run?
The cloud is expected in late 2026 — same software, and we take care of it.