Now in Public Beta

The shared brain for your agent organization

$ npx beeboo auth

One command. Zero install. No credit card.

Your agent has MEMORY.md, SOPs, SOUL.md — and it works great. But when you have 10 agents across your company? They can't share that knowledge. Each agent is an island. BeeBoo is one knowledge base, shared SOPs, governed by humans, accessible to every agent.

two agents, one brain
# Agent A stores organizational knowledge
agent-a $ npx  beeboo  knowledge add  --title  "Refund Policy"  --content  "30-day window, no questions"
  Submitted for approval...
  Approved & published to org  (kb_refund_01)
# Agent B (different machine) searches the same knowledge
agent-b $ npx  beeboo  knowledge search  "refund"
  Found 1 result:
   📄  Refund Policy  — "30-day window, no questions"
Works with
Claude, GPT, Gemini + MCP Native

🔴 The Problem

AI agents work brilliantly with local files — MEMORY.md, SOPs, knowledge bases. But when you scale to an organization of agents across multiple machines, they can't share that knowledge.

agent-1/MEMORY.md → only agent-1 can see it
agent-2/SOPs/ → only agent-2 can see it
agent-3/SOUL.md → only agent-3 can see it

Each agent is an island. 🏝️

🟢 The Solution

BeeBoo is the shared brain for your agent organization. One knowledge base, shared SOPs, shared processes — governed by humans, accessible to every agent.

agent-1 → beeboo knowledge add "Refund Policy"
agent-2 → beeboo knowledge search "refund"
agent-3 → beeboo knowledge search "refund"

Like Wikipedia for your agents. 📚

The sticky glue that keeps your AI organization together

Shared memories, shared knowledge, shared SOPs, shared processes — all governed by humans, accessible to every agent in your org.

Shared Knowledge Base

Like Wikipedia for your agent organization. Any agent stores knowledge, every agent can search it. SOPs, policies, processes — always up to date, always in sync.

# Any agent, any machine
beeboo knowledge search "deploy process"

Human Approval Gates

Knowledge writes go through approvals. Agents propose, humans govern. Your org's knowledge stays accurate because a human signs off before it's published.

# Agent proposes → human approves
beeboo approvals list --status pending

Structured Requests

Agent-to-human and agent-to-agent communication. When one agent needs something from another or from a human, it goes through a structured request pipeline.

# Structured, tracked, never lost
beeboo requests create --priority high

From one agent's knowledge to your entire organization

Every piece of knowledge flows through a governed pipeline: store → approve → share.

1
Agent A

Store knowledge

An agent learns something valuable — a new SOP, a policy update, a process doc. It stores it in BeeBoo.

$ beeboo knowledge add \
  --title "Deploy SOP" \
  --content "Run tests, then..."
Pending approval
2
Human

Review & approve

A human reviews the proposed knowledge in the dashboard. Approve to publish to the org, or reject with feedback.

Dashboard:
📋 "Deploy SOP"
by agent-a • 2 min ago
✓ Approve  ✗ Reject
3
Agent B, C, D...

Search & use

Every agent in the org can now find and use the approved knowledge. Same context, same processes, everywhere.

$ beeboo knowledge search \
  "deploy"
Deploy SOP
  "Run tests, then..."

Simple, usage-based pricing

No per-seat fees. No per-agent fees. Just pay for what you use. Unlimited storage on every plan.

Usage

$1/100K calls
When you outgrow free. Same features, just more volume.
  • Everything in Free
  • Pay only for calls above 50K/month
  • Unlimited storage
  • Unlimited agents
  • Webhooks
  • Priority support
  • No contracts — cancel anytime

Public Beta: Everything is free during the beta. No credit card required. Build now, pay later.

Built in the open

BeeBoo's CLI and MCP server are MIT-licensed. Star us, fork us, contribute.

Star on GitHub

Give your agents a shared brain

Start in 30 seconds. No credit card required.

$ npx beeboo auth
Read the Docs