Skip to content

Instantly share code, notes, and snippets.

@umit
Created August 28, 2026 07:09
Show Gist options
  • Select an option

  • Save umit/55c4920657df854df70d405595b582cd to your computer and use it in GitHub Desktop.

Select an option

Save umit/55c4920657df854df70d405595b582cd to your computer and use it in GitHub Desktop.
Company Brain, agent memory, knowledge graph and ontology products

Company Brain, Agent Memory, Knowledge Graph and Ontology Products

A practical list of products and implementation patterns for building company brains, agent memory, knowledge graphs, and ontology-backed AI systems.

1. GBrain

Garry Tan's open-source personal brain. Your email and calendar flow into a Git repo, and a nightly job re-links everything and flags what's gone stale.

2. mem0

A memory library you call from your own code. It only stores what you explicitly tell it to, and ranks fresh facts above idle ones at search time.

3. Letta

For building agents that remember across sessions. The agent decides what's worth keeping, and a second agent tidies up its memory in the background.

4. Zep / Graphiti

A knowledge graph with a clock in it. When a fact changes, the old one gets an end date instead of being overwritten, so you can still ask what was true last March.

5. Sylph

A content brain that lives entirely in a Git repo. Agents write drafts, humans publish, and afterwards the agent reads your edits to learn what it got wrong.

6. DIY (Claude Code + Git)

What most engineering teams actually do. Markdown in the repo, grep instead of search, and pull requests as the only thing keeping it honest.

7. Pletor

A brand brain for marketing teams. Campaigns, assets, and performance data in one tree, and the brand rules only move when a human signs off.

8. Gorgias Cortex

Built in-house by an eight-person AI team. 12,000 Markdown nodes in GitHub, and every night the questions it got wrong become PRs that fix it.

9. Slite Agent

For teams whose knowledge lives in docs and across sources. It watches ~20 connected tools (Slack, Drive, GitHub, Jira, etc.) for what's gone stale and sends the diff to whoever owns the page. Nothing changes without human approval.


Source context: Company Brain research and examples.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment