All 40 Dependencies

Every package NornicDB depends on, ranked by repo health score.

NornicDB is a purpose-built graph database written in Go that unifies graph traversal, vector retrieval, and historical truth in a single engine. It speaks Neo4j's Bolt protocol and Cypher query language natively, meaning existing Neo4j drivers and applications connect without modification, while gaining vector search, temporal MVCC reads, and AI-native knowledge management features that Neo4j does not provide.

The project emerged from a common AI architecture problem: knowledge-intensive applications — agents, Graph-RAG pipelines, canonical truth stores — typically bolt together a Neo4j instance, a Qdrant or Pinecone vector store, and an embeddings service. NornicDB replaces that stack with a single deployment. Hybrid retrieval (vector search followed immediately by graph hop expansion) runs inside one execution path, eliminating cross-service round trips and the consistency hazards that come with keeping two stores in sync.

NornicDB ships hardware-accelerated inference paths for Apple Silicon (Metal), NVIDIA GPUs (CUDA), and Vulkan-capable hosts, alongside a CPU-only build. It includes a built-in MCP server so LLM agents can store, recall, and discover knowledge directly via standard Model Context Protocol tooling — no extra infrastructure layer required. Knowledge decay policies let the system automatically deprioritize stale nodes over time using configurable decay profiles, which makes it particularly well-suited for long-lived agent memory systems.

Join founders buildingwith open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on Substack
Join 750+ subscribers

Search