Most AI workflows fracture memory across tools: each model or service keeps its own context, so your knowledge and history get duplicated or lost. Open Brain treats your thoughts as one persistent database and an open protocol, letting any AI gateway or agent plug in and read/write the same vectorized memory — so multiple models, assistants, and frontends can compound knowledge instead of recreating it.
What Sets It Apart
- Unified persistent memory: a single database with vector search that acts as the canonical store for thoughts, summaries, and provenance — so recall is consistent across tools rather than per-app caches.
- Open protocol + MCP server pattern: clear runtime separation (capture, gateway, MCP proxy) enables third-party clients, custom gateways, and local deployments to interoperate without brittle middleware.
- Learning-path extensions and skills-first design: curated extensions (household KB, CRM, meal planner) and plain-text skill packs make the repo both a reference architecture and a teach-by-building system for real agent behaviors.
- Community-first contributions and recipes: many importers, integrations, and cooked workflows reduce friction for common data sources (chat exports, Obsidian, social exports) and support reproducible ingestion.
Who It's For & Tradeoffs
Great fit if you want a durable, model-agnostic agent memory that multiple LLMs/assistants can share (developers, privacy-minded teams, advanced hobbyists). It favors self-hosting, database and vector-search familiarity, and engineering setup (MCP server, Postgres/pgvector, deployments). Look elsewhere if you need a zero-ops hosted notes app, a simple single-user notebook, or a turn-key SaaS assistant — Open Brain is an infra layer intended to be integrated, extended, and maintained.
Where It Fits
Treat Open Brain as the “persistence + recall” layer in an agent stack: above you have model providers and UI clients; below you have Postgres/pgvector and deployment infra. It is complementary to RAG pipelines and agent frameworks that need a governed, auditable memory rather than ephemeral context.
