Conductor
§ 01 A knowledge product

Knowledge bases
that compile
themselves.

Drop in raw notes, specs, transcripts — whatever's lying around in your /scratch folder. Conductor turns them into a connected wiki you can search, browse, and plug into Claude, Cursor, or any AI tool that speaks MCP.

See pricing See how it works
  • Self-hostable on Fly, Render, anywhere
  • Your Claude. Your tokens. We never touch your key.
  • MCP server included
§ 02

How it works

Three primitives. Pipe in. Compile. Query. Everything else is on top of that.

  1. 01

    Ingest.

    Drop in markdown, transcripts, links, half-finished specs, meeting dumps. No structure required. The ingest_document tool takes anything that's text-shaped. 

    $ conductor ingest \
    --project acme \
    --tags spec,billing \
    ./scratch/billing-rewrite.md
  2. 02

    Compile.

    Your AI tool reads everything and writes interconnected wiki articles — with cross‑links, source citations, and lint checks for orphans and stale content. It's a build step. For knowledge. 

    you › compile the acme knowledge base

claude › calling conductor.compile()
✓ 12 new articles written
✓ 4 updated, 0 stale
✓ 38 cross‑links resolved
  3. 03

    Query.

    Browse the wiki in the dashboard. Or plug it into Claude, Cursor, your own agent — any tool that speaks MCP gets read access scoped to the right org. 

    Authorization: Bearer kbm.acme.•••••••
→ search("billing rewrite")
← 7 articles · 41 backlinks
§ 03

Built for the people
who keep the context.

Operators

Consultants & agencies running KBs for many clients.

Multi-tenant from day one. Each client gets their own org, their own users, their own MCP tokens, their own subdomain — you stay one logical layer above it all.

Builders

AI-native product teams that want their own docs queryable by their own agents.

The MCP server isn't a side feature — it's the point. Your agents read the wiki the same way you do, scoped to the same org, with the same permissions.

Solos

Operators drowning in scratch files, transcripts, and unfinished thoughts.

One org. One pile of raw. One nightly compile. Wake up to a wiki that organizes itself. Compounds every time you add to it.

§ 04

Pricing.

Compile runs in your own AI tool — Claude Code, Cursor, anything that speaks MCP — so your tokens never touch our infrastructure. Anthropic bills you at cost. We charge for the platform.

Starter

$ 99 /mo

+ $499 one-time setup

For solo operators & one-client consultancies.

  • 1 client workspace
  • 5,000 documents
  • MCP API tokens
  • Per-org users + roles
  • Your Claude, your bill — not ours
  • Email support
Get started
Most popular

Studio

$ 349 /mo

+ $1,500 one-time setup

For consultants juggling a handful of clients.

  • Up to 5 client workspaces
  • 25,000 documents per workspace
  • Custom subdomain per client
  • MCP API tokens (per user)
  • Per-org users + roles
  • Your Claude, your bill — not ours
  • Priority support, 1 business day
Get started

Agency

$ 999 /mo

+ $4,999 one-time setup

For shops running KBs at scale.

  • Unlimited client workspaces
  • 100,000 documents per workspace
  • White-label per client
  • SSO (SAML / OIDC) + audit log
  • Dedicated Slack channel
  • Your Claude, your bill — not ours
  • Signed SLA
Get started
§ 05

Stop losing context.
Start compiling.

We provision your workspace, migrate your first batch of docs, and hand you the keys. You bring the Claude.

Talk to us

Or jump straight to pricing