Structured Knowledge Graph Storage

via “json file-based persistence with atomic writes”

Persistent knowledge graph memory storage for LLM conversations.

Unique: Uses a simple JSON file as the storage backend rather than a database, making the implementation portable and debuggable. The entire graph is serialized on each write, prioritizing simplicity and correctness over performance — suitable for reference implementation but not production use.

vs others: More portable than database-backed persistence because it requires no external services or setup; more inspectable than binary formats because the JSON is human-readable; simpler than transaction-based systems because it avoids complex consistency logic.

via “entity and relationship system for knowledge graph construction”

TypeScript framework for autonomous AI agents — multi-platform, plugins, memory, social agents.

Unique: Integrates entity and relationship tracking directly into agent memory system rather than as separate knowledge graph layer, enabling automatic knowledge graph construction from agent interactions. Entities and relationships are stored with embeddings for semantic queries.

vs others: More integrated than external knowledge graph systems (no separate service) but less sophisticated than dedicated graph databases; better for agent-centric knowledge tracking than general-purpose knowledge graphs.

via “knowledge graph construction and property graph indexing”

LlamaIndex is the leading document agent and OCR platform

Unique: Automatically constructs property graphs from documents using LLM-based extraction with pluggable graph stores and hybrid vector+graph retrieval. Unlike LangChain's graph integrations (which focus on querying existing graphs), LlamaIndex automates graph construction from unstructured documents.

vs others: Enables end-to-end knowledge graph construction from raw documents with automatic entity/relationship extraction, whereas LangChain requires pre-built graphs or manual extraction.

via “graph visualization and knowledge graph exploration”

⚡️AI Cloud OS: Open-source enterprise-level AI knowledge base and MCP (model-context-protocol)/A2A (agent-to-agent) management platform with admin UI, user management and Single-Sign-On⚡️, supports ChatGPT, Claude, Llama, Ollama, HuggingFace, etc., chat bot demo: https://ai.casibase.com, admin UI de

Unique: Integrates graph visualization directly into the knowledge base UI, allowing users to explore document relationships visually without external tools. Entity relationships are automatically extracted from indexed documents.

vs others: More integrated than standalone graph tools because graph data is derived from the knowledge base and visualization is part of the native UI, enabling seamless exploration.

via “graph-based-rag-with-knowledge-graphs”

This repository showcases various advanced techniques for Retrieval-Augmented Generation (RAG) systems. Each technique has a detailed notebook tutorial.

Unique: Converts documents into structured knowledge graphs with entities and relationships, enabling retrieval based on graph structure and relationship patterns rather than text similarity — a structural approach that captures semantic relationships explicitly

vs others: More effective for relationship-dependent queries than text-based retrieval because it explicitly models connections between entities, and more scalable than storing full documents because it stores compressed graph representations

via “graph-based memory storage with semantic relationship indexing”

AI memory OS for LLM and Agent systems(moltbot,clawdbot,openclaw), enabling persistent Skill memory for cross-task skill reuse and evolution.

Unique: Uses property graphs with typed relationship edges (not just vector similarity) to encode semantic structure, enabling graph traversal queries and causal reasoning — unlike vector-only RAG systems (Pinecone, Weaviate), MemOS maintains explicit relationship semantics for structured memory navigation.

vs others: Supports relationship-aware queries and deduplication that vector databases cannot express, at the cost of higher operational complexity; better for agents needing causal chains, worse for pure similarity search at scale.

via “knowledge graph temporal entity-relationship tracking”

The best-benchmarked open-source AI memory system. And it's free.

Unique: Implements temporal knowledge graph in SQLite with explicit timestamp tracking for each triple, enabling time-series reasoning about fact evolution. Most knowledge graphs (Neo4j, ArangoDB) don't emphasize temporal queries; MemPalace treats time as a first-class dimension.

vs others: Simpler than external graph databases (no DevOps overhead) while supporting temporal reasoning that vector-only systems cannot express.

via “knowledge graph and graphrag support for structured reasoning”

