NodeDB vs QLever

NodeDB is a multiple database; QLever is a rdf database. NodeDB (2026-04, BUSL-1.1, Rust) ranks #102 this month; QLever (2017-11, Apache-2.0, C++) ranks #10.

Attribute NodeDB #102 ▼1 Growing QLever #10 ▼2 Strong
At a glance
Rank #102#10
Score 36.363.1
GitHub stars 197897
Popularity 41.955.3
Activity 53.778.4
Community 56.262.4
Research 49.679.1
Fundamentals
Description A multi-model database written in Rust that runs document, key-value, columnar, timeseries, spatial, vector, and array engines in a single binary over shared storage, with graph and full-text search as cross-engine overlays on any collection. Its graph overlay uses a CSR adjacency index with 13 built-in algorithms and a Cypher-subset MATCH syntax, and fuses graph traversal with vector search in a single query for GraphRAG. Speaks SQL over a native MessagePack protocol and the PostgreSQL wire protocol, alongside HTTP/REST, WebSocket, RESP, and ILP.A SPARQL engine capable of querying very large knowledge graphs (including complete Wikidata) on a single machine. Implements full SPARQL 1.1 with autocompletion and text search.
Vendor NodeDB-LabUniversity of Freiburg
Model MultipleRDF
Kind databasedatabase
Category EmergingEmerging
First released 2026-042017-11
Status activeactive
License BUSL-1.1Apache-2.0
Written in RustC++
Query languages SQL, openCypherSPARQL
gdotv support noyes

Feature scores — not surveyed for QLever

Feature NodeDBQLever
Community & Business
Active development
Commercial support
Live community
Open Source 0.5
Pricing ·
Trendiness ·
Deployment
Containerization
Work as dedicated instance
Work as embedded ·
Testing in-memory version ·
Platform
Operating on Linux
Operating on Windows 0.5
SaaS offering ·
Operations
Automatic updates ·
Client side caching ·
Data versioning support
Live backups
Distribution
Cluster Re-balancing
Data Distribution
High-Availability
Query Distribution
Replication support
Developer Experience
Data types defined
Logging/Auditing
Object-Graph Mapper 0.5
Reactive programming
Documentation up-to-date
Binary protocol
CLI
GUI ·
Data Model
Multi-database
Graph-native data
REST API
Query Language
Transactions
Granular locking ·
Multiple isolation levels 0.5
Read committed transaction
Transaction support
Schema & Security
Constraints
Schema support
Secondary indexes
Server side procedures
Triggers
Authentication
Authorization
Data encryption