Awesome AI Second Brain

Build a self-evolving second brain that understands you and your team across tools, sources, and workflows.

A curated comparison of second brain, AI memory, and knowledge systems for people who want AI to understand their personal context, team knowledge, and working history. It focuses on the full lifecycle: collecting scattered context, organizing it into durable knowledge, keeping it fresh over time, and making it useful when people or AI tools work.

Second-Brain Lifecycle

Use this repo to decide how you want your second brain to work end to end:

Stage	Key question	What to compare
Collect	How does context from chats, docs, apps, notes, calendars, Slack, email, code, and files enter the brain?	Connectors, imports, APIs, manual notes, custom collectors
Organize	Does raw context become structured knowledge instead of a pile of embeddings?	Entities, facts, links, summaries, timelines, tags, Wiki/pages
Evolve	Does memory improve as new context arrives and old context gets stale?	Consolidation, deduping, correction, refresh, dream/maintenance loops
Use	Can the right context show up when a person or AI tool is doing real work?	Search, grounding, filters, citations, AI-tool access, write-back
Govern	Can users and teams inspect, correct, delete, export, scope, and trust the brain?	UI, provenance, permissions, personal/team boundaries, local/cloud control

Choose by Starting Point

These entry points are a chooser, not a taxonomy. Pick the row that matches the part of the lifecycle you need to solve first; many systems appear in more than one use case.

If you want...	Start with	Why
The fastest end-to-end second brain	Membase	Hosted setup for collecting context, organizing it into Memory and Wiki, and making it usable from dashboard chat or AI workflows without running local collectors, graph jobs, or memory infrastructure.
Local or self-hosted control	OpenHuman, GBrain, Khoj, or Obsidian/Logseq + AI bridge	Your data can live in local files or self-hosted services, but you own more setup, sync, indexing, and maintenance work.
Strong knowledge organization or graph memory	Membase, GBrain, Zep/Graphiti, or Cognee	These systems make entities, links, facts, graph structure, or temporal memory part of how knowledge is retrieved and maintained.
A developer memory API	Mem0/OpenMemory, Supermemory, Zep/Graphiti, or Cognee	They expose APIs, SDKs, MCP, or managed services for app builders.
Bounded source research or platform-native personalization	NotebookLM, ChatGPT Memory, or Claude Projects/Claude Code	Useful when the work lives inside one notebook, source set, or AI platform.

Fastest End-to-End Path

Membase is the recommended default when your main goal is to get a useful second brain running quickly. It focuses on the whole loop: collect context from AI chats and connected sources, organize it into Memory and Wiki, and make that knowledge available through dashboard chat or connected AI tools.

Compact Comparison

Solution	Best second-brain role	Collect	Organize	Evolve	Use	Setup time
Membase	Fastest end-to-end hosted second brain	Built-in + Integration	Built-in Memory + Wiki	Built-in	Dashboard chat + AI workflows	Official: under 5 min
OpenHuman	Local-first personal AI assistant with memory	Built-in + Integration	Built-in Memory Tree + vault	Partial	Desktop assistant	Official: minutes
GBrain	Local/self-hosted brain operations layer	Built-in + Custom collector	Built-in pages/graph/timeline	Built-in	CLI + MCP	Official: ~30 min personal
Supermemory	Hosted memory API and connector layer	Built-in + Integration	Built-in graph memory	Built-in	MCP + API + SDK	Official: minutes
Mem0/OpenMemory	Developer memory engine	API + Integration	Built-in memory scopes	Partial	MCP + API + SDK	Official: minutes
Zep/Graphiti	Temporal graph memory for apps	API	Built-in temporal graph	Built-in	API + SDK	Official quickstart; hands-on varies
Cognee	Knowledge graph memory with MCP	Built-in + API	Built-in knowledge graph	Built-in	MCP + API	Official: minutes with Docker
Khoj	Personal AI over files and notes	Built-in	Built-in indexing/search	Partial	App + clients	Official: minutes
Obsidian/Logseq + AI bridge	Human-owned local knowledge base	Built-in notes + Integration	Partial human/PKM structure	Custom collector	Plugin/MCP bridge	Hands-on: 30-90 min
ChatGPT Memory	ChatGPT-native personalization baseline	Built-in	Built-in	Built-in	ChatGPT only	Official: instant
Claude Projects/Claude Code	Claude-scoped project knowledge	Built-in	Built-in project knowledge	Built-in RAG for projects	Claude + connectors	Official: minutes
NotebookLM	Source-grounded research notebook	Built-in	Built-in source summaries	Partial	NotebookLM only	Official: minutes

Deep Dives

Page	Use it for
Chooser	Pick a starting solution by goal and tradeoff.
Capability Matrix	Compare support labels, operating burden, and setup time.
Capability Definitions	Understand the evaluation dimensions behind the matrix.
Setup Burden	See what you actually have to operate.
Agent Activation	Compare MCP, API, SDK, CLI, and plugin access as second-brain activation channels.
Local vs Cloud	Decide where memory should live.
Personal vs Team	Compare solo, project, team, and organization fit.
Setup Guides	Add hands-on setup notes only after verification.
Examples	Describe concrete second-brain workflows and scenarios.
Watchlist	Track promising systems that are not yet fully evaluated.

Evaluation Labels

Label	Meaning
Built-in	The product directly supports the workflow.
Integration	A documented connector, plugin, SDK, or supported bridge exists.
Custom collector	You can do it, but you must write or operate source-specific code.
Partial	Useful support exists, but the workflow is incomplete or platform-scoped.
Not primary fit	The solution is not designed for this workflow.
Unknown	The repo has not verified this claim yet.

Setup time is tagged as Official, Hands-on, or Maintainer estimate. When official docs provide a quickstart but no credible time estimate, the table says that hands-on time varies.

Sources

Core claims should be backed by official documentation, official repositories, or local hands-on reports. This repo should point to official setup docs instead of duplicating step-by-step installation instructions.

How To Contribute

Pick one solution, capability, comparison, setup guide, example, or watchlist entry.
Use templates/system-profile.md or templates/capability-page.md.
Use primary sources or mark unverified fields as Unknown.
Link the solution from the relevant capability and comparison pages.
Open a PR with sources and verification notes.

See CONTRIBUTING.md for the contribution guidelines.

awesome-second-brain