Is Zep enough for chat memory?
Often yes for chat-centric memory. Myco targets broader, organization-wide memory and governance needs.
Comparison
Myco vs Zep: Session Memory API vs Source-Backed Organizational Memory
Zep provides a practical memory API for conversational systems. Myco expands that into organizational memory with a deterministic write path and explicit provenance.
| Feature | Myco | Zep |
|---|---|---|
| Primary scope | Org memory graph | Conversation memory |
| Deterministic write path | Yes | Not a stated focus |
| Fact-level provenance | First-class via brain_why | Partial |
| Content-hash deduplication | Yes | — |
| Workspace-scoped isolation | Yes | — |
| Import ChatGPT/Claude history | mycobrain-ingest --from chatgpt/claude-export | — |
| Read-only REST for non-MCP consumers | mycobrain-rest (search + why, loopback) | — |
| Deployment options | Self-hosted (Apache-2.0); managed cloud waitlist | Cloud-focused |
Bottom line
If your requirement is explainable memory with source-level traceability and auditable provenance for every fact, Myco provides deeper controls.
FAQ
Does Myco include search plus graph traversal?
Yes. brain_search covers full-text search out of the box, and semantic search keyless with local Ollama embeddings (OpenAI optional). brain_neighbors traverses the knowledge graph.