GrapheneDB Blog

Updates from the GrapheneDB team

Find Us at GraphConnect 2015

GraphConnect 2015 is this week and we couldn’t be more excited to attend!

We are sponsoring the event and will be available at our booth all day to talk to anyone interested in GrapheneDB. If you’re an existing client, we’d love to touch base and see how you’re enjoying our service. If you’re considering using GrapheneDB, we’d love to talk to you as well to see how we can help you build something great with Neo4j!

What to expect at the GrapheneDB booth

There will be lots of goodies at the GrapheneDB booth. There will be plenty of swag to bring back home, plus we’re giving free credits towards a standard or production plan to those who come visit us at the booth.

Preview new features

We’ll be launching a new metrics dashboard feature soon, but if you’d like to get a sneak peek, please come find us. We’re looking for new or existing customers who may be interested in participating in the beta for this feature. Come get a demo of our new metrics dashboard and sign up for the beta.

Talks we’re looking forward to

In addition to sponsoring, we’re also looking forward to the following talks, so this is where you’ll find us during the conference.

We are, of course, looking forward to Emil Eifrem’s keynote at 9:00am. We can’t wait to hear what news he has to share with the community. In addition, we’re especially interested in:

  • “Real-Time Recommendations with Graphs and the Future of Search” by Michal Bachman, at 2:40pm.

  • “Advanced Neo4j at FiftyThree” by Aseem Kishore at 4:20pm.

  • “Polyglot Persistence for Microservices using Spring Cloud and Neo4j” by Kenny Bastani and Josh Long at 5:05pm.

Now you know where to find us and what to look forward to. Be sure to follow us on Twitter (if you aren’t already) for conference updates. We hope to see you there!

Announcing New Features and Partnerships

Just in time for GraphConnect 2015, we couldn’t be happier to announce two new features coming soon to the GrapheneDB service, as well as two new partnerships.

High availability clustering

Our clients have come to expect the best from GrapheneDB and we want to continue to deliver the best solutions for our customers. We’re proud to announce we are adding clustered deployments on Neo4j Enterprise Edition to our offering.

If you want improved uptime and reliability, or if you’re looking to scale read traffic, our high availability clustered deployments are the right choice for you. Perhaps you’re looking to run reporting on a separate instance without hurting your production environment? Our clustering option can help.

Our high availability offering is custom for each client, if you’re interested in discussing this option, please fill out this form and we will be in touch to discuss with you further.

New metrics dashboard beta

We’re also very excited to announce our new metrics dashboard beta.

GrapheneDB Neo4j server metrics

Our metrics dashboard will allow you to track server errors, as well as see when errors are happening. You will also be able to track median and 95th percentile response times, as well as see incoming HTTP requests. Access to this information will allow you to see what is happening with your Neo4j server in real-time, which can help you diagnose performance issues in order to fine tune your application.

This level of data detailed in an easy-to-use dashboard is something not offered by other Neo4j database-as-a-service providers, and can give you greater visibility into what is happening with your server. If you are interested in trying the metrics beta, please contact us at

Neo4j and Amazon Web Services partnerships

Lastly, we’d like to announce new partnerships with Neo4j and Amazon Web Services.

As a Neo4j Solution Partner, you will benefit from our advanced deployment options with Neo4j Enterprise Edition. As a partner, we have access to expert support straight from Neo Technology, which in turn benefits you — our customer.

As an Amazon Web Services partner, you can enjoy all of the benefits of GrapheneDB, coupled with the service from the largest cloud hosting provider in the world. This truly makes GrapheneDB the best, fastest option to run Neo4j on Amazon Web Services.

These new partnerships solidify our commitment to you, our client, that we seek to partner only with the very best to provide you with the world-class service you need.

GraphConnect Europe 2015, Introducing Azure Beta & Neo4j Server Logs

GrapheneDB is proud to sponsor GraphConnect Europe 2015 (London, May 7th), the only conference that focuses on the rapidly growing world of graph databases and applications that make sense of connected data.

If you’re at the conference, please find us and say hello. We’d love to chat about graphs and have swag with us for you!

We’ve also got some great news to announce!

GrapheneDB on Azure now available in beta

Neo4j Databases Now in Beta on Microsoft Azure

Are you hosting your applications on Microsoft Azure? Now you can take advantage of GrapheneDB’s fully managed Neo4j hosting service, too.

Create your free Neo4j on Azure now

