ArangoDB vs NornicDB

ArangoDB is a multiple database; NornicDB is a property graph database. ArangoDB (2012-03, BUSL-1.1, C++) ranks #2 this month; NornicDB (2025-12, MIT, Go) ranks #60.

Attribute ArangoDB #2 = Leader NornicDB #60 ▼10 Growing
At a glance
Rank #2#60
Score 68.846.5
GitHub stars 14.3k854
Popularity 85.852.6
Activity 80.065.0
Community 51.630.6
Research 80.549.6
Fundamentals
Description A multi-model database supporting graphs, key-value pairs, and documents in a unified JSON-based data model. Offers both an in-memory storage engine and a RocksDB-based engine for larger datasets.A hybrid graph and vector database written in Go with Neo4j compatibility via the Bolt protocol. Supports Cypher queries, native vector search with GPU acceleration, and a tiered memory system with episodic, semantic, and procedural decay. Includes a versioned graph ledger with temporal validity and as-of reads.
Vendor ArangoDB Incorneryd
Model MultipleProperty Graph
Kind databasedatabase
Category EnterpriseEmerging
First released 2012-032025-12
Status activeactive
License BUSL-1.1MIT
Written in C++Go
Query languages AQLopenCypher, GraphQL
gdotv support nono

Feature scores — not surveyed for NornicDB

Feature ArangoDBNornicDB
Community & Business
Active development
Commercial support
Live community 0.5
Open Source
Pricing ·
Trendiness 0.25
Deployment
Containerization
Work as dedicated instance
Work as embedded ·
Testing in-memory version
Platform
Operating on Linux
Operating on Windows
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
Reactive programming ·
Documentation up-to-date
Binary protocol
CLI
GUI
Data Model
Multi-database
Graph-native data ·
REST API
Query Language 0.5
Transactions
Granular locking ·
Multiple isolation levels ·
Read committed transaction ·
Transaction support
Schema & Security
Constraints
Schema support 0.5
Secondary indexes
Server side procedures 0.5
Triggers ·
Authentication
Authorization 0.5
Data encryption