Neo4j vs TuringDB

Both are property graph databases queried with Cypher. Neo4j (2007, GPL-3.0, Java) ranks #1 this month; TuringDB (2025, BUSL-1.1, C++) ranks #53.

Attribute Neo4j #1 = Leader TuringDB #53 = Growing
At a glance
Rank #1#53
Score 83.349.5
GitHub stars 17.2k180
Popularity 97.341.9
Activity 86.782.2
Community 90.252.2
Research 98.649.6
Fundamentals
Description A property graph database that stores data as fixed-size records in linked lists for index-free adjacency traversal. Offers community and commercial editions with an extensive graph algorithms library.An in-memory, column-oriented property graph database engine focused on analytical and read-intensive workloads over large graphs.
Vendor Neo4j IncTuring Biosystems
Model Property GraphProperty Graph
Kind databasedatabase
Category EstablishedEmerging
First released 20072025
Status activeactive
License GPL-3.0BUSL-1.1
Written in JavaC++
Query languages Cypher, GQLopenCypher
gdotv support yesno

Feature scores — not surveyed for TuringDB

Feature Neo4jTuringDB
Community & Business
Active development
Commercial support
Live community
Open Source
Pricing 0.5
Trendiness
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
Transactions
Granular locking
Multiple isolation levels
Read committed transaction
Transaction support
Schema & Security
Constraints
Schema support
Secondary indexes
Server side procedures
Triggers
Authentication
Authorization
Data encryption ·