Back to directory

RushDB

A graph and vector database built on Neo4j that accepts any JSON and returns typed, searchable, relationship-aware records without a schema or migrations, meant as a memory layer for AI agents.

RushDB

RushDB lets an application push JSON of any shape and get back a live, queryable schema, inferred graph relationships, and semantic search, without designing a schema or writing migrations first. It is meant to replace the usual combination of a key-value cache, a vector store, and a graph database with one system and one API.

Nested objects and arrays in imported JSON become linked records automatically, each nested key becomes a label, and CSV can be imported with automatic type suggestion; embeddings are generated and managed server-side rather than through a separate pipeline. It is available as a managed cloud service or self-hosted with Docker on top of a Neo4j instance, with JavaScript and Python SDKs.

It is written in TypeScript.

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.