Neptune vs StromaDB

Neptune is a multiple database; StromaDB is a property graph database. Neptune (2017-11, Proprietary, C++) ranks #4 this month; StromaDB (2026-07, Elastic-2.0, Rust) ranks #152.

Attribute Neptune #4 ▼3 Leader StromaDB #152 ▲9 Emerging
At a glance
Rank #4#152
Score 65.59.2
GitHub stars 2
Popularity 81.212.5
Activity 95.538.8
Community 53.730.6
Research 58.449.6
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).A source-available property graph engine written in Rust that combines typed edges, vector search, and bitemporal facts for retrieval-augmented generation workloads. Queried through a composable operator API over CLI, HTTP, and MCP rather than a graph query language.
Vendor Amazon Web ServicesKatsuhide Tsuruta
Model MultipleProperty Graph
Kind databasedatabase
Category EnterpriseEmerging
First released 2017-112026-07
Status activeactive
License ProprietaryElastic-2.0
Written in C++Rust
Query languages Gremlin, SPARQL, openCypherCustom API
gdotv support yesno

Feature scores — not surveyed for StromaDB

Feature NeptuneStromaDB
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