Microsoft Azure has been one of the most requested providers on GrapheneDB for a long time. We’re happy to announce beta availability of GrapheneDB hosted Neo4j databases on Microsoft Azure.

The service on Azure is currently in public beta with the Sandbox plans generally available in the regions East US 2 and North Europe.

Sandbox databases are a fantastic way to discover the value of GrapheneDB’s fully-managed Neo4j hosting service on Azure or get acquainted with Neo4j. In addition to having your database up and running in a few seconds you can:

  • Access to the Neo4j browser interface
  • Export and restore databases on demand
  • Access the server log files

Want to take the new Azure deployments for a spin?

If you’re already a GrapheneDB user, you can create an Azure deployment from the new database form by selecting “Microsoft Azure” as the provider.

GrapheneDB provisioning on Azure Beta

New to GrapheneDB? This link will take you through the signup process and then to the next step where you’ll be ready to provision your Azure-hosted Neo4j instance. It takes less than a minute to be up and running!

Need production-grade Neo4j hosting on Azure?

Besides the free Sandbox plans, we’re also offering our Performance plans to a select set of beta customers. We plan to make the rest of our plans generally available as soon as possible. Get in touch.

New Feature: Neo4j Log Files

We’d also like to introduce you to our newest feature: Neo4j Server Logs.

This feature enables GrapheneDB users to diagnose and debug issues by providing access to the Neo4j server log files from the user interface.

Streaming of Neo4j Log files on GrapheneDB

We want to make it easy for our users to access the log files when necessary–for instance, when debugging a custom plugin or server extension, or when trying to determine if there are any errors.

How it Works

There are two ways to access the log files:

  • In-browser streaming (similar to the tail UNIX command ): Streaming can be paused to scroll up/down, examine or copy certain sections of the file.
  • File download: Enables you to download the files to your computer for further inspection.

We provide access to the following log files:

  • messages.log
  • neo4j-0.0.log

Server logs are available on all our plans.

As always, we look forward to receiving your feedback.

Introducing Team Collaboration

Team collaboration

Most of our customers are small- to medium-sized development teams that work together on applications. In such work environments it is desirable that multiple developers have access to all production databases, and that they can deploy new instances when testing out new features or setting up new environments.

GrapheneDB has added a new team collaboration feature, making it easy for teams to work together on their Neo4j databases and manage their account easily.

There are three different user roles:

  • owner: the account used to sign up, full access
  • admin: can manage billing details, collaborators and databases
  • collaborators: can manage databases

Managing users is very straightforward. If you’re an account owner or admin, you can add/edit/remove team members from the Users tab in the account area:

Creating a new user

Collaborating on databases

All users within the same account can manage existing databases and provision new instances, without having to add any billing details to their own accounts.

Collaborating on billing

If you have multiple co-founders, or if you need someone from your team to update the billing details and make sure payments get done in time, you can add admin users to your account.

Admins have full access to the billing area, in addition to unrestricted permissions to manage databases. They can also add or remove team members or change their roles.

Collaborating on support

When opening support tickets through our UI, you can also include other team members in CC. They will receive email notifications to any updates on the support ticket, enabling everyone to be on the same page and participate in the conversation.

CC team members in support requests

If you have any questions or comments, or want to provide feedback about this feature, please get in touch.

Neo4j 2.2 on GrapheneDB

First up, congratulations to Neo Technology, especially the engineering team, for releasing Neo4j 2.2!

Neo4j 2.2 Browser UI

A lot of you have been asking when it’s going to be possible to try out the recently released Neo4j 2.2 on GrapheneDB. That’s why we’re happy to announce that you can now upgrade your GrapheneDB deployments to Neo4j 2.2.

As a major new version with plenty of new features, we don’t suggest you go straight into production with it.

What we do recommend at this point is that you begin testing with a new Neo4j 2.2 deployment to ensure that you don’t run into any unexpected issues. As with other releases that include store-migrations, the version upgrade will be non-reversible, so proceed with caution.

We will be tracking and iterating updates to Neo4j 2.2.x as they are released.

Also, we recommend to upgrading to Neo4j 2.1 before embarking on the 2.2 update.

Try Neo4j 2.2 on GrapheneDB for free!

Noteworthy changes

Users are reporting performance improvements of 20% and higher without any changes in code or queries.

