TrustRadius Insights
Neo4j has proven to be a valuable tool for a wide range of applications and industries. Users appreciate its efficiency in storing and …
Starting at $65 per month
View PricingOverview
What is Neo4j?
Neo4j is an open source embeddable graph database developed by Neo Technologies based in San Mateo, California with an office in Sweden.
Recent Reviews
Pricing
Aura Professional
$65
Cloud
per month
Community Edition
Free
On Premise
Enterprise Edition
Contact Sales
On Premise
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://neo4j.com/pricing
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Starting price (does not include set up fee)
- $65 per month
Product Details
- About
- Tech Details
- FAQs
What is Neo4j?
Neo4j Video
What Is Neo4j?
Neo4j Technical Details
| Deployment Types | On-premise, Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Windows, Linux, Mac |
| Mobile Application | No |
Frequently Asked Questions
Neo4j is an open source embeddable graph database developed by Neo Technologies based in San Mateo, California with an office in Sweden.
Neo4j starts at $65.
The most common users of Neo4j are from Enterprises (1,001+ employees).
Comparisons
Compare with
Reviews and Ratings
(33)Loading...
Attribute Ratings
Reviews
(1-9 of 9)Companies can't remove reviews or game the system. Here's why
Score 2 out of 10
Vetted Review
Verified User
Scaling is a huge issue in Neo4j. Clusters are supposed to allow horizontal scaling and they say they support billions of nodes, but in fact, a database with ~600 mil nodes and 1.5TB in size is barely manageable. Backups slow, count() times out, server restart will take hours (!!!!). And 2GB hard transaction limit is another hard candy of a clustered mode, requiring to use things like apoc.iterate for long updates, making them impossible to rollback in case something goes wrong (apoc.iterate commits results on the go).
So - if you need scaling, think twice.
So - if you need scaling, think twice.
- Graph traverse.
- Scaling and clustering.
- Transactions limitations.
- Performance on millions of data.
- Backup and restore.
August 26, 2021
To Neo4J or not to Neo4J? Neo4J all the way!
[Neo4j] is being used on the commercial side of our organization to help create network maps and see relationships between customers or end-users. I am not sure if other areas of the business are using it at the moment. I would say it is still in its infancy at our company, though.
- Show relationships between different data points
- Visualize network maps
- Show stronger influencers
- Be quicker at processing data
- Have less lagging when interacting with the network map
- Be able share with other users on a server
As [we are] working in the US healthcare domain, we have to deal with large databases like UMLS. It also contains more than 12 relationships among the nodes. To analyze and build a relational module, Neo4j is good choice for us. Mostly Neo4j is used in the R&D department for analysis. But it is also in use at application level to support queries on a large dataset.
- It's very efficient on large datasets to support the multiple relations between the nodes.
- Inserting or updating any node or relation is also very easy through the UI or a script
- Provides very good graphical representation to analyse or present a dataset
- Very good interactive UI for analysis of any dataset
- Though the performance is good on a small dataset it requires a well configured server for a large dataset
- Also graphical representation for less complex dataset is good but for complex dataset in which more than 10 relation possible graphs are not good
- Also the interactive UI for a complex dataset is little bit complex
December 18, 2018
Neo4j, best graph database out there!
We use Neo4j to manage all the relationships of our data. We didn't want to use anything else because joins get too slow for querying. Neo4j is actually the glue to our platform. Everything is connected using Neo4j, having it makes the management of our data fairly easy and also allows for easy analysis and reports.
- Easy way to query data.
- Easy way to insert and store relationships.
- Easy to visualize data in Neo4j browser.
- Easy to learn.
- Sometimes hard to visualize complex data analyses.
- Tough to see space used.
- Tough to allocate memory or other configurations.
We used Neo4J to store data that have tree relationships. It is being used by our entire organization for various data to be stored. It addresses the problem of storing data that has multiple relationships pretty well. Storing data in Neo4J allows for a very efficient way to look up nodes and their relationships are quicker than storing similar data in traditional SQL database.
- Mature Query language, I found Cypher QL to be mature in handling all sorts of problems we throw at it. Its expressive enough to be intuitive while providing rich features for various scenarios.
- Native support for REST API, that makes interacting with Neo4J intuitive and easy.
- Support for Procedures in Java, procedures are custom code that could be added to the Neo4J to write custom querying of data. The best part about the procedures is it could be invoked using the REST API. This allows us to overcome any shortcomings from their Cypher query language.
- Nice UI and interface for executing the Query and visualizing the response.
- UI access controlled by User credentials allows for neat access controls.
- Awesome free community edition for small-scale projects.
- Support for language based libraries. Currently, Neo4J only supports Java-based libraries. We used node and found issues with documentation and support for this library. It helps if Neo4J supports libraries in popular languages.
- Support for triggers, that's one of the neat features of Postgres and other traditional SQL databases.
- Support for indexes for data lookup. Looking up multiple nodes information using Neo4J is not very efficient, it is more optimized for looking up relationships between nodes. So adding that support would be very useful.
August 24, 2017
Where graph data modeling shines using Neo4j
I am using it as schemaless data store to persist my knowledge graph. As the name indicates, neo4j is a perfect choice when the query pattern is about finding the relationships between entities. I evaluated it with similar use cases, besides knowledge graph, where finding patterns was essential. It is a very good choice when joins are very common in a relational store. As the data is completely materialized, all joins are in constant time which tremendously improves query performance out of the box without extra system design.
- When joins are a common in a relational store, switching to Neo4j is better
- When pattern matching and surfacing interesting insights is the goal, neo4j's cypher is pretty powerful
- When schema is not completely known beforehand and needs to be evolved with time
- Better support for aggregation queries
- Drivers for Spark where ML or more computationally heavy jobs are to be performed
- Native support for complex properties for nodes and relationships
Score 10 out of 10
Vetted Review
Verified User
Neo4j provides the framework for our business’ cloud solution, which helps companies digitize their supply chains. It is used primarily by our developer team, but our entire organization benefits from it. We were looking for a solution that would be able to handle very complex queries without sacrificing performance, and Neo4j really addresses these issues.
- Very quick to get our project up and running (prototype built in less than 3 months).
- No performance issues even for very large amounts of data, and extremely quick search response time. No need to worry about problems for users of our platform.
- Always easy to extend functionality – Neo4j helps us accelerate our company development.
- Our developer team is very happy with the functionalities provided by Neo4j.
Neo4j was an experiment for us. We needed to model people and relationships for which graph databases were most suited. Google search resulted "Neo4j" on top, so we tried it, and it is awesome! The project, unfortunately, has been shut down, but at the time, we used it as the primary database for the application. The database model was designed such that every piece of information could be mapped to either a node or an edge, so we didn't need to use any sort of relational or other no-SQL database.
- Neo4j is extremely fast.
- Neo4j has its own query language CYPHER which is very intuitive and easy to use.
- Neo4j supports API in almost every language like Java, Python, PHP, NodeJS, etc.
- One of the hardest challenges that Neo4j had to solve was the horizontal scaling problem. I am not updated on recent developments, but at the time of my use, I couldn't find a viable solution.
- Neo4j does not play with other open source APIs like Blueprint. You have to use the native Neo4j API.
- There wasn't a visual tool to see your data. Of course, third party tools are always available, but I would have loved something which came with the Neo4j bundle. I love that Docker comes bundled with Kitematic, so it's not wrong to hope that Neo4j could also ship with some default visualization software.
September 12, 2016
Neo4j: Connecting the dots for graph data
We use Neo4j as storage for data that can naturally be modeled as a graph (think nodes and edges). It allows us to create rich objects with multiple properties, ingest them at reasonable rates, and the search against the graph and return results fast enough that you can run a website directly off it.
It's not a general data storage solution, but for applications where you can about the graph or network nature of the data it excels.
It's not a general data storage solution, but for applications where you can about the graph or network nature of the data it excels.
- It's very easy to install.
- The built in web interface is incredibly useful. It enables you to quickly test out queries and visualize the results.
- Third-party libraries/APIs are well represented. CYPHER isn't actually that hard to write directly, either.
- It would be nice to have some concept of namespaces, or some way of roughly making a single instance multi-tenant. It'd be nice to make sandboxing easier.
- Automatic backups could be improved.