Product · The Brain

Your business, mapped — not documented

The Brain is a typed model of how your business works: the entities that matter, how they relate, the rules that govern them, and the words your team actually uses for all of it.

Connect a database schema, a set of internal docs, or another MCP server, and BrainBox builds the model. For databases, it reads schema metadata and field properties only — tables, columns, types, relationships — never the rows themselves. Your records stay in your systems.

Connect a second source and it enriches the same brain — nothing gets rebuilt or replaced. Docs layer definitions and policy onto the structure the schema provides, and conflicts between sources are resolved by authority, not by whichever loaded last.

What the model holds

Typed entities & relationships

Customer, Invoice, RevenueTarget — each with properties, natural keys, and the join paths that connect them across systems.

Governing rules

The conditions behind business terms: what qualifies as "active," when a grace period applies, which states an order can legally move between.

Vocabulary & aliases

What your team calls things — "ARR," "settlement," "churn" — mapped to the fields and entities they actually refer to, including when two systems name the same thing differently.

Provenance on every fact

Each entity, rule, and definition is attributed to the source that produced it and the curation that confirmed it — an answer is never just an assertion.

Curated by your team, not just generated

The Brain proposes; your experts decide. Anyone who knows the business can review a proposed entity, rule, or definition and correct it directly — and the correction sticks.

One brain per customer, if you need it

BrainBox isn't limited to one shared model per org. If you're building a product that serves your own customers, each gets an isolated brain with hard boundaries. See multi-tenant context and the developer platform.

In practice

How it grounds an agent

# agent, mid-task:

“Which customers count as active?”

→ recall_domain("active customer")

← active customer: status = 2 AND churned_at IS NULL.
   Rule owned by RevOps; source: billing schema + policy doc, curated 3 weeks ago.

Without the Brain, the agent guesses from column names. With it, the definition — and where it came from — is one tool call away.

Give your agents a brain.

Grounded answers, not guesses — from a living model of your business.

Book a Demo