Here’s a short summary of what to expect when upgrading:

  • A major overhaul of the Neo4j Browser, including the ability to visualize query plans and terminate running queries!
  • Fast-write buffering which dramatically increases the throughput of many write workloads.
  • A new pagecache, which is faster and easier to configure. If you’ve struggled to configure your Neo4j memory caches before, you’ll love this one!
  • Full support for profiling and explaining Cypher query plans, including a query plan visualizer in the Neo4j Browser.
  • A new cost based query planner for Cypher, which is smarter at planning queries, in addition to the existing rule based compiler. Neo4j will be smart and will automatically figure out which to use for each query.

For the full list of changes, please look at the release notes for Neo4j 2.2.

Try Neo4j 2.2 on GrapheneDB now!

Want to Host Your Neo4j Databases in Europe? We’ve Got You Covered! ;)

Announcing General Availability of all GrapheneDB plans in AWS EU and Heroku EU regions

At GrapheneDB, we’ve been offering dedicated instances in the EU region since the beginning of our beta phase, but the plans on the Hobby and Standard tier have only been available in the N.Virginia AWS region for most of the time. The reasoning behind this is there was not enough demand for shared instances in Europe to justify setting up and operating the necessary infrastructure.

Europe map

Demand has been increasing steadily over the last couple of months and our European users have been frequently asking us for more affordable plans in the EU region.

We’ve heard you loud and clear and this is why we’re happy to announce that all our AWS plans are now available in the AWS eu-west-1 region (Ireland).

Create your free EU hosted database now

Click on the button above and follow these steps to provision your database in Europe:

  1. Choose a plan (our free Sandbox plan is available in Europe, too!)
  2. Enter a name and select EU (Ireland) region in the AWS region selectbox
  3. You’re set!

Provisioning a Neo4j instance in the AWS EU region on GrapheneDB

GrapheneDB Heroku add-on now available for Heroku EU apps

If you’re using our Heroku add-on, we’re also happy to let you know that it’s now also compatible with the Heroku EU region, making it easy for you to deploy your apps in Europe.

All databases provisioned through the add-on (even thee free Chalk plan) for apps in the Heroku EU will automatically be hosted in the AWS eu-west-1 region (Ireland).

If you haven’t yet, check out our Neo4j add-on for Heroku now. We’ve got free plans to get you started there, too.

Populate Your GrapheneDB Neo4j Instance With a Custom Generated Graph

At GrapheneDB, we are frequently approached by developers working on Neo4j-powered applications, with questions about graph modeling. In this post, we will walk through the process of generating a custom graph with sample data and then populating your GrapheneDB Neo4j instance with it.

If you have data, we usually recommend importing it into Neo4j as outlined in a previous blog post. At that point, you can model the problem, run sample queries and iterate until you get the results you want.

But what if you don’t have any real-world data available? Then generating a sample dataset is probably the best option.

To get started, we recommend Graphgen, a component of the Neoxygen set of tools developed by Christophe Willemsen. It’s a free, open-source, web-based graph generator that you can use to populate Neo4j graphs with sample data. It has following features:

  • A wide range of sample data providers: people’s names, addresses, phone numbers, company names, email addresses, domain names, etc.
  • It relies on a sort of pseudo-Cypher syntax, with the ability to create complex structures
  • and… it’s also capable of populating GrapheneDB instances!

Let’s walk through a detailed example, focusing on people working at companies and the friendship relationship between them.

Step 1: Provision your Neo4j database on GrapheneDB

If you haven’t already, sign up for a free GrapheneDB account at Once logged in, create a new, sandbox database. It’s free!

Creating a Neo4j instance on GrapheneDB

Step 2: Generate the dataset

Sample graph model

Let’s model a simple graph with people and companies:

  • People will be stored as nodes with label Person and a property fullName.
  • Companies will be stored as nodes with label Company and a property name.
  • A Person node can have a KNOWS relationship to other Person nodes
  • Person nodes have a WORKS_AT relationship to a Company

In order to generate this in Graphgen, we will need to describe the pattern in pseudo-Cypher syntax:

(person:Person {name: fullName} *35)-[:WORKS_AT *n..1]->(comp:Company {name: company} *10)
(person)-[:KNOWS *n..n]->(person)

This short snippet will generate:

  • 35 nodes with the Person label and a randomized full name property
  • 10 companies with random company names
  • A relationship WORKS_AT connecting every person to a single random company (n..1)
  • And relationships KNOWS between the Person nodes (many to many, n..n)