Open-source LLM knowledge platform: turn raw documents into a queryable RAG, an autonomous reasoning agent, and a self-maintaining Wiki.

Unique: Integrates knowledge graph construction as an optional enhancement to RAG, allowing queries to traverse entity relationships for multi-hop reasoning. Graph construction is async and does not block document indexing.

vs others: More structured than flat document retrieval (relationships are explicit), more scalable than manual knowledge curation (automatic extraction), and more interpretable than pure semantic search (reasoning paths are visible).

via “knowledge graph construction with entity extraction and community detection”

SoTA production-ready AI retrieval system. Agentic Retrieval-Augmented Generation (RAG) with a RESTful API.

Unique: Integrates LLM-based entity extraction with networkx community detection in a single pipeline, enabling automatic semantic clustering without manual ontology definition. Graph is stored in PostgreSQL alongside document vectors, allowing hybrid queries that combine vector search with graph traversal.

vs others: More flexible than Neo4j's built-in extraction because entity types and relationships are configurable via LLM prompts; more integrated than standalone knowledge graph tools because graph is queried alongside RAG retrieval in the same API call.

via “typed-knowledge-graph-storage-and-querying”

Open-source persistent memory for AI agent pipelines (LangGraph, CrewAI, AutoGen) and Claude. REST API + knowledge graph + autonomous consolidation.

Unique: Implements a typed knowledge graph within a relational database (SQLite/D1) rather than a dedicated graph database, enabling lightweight deployment without external infrastructure. Supports autonomous relationship inference based on semantic similarity and metadata, allowing agents to discover indirect connections without explicit programming.

vs others: Simpler to deploy than Neo4j or ArangoDB because it uses standard SQL; more semantically rich than flat vector stores because relationships carry type information that enables domain-aware reasoning.

via “knowledge graph generation from unstructured text via llm-driven entity and relationship extraction”

The memory for your AI Agents in 6 lines of code

Unique: Implements a dual-storage architecture where extracted triplets are simultaneously indexed in both graph and vector databases (cognee/infrastructure/databases/), enabling hybrid queries that combine structural graph traversal with semantic vector similarity. Supports custom graph models via Pydantic schemas, allowing developers to define domain-specific entity types and relationship types without modifying core extraction logic.

vs others: Outperforms single-database RAG systems (like Pinecone-only or Neo4j-only) because it preserves both structural relationships (for reasoning) and semantic similarity (for relevance), reducing hallucination through multi-path validation; more flexible than LlamaIndex's graph RAG because custom schemas are first-class citizens.

via “graph network construction and traversal for knowledge representation”

💡 All-in-one AI framework for semantic search, LLM orchestration and language model workflows

Unique: Graph networks are co-indexed with vector embeddings in the same storage backend, enabling atomic graph + vector queries without separate graph database; supports relationship-aware retrieval where graph traversal results are automatically merged with semantic search results

vs others: Simpler than Neo4j + vector DB because graph and vector search are unified in one index, but less feature-rich for complex graph algorithms; better for RAG use cases where you want relationship-aware retrieval without operational complexity of dual systems

via “hierarchical project-task-knowledge graph modeling via neo4j”

A Model Context Protocol (MCP) server for ATLAS, a Neo4j-powered task management system for LLM Agents - implementing a three-tier architecture (Projects, Tasks, Knowledge) to manage complex workflows. Now with Deep Research.

Unique: Uses Neo4j as the primary persistence layer with a three-tier node schema (Project, Task, Knowledge) rather than relational tables or document stores, enabling agents to reason about complex dependency graphs and perform relationship-aware queries without JOIN operations or denormalization.

vs others: Outperforms relational databases for deep hierarchical queries and dependency traversal; more structured than document stores (MongoDB) for maintaining strict entity relationships and enabling graph-based reasoning by LLM agents.

via “knowledge graph construction and traversal”

Project-local RAG memory MCP server — knowledge graph + multilingual vector + FTS5 in a single SQLite file. Per-project isolation, 30 MCP tools, codepoint-safe chunking (Korean/CJK/emoji).

