
Overview

Product video
Powered by the ArangoDB graph database, ArangoGraph is a cloud-based graph data and analytics platform that uncovers insights in data that are difficult or impossible to obtain with traditional SQL, document, or even other graph databases - making it easier to drive value from connected data, faster. It offers a comprehensive set of data management and analytical tools - all united by a powerful query language that natively integrates graph, JSON data, search, and machine learning (ML). Supporting many use cases such as Fraud Detection, Cybersecurity, Customer360, and Supply Chain.
Fully-managed graph database-as-a-service, enabling advanced analytics and machine learning.
Advanced security features such as private endpoints, SSO, and audit logging.
Highly available with data replication, cloud backups (in multiple regions).
Only available for purchase via Private Offer Pricing customized by individual use case ** Public offers as listed will not be fulfilled **
For private offers or other needs, please contact cloud-sales@arangodb.com
Highlights
- Fully-managed graph database-as-a-service, enabling advanced analytics and machine learning
- Advanced security features such as private endpoints, SSO, and audit logging
- Highly available with data replication, cloud backups (in multiple regions)
Details
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/12 months |
|---|---|---|
ArangoGraph Committed | Committed Subscription for an A32 OneShard Deployment in us-east-1 | $60,000.00 |
Vendor refund policy
All fees are non-cancellable and non-refundable except as required by law.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Vendor resources
Support
Vendor support
Standard Support (9-5, business hours) is included with your subscription.
Support is accessible via the "Request Help" section of the ArangoGraph UI.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

