Neo4j supported versions

GrapheneDB’s commitment is to offer the newest Neo4j version as soon as they are compatible with the service.

Once a Neo4j version is no longer supported by Neo4j, GrapheneDB will remove it from the deployment options and all the customers with databases running unsupported versions will get a period of 6 months to upgrade their databases.

After that period, the database will be automatically upgraded to the next available supported version as part of a maintenance operation. We strongly encourage you to take action before to avoid any compatibility issues on your end. Read more about how to upgrade on this article.

Support matrix

Neo4j release

End of support from Neo4j

End of support from GrapheneDB


December 1, 2024

June 1, 2024


December 16, 2022

June 16, 2023


May 16, 2022

November 16, 2022


December 23, 2021

June 23, 2022


July 14, 2021

January 14, 2023


May 27, 2022

November 27, 2022


March 31, 2020

June 30, 2021


April 28, 2019

June 30, 2021


November 31, 2018

January 15, 2021


June 13, 2018

January 15, 2021


October 31, 2017

January 15, 2021


April 21, 2017

January 15, 2021

2.2 and older

September 25, 2016

January 15, 2021

GrapheneDB process to support a version

Patch versions

Every new patch release will be tested before offering it on GrapheneDB. There will be a waiting period of one week before GrapheneDB offers the release to ensure there is no major announced bug present.

GrapheneDB will only offer the latest working patch version as a deployment option. You can always check the patch version you’re running by checking the admin interface in the Overview page for example, but you won’t be able to choose from different patch versions while you deploy your database.

GrapheneDB wants to keep new deployments always running with the latest patch version. You can always upgrade your patch version by using the Neo4j upgrade feature.

Minor versions and major versions

Minor and major versions contain changes that could break compatibility with GrapheneDB service. Therefore GrapheneDB will make sure to work with alpha releases as soon as possible to do the necessary changes to support them.

After the minor or major version release GrapheneDB will wait for 2 weeks to offer it as a deployment option. New major and minor versions usually contain bugs right after release, that’s why the period of 2 weeks