You can get started for free with one or more Sandbox databases straight away. No trial period, credit card or upfront commitment required.
You can create and delete databases as you need, as prices are pro-rated by the day. At the end of every month, your spend will be calculated based on how many days each of your databases has been running. We will then collect one single payment from the card on file or pre-paid funds on the account.
Non-profit and educational organizations are eligible for discounts. We also offer discounts to customers that do upfront payments. If you’d like to discuss a discount, please contact us.
There are no hidden extra costs like one-time setup or cancellation fees. We don’t charge for support or data transfers (unlimited).
Should you want to take your data elsewhere, databases can be exported at any time. Data will be immediately available as a download, which can be loaded into an instance hosted locally or anywhere else.
There is no commitment. If you want to cut your spending, you can delete paid databases at any time (remember to export before!) and continue to use our Sandbox databases for free. There is no need to close your account as we only charge for running paid databases.
Should you decide to delete your paid databases, a payment needs to be collected for the time these databases have been running in the current month before deletion. After the next billing cycle, there will be no further payments, unless there are any outstanding invoices or new paid databases are created.
You can have as many paid databases in your account for as long as you want. Free Sandbox databases are limited to 10 per account. This limit can be increased in certain cases.
GrapheneDB does not enforce any artificial limits on data transfer, bandwidth or concurrent connections. Data storage in Standard, Performance and Enterprise databases is limited only by disk size, while storage in the Hobby tier is limited by the number of nodes and relationships based on the plan.
A database will be switched to read-only mode when it exceeds the maximum storage size. (For Hobby accounts, exceeding the node count or relationship maximum count will also set the database to read-only status).
If you wish to turn the database back to read-write mode, the simplest solution is to increase the database capacity by upgrading to a higher plan. You can do this by cloning the database from the GrapheneDB UI using the Upgrade/Clone button. This will create a new instance of the database, but the original instance will continue to be up and running. It's your responsibility to remove the original database if you don't need it anymore in order to avoid any potential charges.
If you don't want to upgrade to a higher plan, but would like to reduce the size to stay within the capacity of your current plan, you can follow these steps:
- Download your database as a tarball (go to “Admin” tab, then click on “Export database” button)
- Unpack the downloaded tarball and put the directory inside the /data directory of your local Neo4j installation.
- Start your local instance and reduce your dataset
- Stop your local instance, compress the dataset and restore your GrapheneDB database with the compressed file (go to Admin tab, then click on Restore database button)
Hobby instances that receive no inbound traffic in a 30 minute time period will transition into sleeping state. Upon the next incoming request, they are awakened and the request is processed as soon as the database is up and running.
The wake-up process takes just a few seconds, so there is no need to worry. Your app shouldn’t suffer from any database unavailability, just a slight delay on the first request after a sleeping period.
Note: This only applies to GrapheneDB Hobby databases.
Hobby, Standard, and Performance plans run on Neo4j Community Edition.
GrapheneDB also operates Enterprise Edition deployments. This requires a license, which can be obtained from GrapheneDB (buy through us) or supplied by the customer (bring your own). If you are interested in operating a Neo4j Enterprise deployment with us, please contact our sales team.
If you are a startup, you may qualify for special discounts if your company has less than 50 employees and earns less than $3M in annual revenue. Contact us for details.
Hobby, Standard, and Performance databases are single-server deployments running Neo4j Community Edition.
GrapheneDB supports clustered High Availability deployments with Neo4j Enterprise Edition. As these plans are custom, please contact our sales team if you are interested in our High Availability options.
Yes, all production-ready plans (Standard, Performance, and Enterprise) feature daily automated and on-demand hot backups.
Backups are verified for consistency and archived for 7 days. Backups are downloadable by the customer and can be used to restore the database or to clone into new instances.
All plans, including Hobby databases, also feature an Export feature, which will stop Neo4j and provide a downloadable copy of the Neo4j store files.
Our dashboard is a rich front-end application that should work with any popular modern browser. If you use our app with an older or unsupported browser, a warning message is displayed at the top of the page. You might encounter errors while using the dashboard if you are using an older, unsupported browser.
GrapheneDB currently supports:
- Microsoft Internet Explorer 10 and higher
- Microsoft Edge 12
- Safari 5 and higher
- Google Chrome 21 and higher
- Firefox 19 and higher
- Opera 13 and higher
You may see an “SSL not available” warning displayed below the link to Launch the Neo4j/Browser interface if it's not possible to open the interface through HTTPS.
This means that you're running an older version of Neo4j. The old webadmin does not work properly in SSL proxy scenarios (see this Github issue). We recommend you upgrade to a newer version of Neo4j in order to resolve this issue. Versions 2.0.x and higher work just fine.
For security reasons, Microsoft Internet Explorer 11 and Microsoft Edge do not support embedding HTTP basic authentication credentials in URLs. This is described in this Microsoft Knowledge Base article. When accessing the Neo4j browser from Internet Explorer 11, we will display the username and password for copying and pasting into the authentication dialog that will be opened by the browser.
When HTTP basic authentication credentials are embedded in URLs, Safari will display a warning about a potential phishing attack. It is safe to ignore the warning and follow the link from the UI, as long as you are browsing https://app.graphenedb.com.
Updated about a year ago