Standard contract
Customer reviews
Efficient query workflows have accelerated debugging and data validation during development
What is our primary use case?
My main use case for ArangoGraph is to run queries to find data while we're developing.
A specific example of how I use ArangoGraph for those queries during development is debugging and making sure everything is working. In my previous role, I worked on a shipping app that functioned as a track and trace for parcels, and I used clients to check the database against the client and the packages to ensure everything was functioning.
How has it helped my organization?
ArangoGraph has positively impacted my organization because it is a good piece of software that developers can learn quickly.
Specific positive outcomes since using ArangoGraph include its speed. Arango has always been quick, and the query language is quick and easy, allowing us to get things pushed out the door quicker.
I estimate that we save at least a couple of days a month.
What is most valuable?
The best features ArangoGraph offers are its simplicity, being built on JSON, which makes it very quick to see an overhead of certain bits of data, and its query language being similar to MySQL, with a slight learning curve but nothing too massive.
Being able to quickly see an overhead of certain bits of data helps me in my day-to-day work by allowing for debugging and making sure everything works before we ship. We can run queries, and from a high overhead view, we know whether it is working or not by the data that is returned.
Along the line, we will be sharding our database.
What needs improvement?
I think the open-source version is good, but when moving on to a paid version, there are a few things that could be taken from the paid version into the open-source version.
For how long have I used the solution?
I have used Arango for seven years, and I have only been using ArangoGraph for about a year.
What do I think about the stability of the solution?
I think ArangoGraph is stable; we have never had any problems.
What do I think about the scalability of the solution?
The scalability of ArangoGraph is good, and it is much easier to scale when the documents are just JSON.
Which solution did I use previously and why did I switch?
Before using ArangoGraph, we were on Rails with a Postgres database, and we decided to switch because we needed something a little bit faster.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing was okay; we just had to do a bit of pre-planning.
Which other solutions did I evaluate?
Before choosing ArangoGraph, I evaluated staying with Postgres as one of the options.
What other advice do I have?
On a scale of 1 to 10, I rate ArangoGraph an eight.
I give it an eight because I am really happy with how it works and how it performs, but I am missing the two points because the enterprise version is a bit too expensive for new startups.
Regarding ArangoGraph's AI capabilities, I trust its governance and security, having no reason to question it or be worried about it.
In terms of ArangoGraph's AI capabilities, the accuracy and reliability of output seem to be fine; it seems to be quick and good.
At the moment, we are using Vultr as our cloud provider.
My advice to others reading reviews on PeerSpot who are looking into using ArangoGraph is to learn the query language. It is really not that hard, and by learning the query language, you will get the most out of ArangoGraph.
Connected data has powered fraud detection and real-time risk profiling across complex relationships
What is our primary use case?
The main use case of ArangoGraph is data analytics, and I have conducted multiple kinds of POCs where I experimented on fraud detection where I identified suspicious connections or spurious activity between account transactions and users. I also dabbled in social media analysis, for example, I wanted to conduct experiments on finding mutual friends in a particular social media platform.
In case of fraud detection, I have used ArangoGraph for finding unwanted or illegal transactional details in banking activity or card activity. Whenever a particular user makes an online transaction using a credit or debit card, that is where ArangoGraph comes into the picture. Since ArangoGraph is a graph database, it exposes hidden relationships between the customer, transactions, IT devices, and merchants.
Apart from fraud detection, I have also used ArangoGraph in data engineering. From my data engineering background, ArangoGraph can be used for master data management, data lineage tracking, and finding relationships between enterprise data sets.
How has it helped my organization?
ArangoGraph has been very helpful in my organization as we extensively use it for multiple use cases such as detecting financial fraud, data engineering use cases in master data management or data lineage, and social media analysis.
Picking one specific example, using ArangoGraph has benefited us to have a single customer view in case of financial fraud detection. It helps us for profiling risk and fraud detection. When I go deeper into fraud detection, it helps us identify shared devices and shared IP addresses, and it helps us in anti-money laundering as well.
What is most valuable?
The best features ArangoGraph offers include support for graph traversal and relationships between queries very efficiently. On top of it, it also has its own query engine known as AQL, so using this, I can query graphs and documents. It also scales or expands horizontally through clusters, and one important feature which I appreciate is that it is very suitable for real-time analytics on connected data.
AQL is basically used for querying graphs and documents, so it is similar to SQL. AQL is something I can use to interact with ArangoGraph, so it can query documents, edges, and graphs using a single language. Not only relational but also non-relational databases such as MongoDB and other graph-based databases can use AQL.
AQL can be used for traversal both inbound and outbound, for multi-hop relationship analysis, finding the shortest path between graphs, and is widely used for anti-money laundering detection patterns and financial frauds.
The governance and security is quite good. Compared to what I have seen for other graph-based databases, ArangoGraph has a comparatively better advantage in terms of data security, and that is why it is the preferred choice in my organization.
What needs improvement?
ArangoGraph can be improved by adding more AI capabilities as everything is moving into the AI space nowadays. If AI capabilities such as agentic AI or Generative AI can be added, it can definitely have more advantage compared to its traditional peers.
In terms of data quality, some implementations use ArangoGraph, so data quality checks would be beneficial. If ArangoGraph could have out-of-the-box features such as identification of duplicates, missing edge validation, or entity resolution already added in-built, it will have more added advantage.
The features I mentioned for improvement are already in the pipeline and should be expected in the next quarter, but apart from that, the working experience I have had with ArangoGraph has been quite fruitful and I expect the same to continue with all the incoming new features that are expected to arrive by next year.
For how long have I used the solution?
I have been using ArangoGraph for close to five years now.
What do I think about the stability of the solution?
ArangoGraph has experienced stability issues.
What do I think about the scalability of the solution?
Scalability-wise, ArangoGraph is quite scalable in terms of horizontal scaling. Whenever there are peak times, ArangoGraph is definitely scalable, and scalability is one of its key strengths.
Adding more servers and nodes to a cluster provides vertical scaling based on the workload, and it provides high availability and distributed data storage, so all these features are an advantage compared to other options.
How are customer service and support?
Customer support has been quite good. Whenever there are challenges, I reach out to ArangoGraph customer service, open up a ticket with them, or simply send an email, and I get support from them immediately.
I would rate customer support nine out of ten.
Which solution did I use previously and why did I switch?
I used traditional databases, NoSQL and SQL databases such as MongoDB, Oracle, MySQL, and PostgreSQL. Using those for my use cases for fraud detection, social media analysis, and master data management compared to using ArangoGraph gave us a more competitive advantage. The processing and solutions provided by ArangoGraph supersede whatever the solution provided by the previous platforms.
What was our ROI?
I cannot give exact numbers in terms of money saved or time saved, but ArangoGraph has been quite beneficial compared to traditional graph databases.
What's my experience with pricing, setup cost, and licensing?
So far, everything is going well, and there are no major concerns in terms of ArangoGraph licensing and pricing cost. When I was actually trying to learn ArangoGraph, I used the community edition, which is the free version. Once I gained substantial experience with that, I went with the enterprise edition within the company when I had use cases within the company itself.
Which other solutions did I evaluate?
When I started working with ArangoGraph with the community edition, the features it had when I was exploring were liked by everyone, and I went with that, so I did not evaluate other options when choosing ArangoGraph.
What other advice do I have?
On a scale of one to ten, I would rate ArangoGraph nine, simply because the features that I have explored are not only at par but exceed compared to its competitors. The only basic area I would say is in terms of GenAI and knowledge integration, as most vendors and competitors are integrating Generative AI and machine learning capabilities within themselves.
In terms of accuracy and reliability, ArangoGraph is reliable, but it certainly requires human review. Obviously, it is important that core AI principles are incorporated such as fairness, transparency, and responsible AI. So far, whatever I have observed or checked in terms of ArangoGraph, it is quite useful.
In my organization, ArangoGraph is deployed on a hybrid cloud. Some deployment is on a private cloud where security and customer data are of utmost importance. However, if it is not dealing with customer-specific data, it is deployed on the public cloud, and I use AWS for the public cloud deployment.
I would recommend others if they have use cases in social media analysis, data analytics, data engineering, master data management, data lineage, or financial fraud such as anti-money laundering or illegal banking transactions. They can definitely give ArangoGraph a try and explore its features, which are definitely above its competitors.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Graph insights have cut data cleanup costs and time but AI security still needs improvement
What is our primary use case?
My main use case for ArangoGraph is that our data is so messy, so we need a graph database to predict and retrieve the data. There is also a product called graph machine learning models that we utilize.
A specific example of how I use ArangoGraph with our messy data is that in our company, some employees are taking sick leave or casual leaves on Saturday or Monday without any apparent purpose. With ArangoGraph, I used it to visualize who is exactly taking sick leave and casual leave in a graph format and issue a small warning about that.
Regarding my main use case with ArangoGraph, I can add that we also used it regarding cyber attacks, and there are many more ways I utilize it.
How has it helped my organization?
ArangoGraph has positively impacted my organization by cutting down our costs and mostly increasing efficiency, which means we do not have to do the work manually.
I can share specific outcomes where mostly it is about a 20 to 30% reduction in costs, and the time saved is around 80%.
What is most valuable?
The best features ArangoGraph offers include ArangoSearch engine which has inbuilt embeddings to store and can process the graph after we dump a lot of data into it. Additionally, there is a product called AI Contextual Data Layer which can retrieve information using natural language.
Out of those, the feature I find myself using the most is the Equalizer, which allows me to simply ask in natural language, and it internally converts that into AQL and executes it in the database, giving me the answer in natural language. This makes it very useful to me.
Regarding the features, I would add that there are features called Importer and Retriever which are available in the public document. The Importer allows us to import data that automatically converts it into a knowledge graph, while the Retriever retrieves relevant information based on whichever query is asked.
What needs improvement?
I think ArangoGraph can be improved as there are many bugs, but the development team is trying to fix them.
I would add that we used to bring our own key as ArangoGraph did not provide any specific fine-tuned LLM for our use case. We need to use our own API keys, such as OpenAI or Claude, but we need our data to remain safe. I think it is better to move from GPUs and develop their own LLM.
Regarding ArangoGraph's AI capabilities, at the time I used it, I did not think they provided much security.
Regarding ArangoGraph's AI capabilities, its accuracy and reliability of output sometimes depend on user queries. The main thing it is missing is AI guardrails and security. When I used it, we could easily inject the prompt and it would break, but I do not know about it now as I have not used it in a while.
For how long have I used the solution?
I have been using ArangoGraph for about one year and two months.
What do I think about the stability of the solution?
I do not think ArangoGraph is stable as they release updates every month with many bugs. Although it might become stable at some point, right now I do not think so.
What do I think about the scalability of the solution?
ArangoGraph's scalability is pretty good and it depends on the environment, mainly involving DevOps and Kubernetes.
How are customer service and support?
I would rate customer support as mostly 9 out of 10, but when it comes to AI capabilities, it was like 4 out of 10, though overall it was good.
I would rate the customer support a seven.
Which solution did I use previously and why did I switch?
I previously used Neo4j, which offers the same capabilities but has a better solution for our use case.
What was our ROI?
I have seen a return on investment as previously we cleaned up the data with six to seven members without ArangoGraph. Now it is a one-person job, while the money kind of increased, but is expected to decrease over time, with the time saved being huge.
What's my experience with pricing, setup cost, and licensing?
The experience with pricing, setup cost, and licensing was reasonable, as the setup cost was not that expensive.
Which other solutions did I evaluate?
Before choosing ArangoGraph, we did not evaluate any other options, but after choosing it, we made a shift to Neo4j.
What other advice do I have?
On a scale of 1 to 10, I would rate ArangoGraph a seven.
I chose seven because when I tried to use another product related to it, the UI is not that great compared to Neo4j.
ArangoGraph is deployed in my organization in an air-gapped environment.
The advice I would give to others looking into using ArangoGraph is that they first need to understand the graph fundamentals and then learn basic SQL, specifically AQL, and start with a smaller dataset, trying out the Enterprise Edition in Docker before contacting the Arango team. If they need AI capabilities, they must shift to the AI Contextual platform and have a basic understanding of Python to integrate with the code, along with having APIs for using ArangoGraph for AI purposes.
Graph views have transformed how users understand buyer supplier product relationships
What is our primary use case?
My main use case for ArangoGraph is to display graphs on the UI so users get a view with a graph-based interface showing relationships such as who is a customer, who is a buyer, and who is a supplier. I maintain these relationships using ArangoGraph.
I can provide a specific example of how I use ArangoGraph to maintain buyer-supplier relationships. In Arango, which is a multi-model database, I use ArangoGraph with edges and vertices. My vertices are customers and suppliers, and other vertices are items that the supplier provides to the buyer. The relationships between products, customer products, and suppliers are maintained through edges, while vertices contain customer, product, and supplier information. This is how I use ArangoGraph to show the relationship between the customer, seller, and buyer of products.
This is my main use case because without a graph, users need to check tabular information and read everything to understand relationships. With a graph using edges and vertices, users can easily identify connections. For example, if a buyer purchased three products—product A, product B, and product C—from a specific supplier, users can easily see the delivery status and what products were bought through these graphs.
How has it helped my organization?
ArangoGraph has had a positive impact on my project, mainly in managing visualization of complex relationships between buyers, suppliers, and products. Previously, understanding how different entities were connected could be challenging. With ArangoGraph, I can represent relationships using vertices and edges and retrieve connected information through graph queries. This makes it easier for the backend to provide relationship data to the front end when users can explore connections visually. It also provides flexibility when adding new entities or relationships as business requirements evolve. Overall, the biggest benefits are better relationship management, easier data exploration, and more flexibility in the application.
I have seen positive improvements, especially in how I can retrieve and explore relationships. For example, when a user wants to see a supplier connected to a particular product or buyer, I can use graph traversal queries to retrieve those relationships directly. This has made relationship-based data retrieval more straightforward for backend development and has helped provide a better graph experience on the UI. In terms of exact metrics, I have not formally benchmarked the time-saving or performance improvement, but from my development perspective, the main benefits have been simpler relationship queries and easier maintenance with greater flexibility as the data model evolves.
What is most valuable?
One of the best features of Arango is that it is a multi-model database, and specifically, the best features of ArangoGraph are scalability and user interface, which are most important in the e-commerce domain. Previously, I was in the healthcare e-commerce domain, where scalability matters more, and that is the feature it provides, which is very useful for my work. As I mentioned, the user interface definitely adds more value whenever users see details using edges and vertices.
The scalability of ArangoGraph is useful for my project because I manage relationships between customers, buyers, suppliers, and products, and this data keeps growing over time. As more suppliers, buyers, and products are added, the number of relationships also increases. ArangoGraph provides options to scale as data grows, which helps me plan for increasing data volumes and more complex graph queries. From the backend perspective, this is valuable because I want users to explore these relationships smoothly without major changes to the application architecture. Overall, scalability helps me support growth and manage increasingly complex relationships.
Another useful feature is AQL, which allows me to retrieve data through graph traversal queries. The flexibility of graph traversal capability and ease of managing complex relationships are the features I appreciate most.
What needs improvement?
Overall, ArangoGraph has been useful for my project, but I think there are a few areas where it could be improved. One area is the developer experience, especially when working on complex graph queries. Better debugging tools and more detailed query performance insights would make troubleshooting easier. Another area is graph visualization, where having more advanced built-in visualization and exploration features would be helpful, especially when dealing with a large number of vertices and edges.
When working with complex relationships involving multiple buyers, suppliers, and products, it would be helpful to have more intuitive tools to analyze graph traversal queries and identify performance bottlenecks. Additionally, better integration examples for backend applications would make development and troubleshooting easier.
For how long have I used the solution?
I have been using ArangoGraph for two years.
What do I think about the stability of the solution?
ArangoGraph has been quite stable for my use cases. I have been using it for around two years to manage the relationships between buyers, suppliers, and products. From a backend developer perspective, it has been reliable for storing and retrieving graph data using AQL queries, and I have not encountered any major stability issues in my day-to-day development work.
What do I think about the scalability of the solution?
ArangoGraph offers good scalability for my use cases. In my project, I manage relationships between buyers, suppliers, and products, and as the number of entities increases, the relationships also become more complex. ArangoGraph supports horizontal scaling, which is useful for handling growing data volumes and increasing workloads. From a backend development perspective, its graph traversal capability helps me manage these relationships efficiently, and overall, I am satisfied with its scalability, although I have not personally conducted large-scale performance or load testing.
How are customer service and support?
Customer support for ArangoGraph is good. I would rate the customer support a nine out of ten.
What other advice do I have?
Based on my experience, I would rate ArangoGraph an eight out of ten.
I chose an eight out of ten for ArangoGraph because it has been really useful for my project, especially in managing complex relationships between buyers, suppliers, and products. I appreciate the graph traversal capability, flexible data modeling, and AQL query language. There is still some room for improvement in areas such as query debugging, performance monitoring, and developer documentation, but overall, I am satisfied with the product and its capabilities.
Regarding ArangoGraph's AI capabilities, I think its governance and security are useful, particularly around access control and managing permissions. Since my application deals with business relationships between buyers, suppliers, and customers, data security and controlling access to sensitive information is important. Features such as fine-grained access control, audit logging, and better visibility into how data is accessed by AI applications are important. Overall, my experience with ArangoGraph has been positive, but I would need more hands-on experience with the AI governance features to evaluate them properly.
Regarding ArangoGraph's AI capabilities, while I have not explored them extensively because my primary use case is managing the graph-based relationship between buyers, suppliers, and products, my experience with the accuracy and reliability of the graph query results has been positive. ArangoGraph helps me retrieve connected data using AQL and graph traversal, which is important for managing accurate business relationships.
I would recommend ArangoGraph to organizations that need to manage complex relationships between different entities. My advice would be to first understand your use case and design your graph accordingly.
Graph queries have become faster and now uncover complex data privacy dependencies
What is our primary use case?
ArangoGraph's main use case is to save interconnected data and traverse across connected data similar to how you traverse through a graph. In a traditional database, you need foreign key connections, but ArangoGraph enabled me to traverse through efficiently with minimal complexity.
In one of my projects, I had to connect certain privacy records entities to certain master data, and this master data needed to be connected to another set of master data. I had to find dependencies between master data and determine what master data privacy records were connected to. When this happened with thousands and lakhs of records, ArangoGraph really helped in that case.
How has it helped my organization?
I was able to easily perform queries, and the complexity and time consumption were very small compared to using a traditional database. For some queries that took one minute with traditional databases, I was able to complete them within four seconds in ArangoGraph when testing with certain cases. This was the main impact.
What is most valuable?
The best feature of ArangoGraph was that I could decide the mode of traversal. The querying was smooth, and I could configure the understanding of how to query and the level of depth I needed to traverse through the data.
ArangoGraph provided AQL, which is Arango Query Language, as the go-to way for queries, and that was really easy to understand and digest. Within a very short time, I was able to figure out how to do this querying and understand how the language works. The documentation was easy to understand and apply to my use cases.
What needs improvement?
It could be more performant if possible, and greater speed could be achieved. Other than that, I do not have many suggestions.
For how long have I used the solution?
I used ArangoGraph for three years in my career at the initial stage.
What do I think about the stability of the solution?
It is stable.
What do I think about the scalability of the solution?
Scalability was good.
How are customer service and support?
Customer service was good, and I would rate it at nine.
Which solution did I use previously and why did I switch?
I did not use any other solution previously.
What's my experience with pricing, setup cost, and licensing?
The setup cost was satisfactory.
Which other solutions did I evaluate?
The only other solution I considered was Neo4j.
What other advice do I have?
I would rate ArangoGraph at eight. It was really good and does the job. I never faced any failure scenario or deadlock situation, and the support team was always helpful. These are the reasons for my rating. Overall, I would say the experience was good. I would recommend comparing it with Neo4j for your use case.