Follow up on the latest improvements and updates.

RSS

April 24, 2026

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Fleet Manager

Aura Console User Password Requirements

Boosting Your Aura Security 🔐
To keep your graphs under lock and key, we’re rolling out a small update to our password policy and a friendly reminder about your security toolkit.
What’s Changing?
Starting today, the minimum password length for the Aura Console is increasing to 16
 characters.  This will apply to any new users, or any users that reset their password.
Why the change?
While "Gr4ph123
" was a solid start, modern security standards have evolved. Experts such as NIST now agree that password length, combined with always using a unique password, are the best defense against attacks. A longer password creates exponentially more entropy, making it much harder for bad actors to guess, while remaining easier for humans to remember if you use a simple passphrase (e.g., Correct-Horse-Battery-Staple).
Level Up with MFA 📱
A strong password is a great first layer, but why stop there? We highly recommend enabling Authenticator-based TOTP MFA (Time-based One-Time Password) as this is ultimately the best way to protect your Aura account.
How to do it:
Log in to the Aura Console using email/password.
Go to Account > Settings > Preferences > Security.
Enable Multi-Factor Authentication (MFA).
Follow the MFA set up steps.
If you are an Org admin, you can make Authenticator-based MFA mandatory for all of your org users in the Organization Security Settings.  It only takes a minute, but it gives you peace of mind that lasts much longer.
Action Items for You
Update your password: If you're using a short password it is time to update it.  The next time you change your password, you’ll be prompted to meet the new 16-character requirement.
Enable MFA: If you haven’t already, grab your favorite authenticator app (like Google Authenticator or Authy) and link it to your account.
Pro Tip: Using a password manager makes meeting this 16-character requirement a breeze. Let the robots do the remembering so you can focus on the querying!

April 23, 2026

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

Dashboards

Dashboard actions now available

The Neo4j Dashboards tool now has

Actions

available for all Aura tiers:

Build interactive filtering based on table cells
Create checklists and let users select parameters dynamically
Add in drilldowns to enable rich dashboarding applications

Check out the documentation to learn how to add actions into your own dashboards.

April 22, 2026

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura Database April Release

The Neo4j Aura April release is now rolling out—starting with AuraDB Free and gradually extending to higher-tier instances.

This release focuses on strengthening GQL compliance, expanding GenAI capabilities with new AI token functions, and improving memory efficiency for complex queries.

🚀 New Cypher 25 Features (GQL Standards)

We are continuing our commitment to GQL (Graph Query Language) standards by introducing new predicates and statements that align Cypher with international standards:

IS LABELED / IS NOT LABELED
: New GQL-compliant predicates to test for node labels (equivalent to the existing
IS
and
IS NOT
syntax). More details on Cypher Manual.
FOR Statement
: You can now use the GQL
FOR
statement to extract individual rows from a list (the GQL equivalent of
UNWIND
).

🤖 New AI Token Handling Functions

To further support GenAI and LLM integration workflows, we’ve added two new functions to help manage context windows and token limits:

ai.text.chunkByTokenLimit
: Automatically split input strings into lists while respecting specific token limits. Link to Docs.
ai.text.countToken
: Easily estimate the token count of a given string directly within your query. Link to Docs.

📈 Performance & Infrastructure Improvements

Memory Optimization
: Significant reduction in memory usage for the
SHORTEST
statement and improved precision for memory tracking within the Top operator.
Parallel runtime
memory tracking enhancements: Improved the precision of memory tracking within the Top operation.
Detailed
version reporting
in query output: EXPLAIN and PROFILE output now consistently includes the underlying Neo4j version, reporting down to the point release.
Drivers
: Updated
neo4j-java-driver
and
netty-bom
.

🛠️ Bug Fixes

Vector Indexing
: Fixed an issue where quantized data in
vector-3.0
indexes wasn’t being utilized at query time. This fix reduces memory usage for vector searches without requiring an index rebuild.
RBAC/PBAC
: Resolved an error that occurred when running duplicate Property-Based Access Control commands containing temporal functions.
Show Databases
: Fixed an incorrect error message when passing a parameter with the incorrect type to SHOW DATABASES.
Stability
: Fixed a rare record format bug related to iterating relationships on nodes that concurrently become dense.
Pathfinding
: Fixed a bug where
SHORTEST
would occasionally omit valid paths when multiple targets were present.

