Why I built it.
The idea took shape in November 2025: give agents access to the company context I kept assembling myself. System configurations, business processes, and decisions lived across different tools, yet a useful solution often depended on all three.
The first MVP was ready around January 2026. Today, Company Brain connects 17 internal communication platforms, business systems, and tools. It is a production system that I also use in my own engineering work.
How it works.
Event-driven and scheduled pipelines collect, analyze, and normalize information into a shared context service. Records are indexed and embedded, with updates flowing in as the underlying sources change. This gives downstream applications a common reference for the connected company knowledge.
PostgreSQL with pgvector supports hybrid retrieval: semantic search finds related concepts across differently worded material, while lexical search preserves the precision of system names, fields, and business terminology.
Context for everyday work.
Employees can connect Claude Code or Codex, and internal agent products can use the same maintained context. Permission-aware access scopes what each user or agent can retrieve.
For me, this means less repeated briefing and more time assessing a design’s fit with the business. New tools can build on company knowledge that is already connected and prepared for retrieval.
Example: designing a sales automation.
Company Brain brings together the CRM architecture, the end-to-end client journey, and sales processes. MCP gateway access to the relevant development environments gives a coding agent the tools to investigate an implementation alongside that business context.
An illustrative prompt: “Design a follow-up workflow for leads stalled at this CRM stage.” The agent can propose triggers, fields, integration points, and exception handling in one request, giving me a design grounded in our systems to review.