Notice the syntax is almost standard Cypher, but with some simple additions to specify properties using formatters, indicate the amount of nodes to create, define the relationships and their cardinality. For further details please read the project documentation.

Next, open, put your code snippet in the text area and hit the Generate button. The resulting dataset will be rendered as an interactive graph which you can navigate.

Generating the graph with Graphgen

Step 3: Populate your GrapheneDB Neo4j instance with the generated dataset

Click on the Populate your database button. A modal dialog will pop up, with fields for the URL, username and password.

Fill out these fields with the connection details located in the Connection tab for your Neo4j instance in the GrapheneDB user interface: URL, username and password.

Populating the database with Graphgen

Step 4: Browse and query your generated dataset on GrapheneDB

Loading the generated graph into your GrapheneDB should take just a few seconds. After the process is completed, go back to GrapheneDB’s interface.

In the overview tab, use the Launch button fire up Neo4j’s web-based browser UI.

Browsing the generated graph in Neo4j

If you, like us, also find Graphgen a useful tool, make sure to say thanks to Christophe for putting it together and stay tuned to his Twitter account for some nice upcoming features.

Graphgen is open-source and you can also have a look at other great Neo4j related tools Christophe put together at, like neoclient, a PHP client for Neo4j which is also supported by GrapheneDB.

Neo Technology Just Closed $20M in Funding. Here’s Why It’s a Big Deal!

Neo Technology, makers of Neo4j, announced their $20M Series C round yesterday, bringing the company’s total investment to date to $44M. The funding announcement was covered by popular media such as Techcrunch, Venturebeat, Gigaom, Pando and Forbes. The official press release from Neo Technology is here.

Why graph databases

Companies have identified data-driven operations, and decisions, as keys to success. But we live in an increasingly connected world, and traditional databases can’t handle the amount of connected data that holds together our social, personal and professional networks.

Graph databases, on the other hand, outperform traditional databases by factor of thousands when managing complex, connected data. They have inherent advantages in an environment where everything is connected.

Neo Technology makes Neo4j, the market leader in graph databases. With its intuitive query language Cypher, the interactive browser interface introduced in 2.0, and the new ETL functionality introduced in 2.1, Neo4j is moving quickly and acquiring a noticeable head start and consolidating itself as the graph database for apps.

Graph databases are here to stay

Graph databases organize information more intuitively than traditional databases. Developers can query data and ask questions that traditional databases don’t. Simply put, they’re built with connectedness in mind.

Graph databases are here to stay, and will be very influential in the coming years. Forrester predicts 25% of the enterprises to be using graph databases by 2017 [1].

An ecosystem of providers around Neo4j is emerging, be it hosting, visualization,or complementary libraries. Over the coming years we’ll continue to see others emerging. Neo4j is a central piece of technology for many companies and these providers bridge certain gaps in the value-add chain that make graph databases easier to adopt, use and extract value from.

Neo Technology knows it, and so do its investors.This funding milestone is another sign of the graph database market picking up steam.

Taking Neo4j to the Cloud

At GrapheneDB, we are big believers in graph databases. Our goal is to make Neo4j technology accessible and easy for developers to use. That’s why we created our hosted database platform.

GrapheneDB is a part of the ecosystem that’s emerging around Neo4j technology. We took the core Neo4j technology, built an automated operations layer and a user-friendly interface to manage operational aspects, such as configurations, plugin management, and backups. By taking care of operations, our users are able to focus on developing graph-powered apps and increase their productivity, knowing that they we will make sure their database runs around the clock.

We provide different levels of service, from Hobby, to get started, to Production-grade plans with automatic backups and server monitoring. No matter the app, our platform helps you get graph database instances up and running.

Try us out for free

If data-driven operations and decisions are keys to success, then find out how graph databases can help you. Go to and get started with one of our free plans.

[1] TechRadar(TM): Enterprise DBMS, Q1 2014. Forrester Research. 2-13-14

Importing Data Into Neo4j via CSV

At GrapheneDB, a question we get asked quite often from users is how to import data. Sample datasets are good, but loading your own data is even better. This post will explain how to import data from a CSV file into Neo4j. After outlining the steps to take, we list some special considerations for GrapheneDB users.

One of the most important steps when evaluating a new technology for your stack is importing existing data. CSV is one of the most popular standards for data exchange and most of the popular database engines support exporting data in CSV format.

