Neptune vs Traverse

Neptune is a multiple database; Traverse is a property graph database. Neptune (2017-11, Proprietary, C++) ranks #14 this month; Traverse (2026-03, Proprietary, Rust) is not ranked.

Attribute Neptune #14 ▲2 Strong Traverse — ▼7 Insufficient data
At a glance
Rank #14— Not ranked
Score 61.140.9
GitHub stars ——
Popularity 61.0—
Activity 60.951.4
Community 61.859.1
Research 60.4—
Fundamentals
Description A fully managed graph database service from AWS supporting both property graph and RDF models. Available as Neptune Database (for transactional workloads) and Neptune Analytics (for analytical queries).An in-memory property graph database written in Rust, speaking Cypher and GQL over the Bolt protocol for Neo4j driver compatibility. Includes a built-in graph data science library of 36+ algorithms callable from Cypher, and runs as a server, an embedded in-process library, a Cloud Hypervisor/Firecracker unikernel, or entirely in the browser via WebAssembly.
Vendor Amazon Web ServicesTruespar
Model MultipleProperty Graph
Kind databasedatabase
Category EnterpriseEmerging
First released 2017-112026-03
Status activeactive
License ProprietaryProprietary
Written in C++Rust
Query languages Gremlin, SPARQL, openCypheropenCypher, GQL
gdotv support yesno

Feature scores — not surveyed for Traverse

Feature NeptuneTraverse
Community & Business
Active development ✓—
Commercial support ✓—
Live community ✓—
Open Source ·—
Pricing ✓—
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 0.5—
Replication support ✓—
Developer Experience
Data types defined 0.5—
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 0.5—
Secondary indexes ✓—
Server side procedures ·—
Triggers ·—
Authentication ✓—
Authorization ✓—
Data encryption ✓—