Sign up

Go to hanzo.id and sign in with email, GitHub, Google, or wallet. The first user to sign up under your domain becomes the owner. You are redirected to console.hanzo.ai.

See Getting Started for the per-method details.

Create your organization

In the console:

1. Click your profile menu → Switch organization → Create organization.
2. Enter a slug (e.g. startx). This becomes your namespace everywhere in Hanzo — IAM, brain, bot, team.
3. Invite teammates by email. They will receive a sign-in link bound to your org.

Roles ship with the org:

• owner — full admin
• admin — manage members and projects
• member — use API keys and resources

See Organizations for the full role matrix.

Generate a scoped API key

From the console, Projects → New Project → API Keys → Create Key.

hk-proj-org-startx-abc123...

Copy it now. Set it in your shell:

export HANZO_API_KEY="hk-proj-org-startx-abc123..."

This single key is the credential for every Hanzo service. The gateway routes calls based on the key's project scope.

Seed secrets into KMS

Hanzo KMS holds anything you would otherwise stuff into a .env file: channel tokens, third-party API keys, signing keys.

# Authenticate (one-time) — uses your active hanzo.id session
hanzo kms login

# Seed a Slack bot token under your org
hanzo kms put /channels/slack/BOT_TOKEN "xoxb-..." --org startx

# Seed an OpenAI key
hanzo kms put /providers/openai/API_KEY "sk-..." --org startx

Every downstream Hanzo service reads from KMS at startup — you never paste secrets into a YAML file. See KMS Quickstart.

Install a brain profile

A brain profile is a saved starting state for Hanzo Brain: schema, seeded pages, embedding model, search weights.

Pick the one that fits your org:

Install:

npm install -g @hanzo/bot
hanzo-bot brain install founder --org startx

That writes ~/.hanzo/brain/startx/brain.db, seeds it with the founder profile content, and registers it with your Hanzo org. From now on every agent, bot, and MCP call your org makes reads and writes through that brain.

The brain file is byte-identical across runtimes — you can swap the Go binary in later without re-seeding:

go install github.com/hanzobot/go/cmd/hanzo-bot@latest
hanzo-bot brain status --org startx   # same file, same ids

See Brain for the full algorithm surface.

Wire up the bot

The bot is the gateway between every channel and your brain + agents.

hanzo-bot serve --org startx

That starts the bot, connects to every channel for which it found a token in KMS, and routes inbound messages through the agents framework against your seeded brain.

Add a channel later:

hanzo kms put /channels/discord/BOT_TOKEN "..." --org startx
hanzo-bot reload

See Bot and hanzobot/ts for adapter details.

Stand up the team workspace

Hanzo Team gives your org a shared workspace: docs, tasks, calls, meetings, files. It uses the same IAM identity so your existing org members sign in with one click.

hanzo team open --org startx

That provisions a team workspace at team.hanzo.ai/startx (or your custom domain) and joins every IAM member.

Test the full path

Send a message to one of your wired channels:

What's on the roadmap?

What happens behind the scenes:

Channel (Slack)
   │
   ▼
Hanzo Bot      ──► reads ~/.hanzo/brain/startx/brain.db   (Brain)
   │                ─► hybrid search finds the right page
   ▼
Hanzo Agents   ──► dispatches to the agent that owns the topic
   │                ─► agent calls Hanzo LLM Gateway with HANZO_API_KEY
   ▼
Hanzo IAM      ──► validates token, checks org scope (X-Org-Id)
   │
   ▼
Reply in Slack

Every step is scoped to startx. Teammates outside the org cannot read or write the brain even if they have a Hanzo identity.

Add a teammate

Already invited from step 2. They click the email link, sign in via hanzo.id, land in startx's console. Their messages flow through the same bot, the same brain, the same agents.