01 · Connect
Bring your company sources
Documents, Notion, Slack, and Drive flow into one organization-scoped workspace.
Connectors · uploads · sync
The context backend for AI-native companies · local-first MVP
Think Supabase — for your company's knowledge
Build your company brain.Ship context-aware AI.
Komponist is the backend platform for company context: connect scattered sources, turn them into reviewed knowledge with citations, then serve the same truth to your team, product, and AI agents.
One workspace per organization Human-governed API + MCP ready
komponist / demo-api
Checking API
Sources
UPProduct strategy6 facts
UPSecurity policy6 facts
NONotion workspaceconnected
+ connect source
Context graph
MVP launch
confirmed
Project
Goal10 partners
Decision4 entity types
ConstraintReview first
Evidencestrategy.md
Retrieving confirmed context…
Komponist is checking the demo workspace.
No Dave required. ✓
One context layer underneathHumans+Claude+OpenAI+Codex+Your agent
The company context stack
The backend your agents are missing.
Supabase gives applications a database, auth, and APIs. Komponist gives AI applications governed company memory, retrieval, and agent access.
Not another chatbot · shared infrastructure for every AI surface
02 · Govern
Build trusted company memory
Komponist extracts durable facts, links them in a graph, and keeps a human in control.
Entities · evidence · review
03 · Serve
Give context to every interface
People use Studio. Products and agents use the same knowledge through API and MCP.
Studio · chat · API · MCP
Platform primitives
Company context without the document archaeology.
The dashboard and infrastructure come together. Start with documents today; connect every teammate, product, and agent tomorrow.
01
Ingest the useful stuff
Upload documents or connect Notion. Komponist extracts decisions, goals, constraints, and projects — not another pile of chunks.
Sources → facts →
02
Review before trust
Every new fact enters a human review queue with confidence, exact evidence, and its original source attached.
Governed by default →
03
Keep the relationships
Projects advance goals. Decisions affect projects. Constraints stay connected to the work they shape.
Context graph →
04
Ask with receipts
Chat across confirmed company knowledge. Every answer carries citations an engineer — or an agent — can inspect.
Cited answers →
05
One brain per workspace
Organization-scoped users, roles, credentials, API keys, and revocation keep customer context separated.
Multi-tenant →
06
Built for agents too
Expose the same confirmed brain over MCP and API so coding agents stop guessing what the company decided.
MCP + API →
Three steps
From messy source to useful brain.
No migration project. No ontology workshop. No mysterious answer without a source.
01
Drop in a document
Markdown, text, or YAML. Raw uploads are processed in memory.
02
Confirm the facts
Approve what is true, reject what is noise, keep every citation.
03
Call the brain
Ask in Studio or connect an agent through your scoped MCP key.
Agent interface
A company brain you can call.
Use the same confirmed context in Studio, your own product, or any MCP-compatible coding agent.
- Organization-scoped API keys
- Citations and entity metadata
- Revocable access for every agent
ask-komponist.tsMCP · API
import { createKomponistClient } from "@komponist/sdk"
const komponist = createKomponistClient({
url: process.env.KOMPONIST_URL!,
apiKey: process.env.KOMPONIST_API_KEY!
})
const { data, error } = await komponist.context.search(
"What did we decide?",
{ types: ["Decision", "Constraint"] }
)
// confirmed facts · citations · org isolated
data?.items[0].evidence✓ Context compiled. Nothing invented.
Local MVP · ready to test