Skip to content

docs: add a Why section to the README - #7

Merged
springfall2008 merged 2 commits into
mainfrom
docs/readme-why
Nov 7, 2026
Merged

springfall2008 merged 2 commits into
mainfrom
docs/readme-why

Conversation

@springfall2008

Copy link
Copy Markdown
Owner

Adds a Why section after the intro: what the project is for, and how it differs from other memory tools.

  • Hosted in your own Supabase project, versus hosted SaaS memory (Mem0 Platform, Supermemory, Zep) or self-hosted servers you run yourself (mcp-memory-service, Graphiti, Cognee)
  • Per-member, per-scope read/write enforced by Postgres RLS
  • Threads for agent-to-agent handoff
  • No LLM in the write path
  • Team administration: audit log, soft delete, backups

It also says when a single-user tool is simpler.

The comparison is based on public write-ups of those tools as of Nov 2026, several of which are vendor-authored, so the claims about other projects are kept general.

🤖 Generated with Claude Code

springfall2008 and others added 2 commits November 7, 2026 18:28
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@springfall2008
springfall2008 merged commit 856842e into main Nov 7, 2026
1 check passed
@springfall2008
springfall2008 deleted the docs/readme-why branch November 7, 2026 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant