NornicDB-Hermes-Memory-GPU

NornicDB is a Neo4j-compatible graph, vector, and temporal database with GPU-accelerated (CUDA or Vulkan) HNSW vector search, native graph traversal, managed…

  • AI
  • Databases
  • Network Services
  • Tools & Utilities
NornicDB is a Neo4j-compatible graph, vector, and temporal database with GPU-accelerated (CUDA or Vulkan) HNSW vector search, native graph traversal, managed embeddings, and policy-based memory decay. This build provides long-term Graph-RAG memory for the Hermes agent, persisting and auto-linking data as a self-organizing knowledge graph with MVCC temporal reads through Bolt/Cypher and Qdrant-compatible gRPC interfaces.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

76/100 Good

Maintained
100last commit 13 days ago
Popular
59924 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
85512 MB minimum RAM

Availability: platform listings confirmed today, links checked 31 days ago

GitHub stars
924
Open issues
21
Last commit
2026-11-08
Latest release
v1.4.3
License
MIT
Activity
declining

Checked 13 days ago - source: GitHub (orneryd/NornicDB)

Resources & Compatibility

Minimum requirements: 512 MB RAM. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Download, install, and start the service Download the NornicDB binary, run sudo nornicdb install, then start it now and enable it to start at boot using sudo systemctl start nornicdb and sudo systemctl enable nornicdb. If you skip this, the app will not automatically come back after a reboot and you will not have an easy log to check when something goes wrong. source
  • Set the ports and config file first When starting the server, pass the config file (settings file) and the ports you want to use, for example nornicdb serve --config ~/.nornicdb/config.yaml --bolt-port 7687 --http-port 7474. If the database port or web/API port is wrong or blocked, other apps and web clients will not be able to reach it. source
  • Set OAuth provider credentials If you use the OAuth (standard sign-on) provider, start it with real client ID and client secret values and a port you can reach, such as -client-id my-client -client-secret my-secret -port 9999. Without valid credentials and an open port, users will not be able to sign in through that provider. source
  • Ports and data volume Expose ports 7474 (browser UI) and 7687 (Bolt); map a persistent volume at /data for the database. source

Fetched 39 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What ports and config should I pass when starting NornicDB so clients can reach it?

Start the server with the config file and the ports you want, for example bolt port 7687 and HTTP port 7474. If the database port or web/API port is wrong or blocked, other apps and web clients cannot reach it.

What credentials are required for the OAuth sign-on provider?

Start the OAuth provider with a real client ID and client secret and a port that users can reach. Without valid credentials and an open port, users cannot sign in through that provider.

Why might NornicDB not come back after a Linux reboot?

After downloading the binary, run the install command and then start and enable the systemd service. If you skip this, NornicDB will not automatically start after reboot and you will not have an easy log to check.

Which Docker image should I use on a GPU host?

Use the CUDA image for NVIDIA CUDA hosts and the Vulkan image for Vulkan hosts. Docker on macOS does not expose Metal acceleration, so the Apple Silicon image runs but GPU acceleration on macOS requires a native install or local build.

What interfaces can client applications use to connect to NornicDB?

It speaks Neo4j Bolt and Cypher and also exposes REST, GraphQL, and gRPC interfaces. It can preserve Qdrant-style client workflows through a Qdrant-compatible gRPC surface.

Answers sourced from github.com, github.com, github.com, github.com

Community

Collected 48 days ago - public community threads