For full details of all updates and fixes in this release, please visit: Release Notes: Neo4j Aura Database – April 2026.

April 21, 2026

new

Export results from Neo4j Graph Intelligence to your Lakehouse in Microsoft Fabric

Great news if you use Microsoft Fabric in your organization. You can now export the results from your graph analysis back to the Lakehouse.

Feature

Export is only available for Graph Datasets created from data in Fabric.
The import model used to transform the Lakehouse-to-graph governs which nodes and relationship types are exported.
Choose between updating the original source tables OR creating new results tables.
Documentation is available here.

This feature is not available for Graph Datasets created by connecting an existing Aura database to Fabric

April 20, 2026

new

Desktop

New Console

Neo4j Desktop 2 v2.1.4 - Connect to Desktop in Aura console

What's new

We've added a

'Neo4j Aura' button

in Neo4j Desktop v2.1.4, for migrating local databases and seamlessly connecting to Aura tools.

See your running Desktop instances inside the Aura console and use cloud-only features and AI-assistants. Look for the 'From Neo4j Desktop' instance label in the self-managed tab. Switch back to Desktop to manage local instances. To use AI-assistants with Desktop instances make sure you install the APOC plugin, find it in the local instance (...) menu > 'Plugins'.

Other core changes

Swapped to the Azul JRE, instead of JDK, to save space
Added support for accepting self-signed certificates for remote connections
Added URI input validation to various connection modals
Added a forgotten password reset, find it in the local instance (...) menu > 'Security'

Fixed a token refresh 'API Error' issue on the instances page
Fixed an instance status issue in the instance overview panel

Query

Added support for user controlled auto-committing transactions via the :auto command

Explore

Fixed issue where locked Search Phrase did not update with changes to Cypher query
Numerous other bug fixes and enhancements

Import

Added support for composite keys on node IDs

April 8, 2026

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDB Business Critical

Explore

Multiple Explore Scenes

Users of Explore can now store multiple Scenes! Up to 3 Scenes can be saved for a Free Instance, 5 for Pro Instances, while Enterprise Instances benefit from an unlimited number of Scenes.
Note that at this time, Scene data can only be persisted until an Instance is paused.
Additionally, Perspectives and Scenes are now stored online, meaning that they can be accessed from different workstations and web browsers. Limits on the number of Perspectives that can be stored have also been introduced, with Free Instances limited to only the Default Perspective, Pro Instances having up to 5 Perspectives, and no limits on Enterprise Instances. Any existing Perspectives will automatically be migrated to online storage.

April 8, 2026

improved

Neo4j Fleet Manager

Fleet Manager enhancements with Neo4j 2026.03 release

With the general availability of 2026.03, Neo4j is pleased to announce two enhancements to Fleet Manager.
Simpler Setup
The fleet manager plugin is now incorporated in the Neo4j binaries and enabled by default, meaning there is no longer a need to perform plugin setup as part of installing Fleet Manager.
Setup can be achieved directly from the Aura console in three easy steps for deployments running 2026.03 or later:-
Add a self-managed instance to a project in the console
Enter a name and connection URI for the self-managed deployment, and connect to Neo4j
Confirm that fleet manager is ready and click next.
The existing manual installation and registration via the Aura API and CLI is still available. Remember to remove the plugin on 2026.03 or later when upgrading, although Neo4j will still start if the plugin is present. 
Query Log Analyzer for Self-managed Enterprise
Query Log Analyzer for self-managed Enterprise Edition databases in Fleet Manager is now available where Neo4j is running 2026.03 or later.
This is a summary only feature, and aggregate query logs are collected in 10 minute buckets and uploaded to the service. The familiar UI presents the information in the console, with time selection, filters and sorts as with Aura QLA. 
There is no ability to see individual query executions (details) for Fleet Manager; these are available on the self-managed deployment if needed.
To use the feature:- 
Ensure you are running Neo4j Enterprise Edition 2026.03 or later, and have the deployment registered in Fleet Manager
Have Neo4j configured to obfuscate query logs (db.logs.query.obfuscate_literals=true
). This will also affect the local query log files and is to prevent any potential exposure of sensitive data.
Opt-in to use the feature using the console. Choose inspect for the deployment, go to the settings tab and enable Query Log Analyzer.
Once enabled, it can take 10 minutes or more for data to be available in the console.
Documentation is available in the Aura docs for Fleet Manager.

