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 #39. They differ on 13 of 46 surveyed features.
| Attribute | Neo4j | TuringDB |
|---|---|---|
| At a glance | ||
| Rank | #1 | #39 |
| Score | 88.8 | 49.6 |
| GitHub stars | 17.4k | 188 |
| Popularity | 98.6 | 41.5 |
| Activity | 86.5 | 76.1 |
| Community | 73.8 | 50.5 |
| Research | 98.7 | 50.0 |
| 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 Inc | Turing Biosystems |
| Model | Property Graph | Property Graph |
| Kind | database | database |
| Category | Established | Emerging |
| First released | 2007 | 2025 |
| Status | active | active |
| License | GPL-3.0 | BUSL-1.1 |
| Written in | Java | C++ |
| Query languages | Cypher, GQL | openCypher |
| gdotv support | yes | no |
Feature scores 13 of 46 rows differ
| Feature | Neo4j | TuringDB |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | ✓ |
| Commercial support | ✓ | ✓ |
| Live community | ✓ | ✓ |
| Open Source | ✓ | · |
| Pricing | 0.5 | 0.5 |
| 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 | ✓ | ✓ |
| 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 | · | · |
Links
- Neo4j · website · github · full profile
- TuringDB · website · github · full profile