Back to directory

KektorDB

A memory system for AI agents that pairs vector search with a temporal knowledge graph and a background process that consolidates memories, flags contradictions and lets unused facts fade over time.

KektorDB

KektorDB combines high-performance vector search using HNSW with a temporal knowledge graph and what it calls a cognitive engine, which continuously analyzes stored data, detects contradictions, tracks importance, and lets irrelevant information fade naturally rather than growing without bound.

A background process it calls the Gardener consolidates duplicate memories, detects when a new fact contradicts an established one, identifies gaps in the knowledge graph, and can propose or, in its more autonomous mode, automatically resolve minor contradictions. A separate scoring system assigns each memory a confidence level of crystallized, stable, volatile or contested, based on how consistently it has been confirmed. Once set up, an agent connected over MCP gains dozens of tools covering memory storage and recall, graph traversal, session management and confidence queries.

It is set up and run through a single command-line tool.

More in Agent memory

See all 450
  • A long technical guide to AI agent memory: why stateless LLMs need it, the different memory architectures from vector stores to knowledge graphs, and how Cognee implements one as an open-source memory layer.

  • A local, file-based long-term memory layer for a personal AI that never summarizes conversations, keeping every line with a timestamp and searching by time first and words second, rather than retrieving only similar-seeming chunks.

  • NEOTH

    deepwiki.com

    A local-first personal AI daemon in Rust with five memory tiers, consent-gated tools, a WASM plugin sandbox, multi-provider model routing and signed audit logs, aimed at people who want both a daily assistant and a serious coding helper.