April 2, 2026

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Business Critical

Available for VDC - GraphQL DataAPI

We are pleased to announce availability of GraphQL DataAPIs for our Virtual Dedicated Cloud customers.
At this time, we have re-worked and improved the user interface for all Aura Console users with 
One click generation of GraphQL Type Definitions based on information in your graph
Test Type Definitions. by writing queries / mutations
Next on our list is to allow you to choose the size for your GraphQL DataAPI for your needs. 
As ever, please let us know of any feedback on our GraphQL Discord channel or on GitHub 
Regards
The GraphQL team at Neo4j

March 27, 2026

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura Database March SECOND Release

The Neo4j Aura March SECOND release is now rolling out—starting with AuraDB Free and gradually extending to higher-tier instances.

This second release in March reveals excited new security features and Cypher 25 updates!

🧑🏻‍💻Cypher 25: New Path Modes & Visibility

We’ve added several features to make your queries safer and more transparent:

ACYCLIC Path Mode
: You can now specify that a node cannot be traversed more than once in a pattern match, avoiding loops.
LOAD CSV Progress Tracking
: Use
SHOW TRANSACTIONS
to see real-time progress metrics for ingestion jobs.
GQL Conformance
: We’ve added the
PROPERTY_EXISTS()
function to keep your code aligned with the latest GQL standards.

🚛 Fleet Manager Updates

These apply if you are running Self-managed Neo4j instances, and upgraded the Neo4j version of your instances to 2026.03:

Built-in Fleet Manager
: You won't need a plug-in to use Fleet Manager to manage your Self-managed Neo4j instances on Aura console anymore. It is ready by default.
Query Log Aggregation
: You can now view aggregate query logs directly in the Aura console. Ensure
db.logs.query.obfuscate_literals=true
is set to enable this.

🛠️ Bug and Security Fixes

Updated Jetty to v12.0.33 to resolve CVE-2026-1605.
Fixed a rare bug in the pipelined runtime involving EXISTS subqueries that could cause incorrect intermediate results.
Dynamic lookups now use locking index seeks when required, whereas previously they were vulnerable to constraint violations if used concurrently in a merge context.

For full details of all updates and fixes in this release, please visit: Release Notes: Neo4j Aura Database – March 2026.

March 2, 2026

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura Database March Release

The Neo4j Aura March release is now rolling out—starting with AuraDB Free and gradually extending to higher-tier instances.

🚀 Updates

New organizations created after 4 March default to Cypher 25. If you're an Organization admin, you can toggle the setting as needed.
Vector search with filters (in-index filtering) and the new Cypher
SEARCH
syntax for vector queries are now GA and supported for production use.
GRAPH TYPE
is now available in Preview - It provides you the ability to declare your data model in a single, unified blueprint. This enforces strict data integrity including validation of relationship connections and label definitions without sacrificing the flexibility of an open schema.
Added GQL-compliant aliases for existing Cypher functions.
Added
ai.text.structuredOutput()
function to the GenAI Plugin, taking a textual prompt and map schema and outputting the result as a map adhering to the given schema.

🐞 Bug fixes

Fixed a bug in pipelined runtime where sometimes queries with multiple
SelectOrSemiApply
operators in the query plan could fail.
Fixed a bug where use of a composite property index in combination with a dynamic node label or dynamic relationship type could result in an incorrect
MATCH
result being returned.
Fixed issue with conditional query
WHEN
not aggregating null values correctly without a grouping key.
Fixed a bug with the new MergeUniqueNode operator.

For full details of all updates and fixes in this release, please visit: Release Notes: Neo4j Aura Database – March 2026.

→