Unique: Integrates knowledge graph construction directly into MCP server, allowing LLM agents to reason over structured entity relationships alongside vector similarity, rather than treating the knowledge base as unstructured text chunks

vs others: More structured than pure vector RAG for complex domains, and more accessible than standalone graph databases because it's embedded in the MCP workflow without requiring separate infrastructure

via “knowledge-graph construction and relationship inference”

Send voice notes to Telegram → get organized knowledge base, tasks in Todoist, and daily reports. Persistent memory with Ebbinghaus decay, vault health scoring, knowledge graph. Runs on Claude Code + OpenClaw. 5/mo.

Unique: Uses Claude for semantic relationship inference rather than keyword matching or NLP libraries, enabling understanding of implicit connections (e.g., 'this contradicts what I said about X'). Integrates graph structure into vault health scoring.

vs others: More semantically accurate than Obsidian's backlink system because it infers relationships from content meaning, not just explicit links; more scalable than manual tagging because inference is automated.

via “persistent knowledge graph memory for ai agents with semantic search”

Neo4j Labs Model Context Protocol servers

Unique: Implements memory as a graph structure rather than flat vector embeddings, allowing agents to reason over relationship patterns and entity connections. Uses Neo4j's native graph query capabilities to retrieve contextual subgraphs relevant to current agent state, combining pattern matching with semantic search for multi-dimensional retrieval.

vs others: Outperforms vector-only memory systems for relationship-heavy reasoning because it preserves and queries structural relationships between facts, enabling agents to discover indirect connections and reason over graph patterns that vector similarity alone cannot capture.

via “knowledge-graph visualization and exploration”

Hi HN,AI agents that can run tools on your machine are powerful for knowledge work, but they’re only as useful as the context they have. Rowboat is an open-source, local-first app that turns your work into a living knowledge graph (stored as plain Markdown with backlinks) and uses it to accomplish t

Unique: Visualizes a work-specific knowledge graph with domain-aware filtering and multiple visualization modes, rather than generic graph visualization tools

vs others: More useful than generic graph visualization because it understands work entity types and relationships, and more interactive than static reports because it allows real-time filtering and exploration

via “graph storage and persistence with sqlite backend”

Local knowledge graph for Claude Code. Builds a persistent map of your codebase so Claude reads only what matters — 6.8× fewer tokens on reviews and up to 49× on daily coding tasks.

Unique: Uses SQLite as a lightweight, zero-configuration graph storage backend with indexes optimized for common query patterns (entity lookup, relationship traversal, impact analysis). The storage layer supports concurrent read access and requires no external services.

vs others: Simpler than cloud-based graph databases (Neo4j, ArangoDB) because it requires no external services or configuration, making it suitable for local development and CI/CD pipelines.

via “hierarchical knowledge graph construction and reasoning”

Cognithor · Agent OS: Local-first autonomous agent operating system. 19 LLM providers, 18 channels, 145 MCP tools, 6-tier memory, Agent Packs marketplace, zero telemetry. Python 3.12+, Apache 2.0.

Unique: Integrated knowledge graph construction with hierarchical reasoning, rather than treating graphs as optional; combines graph traversal with semantic search for hybrid reasoning

vs others: Enables relationship-based reasoning beyond semantic similarity; multi-hop reasoning capabilities support complex questions that require understanding entity connections

via “multi-graph-type data model abstraction”

Manage, analyze, and visualize knowledge graphs with support for multiple graph types including topologies, timelines, and ontologies. Seamlessly integrate with MCP-compatible AI assistants to query and manipulate knowledge graph data. Benefit from comprehensive resource management and version statu

Unique: Provides unified abstraction over topology, timeline, and ontology graph types with type-specific validation and traversal semantics, rather than treating all graphs as generic property graphs. Enforces temporal ordering in timelines and class hierarchies in ontologies at the query layer.

vs others: Handles mixed graph types in a single system vs. maintaining separate backends for each type, reducing operational complexity while preserving type-specific semantics