Neptune vs RelationalAI

Neptune is a multiple database; RelationalAI is a other database. Neptune (2017-11, Proprietary, C++) ranks #4 this month; RelationalAI (2022, Proprietary, Julia) ranks #111.

Attribute Neptune #4 ▼3 Leader RelationalAI #111 ▲18 Growing
At a glance
Rank #4#111
Score 65.533.6
GitHub stars
Popularity 81.220.0
Activity 95.5
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 cloud-native relational knowledge graph system (RKGS) that models all data as relations in Graph Normal Form and is queried with Rel, a declarative, Datalog-based modeling language. Positioned as a knowledge graph coprocessor for Snowflake, it runs in-account as a Native App on Snowpark Container Services, adding rule-based reasoning, graph analytics, and predictive and prescriptive analytics over data where it already lives. The engine is built in Julia.
Vendor Amazon Web ServicesRelationalAI
Model MultipleOther
Kind databasedatabase
Category EnterpriseGrowing
First released 2017-112022
Status activeactive
License ProprietaryProprietary
Written in C++Julia
Query languages Gremlin, SPARQL, openCypherRel, SQL
gdotv support yesno

Feature scores — not surveyed for RelationalAI

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