Changelog
Follow up on the latest improvements and updates.
RSS
new
AuraDB Virtual Dedicated Cloud
AuraDB Professional
AuraDB Business Critical
User Tools Support over HTTPS in Console
- Allows connections over HTTPS (port 443) when network security blocks Bolt (port 7687)
- Helps customers connect Neo4j user tools using Query API
- Works with existing SSO configurations for Query / Explore

new
AuraDB Virtual Dedicated Cloud
AuraDB Professional
AuraDB Free
Data Importer
Import from BigQuery and VDC support


new
AuraDB Professional
AuraDS Professional
AuraDB Business Critical
New invoice structure for Neo4j Aura
- total AuraDB and AuraDS instance usage in GB-hours under "Qty."
- total GraphQL usage in MB-hours under "Qty."
- total Aura Graph Analytics usage in GB-minutes under "Qty."
- total charge for the respective Aura product under "Amount".

new
AuraDB Virtual Dedicated Cloud
AuraDB Professional
Important Final Reminder: Support for creating AuraDB version 4 instances ending May 31, 2025
new
AuraDB Virtual Dedicated Cloud
AuraDB Professional
AuraDB Free
AuraDS Professional
AuraDS Enterprise
AuraDB Business Critical
Neo4j Aura Database May Release Update
- dbms.components() procedure will now also include the supported cypher versions.
- bug fix in pipelined runtime, where in certain scenarios cached properties in an OPTIONAL MATCH were not properly cleared between rows, which could lead to incorrect results.
new
AuraDB Virtual Dedicated Cloud
AuraDB Business Critical
Adjustable Storage now available for AuraDB on GCP!

- Greater Flexibility: Scale resources to better suit your needs
- Cost Efficiency:Avoid additional compute expenses when only extra storage is required.
- Enhanced Experience: Eliminate manual processes and custom workaround requests through Support teams
new
AuraDB Professional
AuraDB Business Critical
Neo4j Announces GraphQL API for Neo4j AuraDB
- The new GraphQL API enables developers to:
- Create precisely tailored queries that return only needed data
- Reduce over-fetching and under-fetching of data
- Build more responsive applications with fewer round trips
- Leverage declarative data fetching while maintaining the power of graph relationships
- AuraDB Professional Trials
- AuraDB Professional
- AuraDB Business Critical
new
AuraDB Virtual Dedicated Cloud
AuraDB Business Critical
Neo4j Aura Graph Analytics Now Available!
- Provides up to an 80% increase in model accuracyand deeper insights by transforming graph structures into ML-ready features with graph embeddings
- Delivers 2X faster insightscompared to open-source alternatives through parallelized in-memory processing of graph algorithms
- Uses 75% less code and zero ETLwith 65+ prebuilt, optimized graph algorithms, native Neo4j integration, and support for projections using any data source
- Removes administrative overhead and lowers TCOwith no server provisioning, pay-as-you-go pricing, and independent scaling of compute and storage
new
AuraDB Virtual Dedicated Cloud
AuraDB Professional
Important: Support for creating AuraDB version 4 instances ending May 31, 2025
new
improved
AuraDB Virtual Dedicated Cloud
AuraDB Professional
AuraDB Free
AuraDS Professional
AuraDS Enterprise
AuraDB Business Critical
Neo4j Aura Database April Release Update
- Neo4j Admin Database upload http requests have changed to ensure compatibility with the new Aura console.
- Introduce --error-format argument to Cypher Shell to control how errors are displayed. See Operations Manual.
- Transient error is not thrown when returning startNode and endNode on a deleted relationship.
- The AggregationSkippedNull warning is not sent going forward as this is the expected behaviour
- Fixes a bug that could cause incorrect ‘Mixing label expression symbols ('|', '&', '!', and '%') with colon (':') between labels is not allowed..’ errors.
- Fixes a bug where EXPLAIN would sometimes report slightly modified return columns if these variables were reused in the query.
- Fixes an issue in Legacy runtime where relationships created in a FOREACH block would all be created with a rightward direction ie FOREACH (... | CREATE (a)<-[:R]-(b)) would create (a)-[:R]->(b) relationship