Amazon Neptune Analytics vs ArangoDB
Amazon Neptune Analytics vs ArangoDB: side-by-side comparison of two knowledge-graph platforms systems — architecture, taxonomy, license, pricing, MCP/A2A support, and direct edges.
Cost & capability
| Amazon Neptune Analytics | ArangoDB | |
|---|---|---|
| Cost tier | mid | mid |
Where they differ (9)
Rows where both sides have data and the values disagree — the shortlist of dimensions that actually distinguish these two systems.
| Amazon Neptune Analytics | ArangoDB | |
|---|---|---|
| Type | Vector + graph in one managed service | Multi-model: graph + doc + KV + vector |
| Created | 2023-11 | 2014 |
| Pricing | Pay-per-use — billed per m-NCU-hour (1 m-NCU = 1 GB memory plus compute for 1 hour), $0.03 per m-NCU-hour in us-east-1 (16 m-NCU graph = $0.48/hour); paused graphs billed at 10% of compute | Pay-per-use |
| Funding | searched not found | Series B · 2021-10 |
| Backend storage | custom (AWS Neptune managed) | custom (RocksDB-backed multi-model) |
| Deployment | Managed-only | Both |
| API surface | REST, openCypher, Gremlin, SPARQL, SDK: AWS SDKs | REST (HTTP), SDK: many |
| MCP | yes — official AWS Labs Amazon Neptune MCP server (openCypher queries, schema and status for Neptune Analytics graphs) | yes — community ravenwits/mcp-server-arangodb |
| OpenTelemetry | first-class — CloudWatch / OTel | first-class |
At a glance
| Amazon Neptune Analytics | ArangoDB | |
|---|---|---|
| Section | Knowledge-graph platforms | Knowledge-graph platforms |
| Tier | T1 | T1 |
| Type | Vector + graph in one managed service | Multi-model: graph + doc + KV + vector |
| Created | 2023-11 | 2014 |
| License | — | BSL-1.1 (source-available; each release converts to Apache-2.0 four years after release) |
| GitHub | — | arangodb/arangodb — ~14.3k stars, active (commit date not captured) |
| Pricing | Pay-per-use — billed per m-NCU-hour (1 m-NCU = 1 GB memory plus compute for 1 hour), $0.03 per m-NCU-hour in us-east-1 (16 m-NCU graph = $0.48/hour); paused graphs billed at 10% of compute | Pay-per-use |
| Funding | searched not found | Series B · 2021-10 |
| Backend storage | custom (AWS Neptune managed) | custom (RocksDB-backed multi-model) |
| Deployment | Managed-only | Both |
| API surface | REST, openCypher, Gremlin, SPARQL, SDK: AWS SDKs | REST (HTTP), SDK: many |
| Embedding | BYO | BYO |
| Multi-tenancy | hard-isolation | hard-isolation |
| MCP | yes — official AWS Labs Amazon Neptune MCP server (openCypher queries, schema and status for Neptune Analytics graphs) | yes — community ravenwits/mcp-server-arangodb |
| A2A | no Google A2A (Agent2Agent) integration documented as of 2026-05. | no Google A2A (Agent2Agent) integration documented as of 2026-05. |
| OpenTelemetry | first-class — CloudWatch / OTel | first-class |
| Optimised for | relationship modeling + reasoning + governance over pure vector | relationship modeling + reasoning + governance over pure vector |
| Anti-fit | not for purely-vector or simple-RAG use cases (graph adds setup cost) | not for purely-vector or simple-RAG use cases (graph adds setup cost) |
Pros & cons
Amazon Neptune Analytics
Pros: Managed graph database with vector + graph hybrid for AWS-native architectures; first-class integration with Bedrock and SageMaker.
Cons: AWS-only; vector + graph hybrid is newer than dedicated competitors; pricing complexity around graph queries.
ArangoDB
Pros: Multi-model (graph + document + KV) in one engine — useful when memory crosses paradigms without managing multiple databases.
Cons: Multi-model adds complexity vs single-purpose engines; smaller community than Neo4j or MongoDB.