Starting with 2.1, Neo4j includes a LOAD CSV [Neo4j Docs] Cypher clause for data import, which is a powerful ETL tool:

  • It can load a CSV file from the local filesystem or from a remote URI (i.e. S3, Dropbox, Github, etc.)
  • It can perform multiple operations in a single statement
  • It can be combined with USING PERIODIC COMMIT to group the operations on multiple rows in transactions to load large amounts of data [Neo4j Docs]
  • Input data is mapped directly into a complex graph structure as outlined by the user
  • It’s possible to manipulate or compute values in runtime
  • It allows merging existing data (nodes, relationships, properties) rather than just adding it to the store


Have your graph data model ready

Before running the import process you will need to know how you want to map your data onto the graph. What are the nodes and relationships, and which properties will they have?

Tune cache and heap configuration

Make sure to increase the heap size generously, specially if importing large datasets, and also make sure the file buffer caches fit the entire dataset.

You can estimate the size of your dataset on disk after the import by using the table in the official Neo4j docs.

Let’s assume we are going to store 100K nodes, 1M relationships and a fixed-size property per node/relationship (i.e. an integer number) :

  • Node store: 100,000 * 15B = 1.5 MB
  • Relationship store: 1,000,000 * 34B = 34MB
  • Property store: 1,100,000 * 41B = 45.1 MB

Those are the minimum values that we should use in your filebuffer cache configuration.

Set up indexes and constraints

Indexes will make lookups faster during and after the load process. Make sure to include an index for every property used to locate nodes in MERGE queries.

An index can be created with the CREATE INDEX clause. Example:

CREATE INDEX ON :User(name);

If a property must be unique, adding a constraint will also implicitly create an index. For example, if you we want to make sure we don’t store any duplicated user nodes, we could use a constraint for the email property.


Loading and mapping data

The easiest way to load data from CSV is to use the LOAD CSV statement. It supports common options, such as accessing via column header or column index, configuring the terminator character and other common options. Please refer to the official docs for further details.

To speed up the process, make sure to use USE PERIODIC COMMIT, which will group multiple operations (by default 1000) into transactions and reduce the times Neo4j has to hit the disk to commit the changes.

LOAD CSV WITH HEADERS FROM "file:///tmp/users.csv" AS csvLine FIELDTERMINATOR ';'
MERGE (u:User { email:}) ON CREATE SET u.username = csvLine.username, =;

Please note that values are read as Strings, so make sure you do format conversion where appropiate, i.e. toInt(csv.columns) when loading integer numbers.

The load process can be run from the Neo4j shell, either interactively, or by loading the Cypher code from a file using the option -file filename.

Alternatively, the code can be entered manually into the shell or the browser UI.

Considerations for GrapheneDB users

A few considerations when loading data into your GrapheneDB Neo4j instance:

  • caches and heap can only be configured on the Standard plans and higher. They are fixed on the lower-end plans
  • neo4j-shell does not support authentication and thus it can’t be used to load data into an instance hosted on GrapheneDB or otherwise secured with authentication credentials
  • when running the command from the browser UI, bear in mind Neo4j won’t be able to access your filesystem. You should provide a publicly available URL instead, i.e. a file hosted on AWS S3
  • for larger datasets, we recommed running the import process locally and once completed, perform a restore on your GrapheneDB instance

For a comprehensive tutorial, including tools to clean up the CSV files, common pitfalls and more advanced tools like the super fast batch importer please refer to this comprehensive CSV import guide.

Please don’t hesitate to post any comments or contact our support team if you are having issues loading data into your GrapheneDB instance.

GrapheneDB Concludes Beta Phase, Releases New Plans

GrapheneDB has concluded the beta stage of its product development.

Leaving beta stage means that the service’s core functionality has been tested and proven. A significant user base has adopted GrapheneDB’s platform for hosting managed graph databases.

As GrapheneDB continues to improve on current features and build additional ones, customers can register now, knowing they’ll get a reliable, straightforward hosting service for their graph databases.

“Success Kid” Photograph (c) Laney Griner / Used with Permission

“Our cloud hosting platform operates the largest fleet of managed Neo4j databases,” says Alberto Perdomo, GrapheneDB co-founder. “We built this platform as developers, for developers. There was no good, reliable hosting service for graph databases, so we built GrapheneDB.”

GrapheneDB’s flexible tier and plan system means that developers can test ideas before taking an app into production.

To learn more about GrapheneDB, visit To view pricing and register a free account, visit