MemoryAtlas

Three-stage ECL pipeline: Extract ingests 30+ multimodal formats (PDF, Slack, Notion, images, audio) via dedicated connectors with auto-OCR and transcription; Cognify runs LLM-powered entity/relationship extraction into subject-predicate-object triples with RDF/OWL ontology alignment and URI-based coreference resolution (unifying name variants across documents into canonical identifiers); Load dual-writes to a pluggable graph store (Postgres native, Neo4j, Kuzu) and vector store (pgvector, Qdrant, LanceDB). Retrieval combines graph BFS traversal, vector similarity, temporal filtering, and auto-routing query optimization; hot context is cached in session memory with transparent fallback to the persistent knowledge graph across sessions.

Storage
Dual-write: pluggable graph store (Postgres native, Neo4j, Kuzu, Neptune) and vector store (pgvector, LanceDB, Qdrant, ChromaDB, Weaviate); relational metadata via SQLAlchemy. Local self-host or managed cloud.
Retrieval
Graph BFS traversal, vector similarity, temporal filtering, and auto-routing query optimization over a persistent ontology-grounded knowledge graph; session memory cache falls through to the permanent graph for cross-session recall; agentic skill-based retrieval also supported.
Self-host
Self-host: moderate
License
Apache-2.0
Pricing
Free (1M tokens/mo included, 1 workspace); Standard $2.50/1M tokens + $5/additional workspace (unlimited workspaces, Slack/Notion/Drive integrations); Enterprise custom (BYOC, SLA, dedicated support). The former 'Hobby'/'Growth' tier names were renamed to 'Free'/'Standard' on the pricing page; terms unchanged. · Free + paid
GitHub stars
29,917
Last release
2026-08-08
Last commit
2026-08-10
First catalogued
2026-06-28

Strengths

  • Cognify stage extracts structured entity/relationship triples with RDF/OWL ontology alignment and URI-based coreference resolution, eliminating duplicate-entity drift across ingestion runs
  • Multi-hop graph reasoning via BFS traversal over the ontology-grounded knowledge graph — outperforms pure vector RAG on multi-hop QA benchmarks
  • Pluggable backends: swap graph store (Postgres, Neo4j, Kuzu) or vector store (pgvector, Qdrant, LanceDB, Weaviate) without changing application code
  • First-party adapters for LangGraph and CrewAI alongside MCP server (stdio + HTTP), REST API, CLI, and Python SDK
  • Session memory with background graph synchronization: hot context cached locally and persistent knowledge graph updated asynchronously across sessions
  • v1.3.0 (Jul 2026) adds an optional Topic Index that clusters ingested documents and generates per-cluster overviews, plus metadata filtering (tags/author/date ranges) and configurable embedding model/chunk size at ingest time

Watch out

  • No SOC2/HIPAA as of mid-2026 — disqualifying for regulated data
  • RDF/OWL ontology alignment in the Cognify stage requires semantic-web expertise; teams without this background face a steep learning curve when customizing or debugging graph extraction pipelines
  • Graph BFS traversal is slower than pure vector RAG; TB-scale deployments require manual Neo4j sharding and vector store cluster tuning — self-host operational burden grows substantially at production scale

Best for

  • Cross-document multi-hop reasoning where entity identity must be preserved across ingestion runs (legal, finance, research evidence graphs)
  • LangGraph or CrewAI agents needing first-party persistent memory without building a custom graph layer
  • Enterprise knowledge-graph workflows over large mixed-format corpora where ontology-backed deduplication matters

How it integrates

Benchmark results

BenchmarkValueBackboneTrustSource
beam-10m0.67 accuracySelf-reportedcognee maintainers (README Benchmarks section)

Sources

Last verified 2026-08-01 · updated by refresh-framework-cards