Neo4j
Home
Feedback
Changelog

Changelog

Follow up on the latest improvements and updates.

RSS

new

Neo4j Aura Database - October 2026

Advance notice of upcoming changes
  1. DBMS.Components
Currently,
dbms.components
currently reports 5.27 on Aura regardless of the version actually running your database. After the 2026.12 LTS,
dbms.components
will report the calendar version of the engine actually running your database, for example [2027.01]. Nothing changes in this release.
Who this affects
Any application or integration that reads the value returned by
dbms.components
and depends on its format. This includes the Kafka connector, the Spark connector and GraphQL integrations.
What to do before then
  • Check whether your application parses the value returned by
    dbms.components
    .
  • Update any logic that assumes a 5.x version string so that it accepts a calendar version.
  1. Database Password Requirements
Starting in January, alongside the upgrade of Neo4j AuraDB instances to the 2027.01 release, we are increasing the minimum password length for native database users from
8 characters to 16 characters
.
Why are we making this change?
At Neo4j, we take the security of your data seriously. Password length is one of the most effective tools for keeping accounts secure. This update aligns Neo4j Aura with modern security best practices and recommendations from standards bodies like NIST.
Who is impacted?
For the vast majority of our customers, this change will have no impact and requires no action.
You will
not
be affected by this change if:
  • You use secure 16+ character passwords such as the automatically generated 44-character password issued when an Aura instance is first deployed.
  • You manage user authentication through an external OIDC SSO provider rather than native database users.
What about existing native users?
Existing native database users will
not
be impacted. Your current passwords will continue to work without interruption.
The new 16-character minimum will only be enforced in the following scenarios:
  1. When creating a
    new
    native database user.
  2. When
    changing or resetting the password
    for an existing native database user.
If you have any questions or need assistance adjusting your provisioning scripts to accommodate the new minimum length, please reach out to Neo4j Support.
New features and improvements
Security
  • Dynamic Row-Level Security via ABAC User Tags in PBAC: you can now reference Attribute-Based Access Control (ABAC) user tags inside Property-Based Access Control (PBAC) rules using
    abac.native.user_tags()
    .
This enables a capability similar to dynamic Row-Level Security (RLS) in relational databases by restricting access based on whether an element's property matches the authenticated user's tags.
Example:
GRANT TRAVERSE ON GRAPH *
FOR (n:Project) WHERE n.department IN abac.native.user_tags()
TO projectTeam
Limitation:
Negation unsupported: Unlike standard
IN
expressions, predicates using
abac.native.user_tags()
cannot be negated with
NOT
.
See Operations Manual → Grant a property-based privilege using native user tags and Operations Manual → Negation and DENY with abac.native.user_tags().
🚀 New Cypher Cypher 25 Features
  • Improve the concurrency of
    CALL { ... } IN CONCURRENT TRANSACTIONS DISJOINT BY
    transaction batch scheduling with resource access conflicts between batches.
  • Added a parameter to
    db.schema.visualization()
    to eliminate ghost relationships, at the cost of some performance. See Operations Manual -> Procedures for details.
  • Introduced map addition, allowing maps to be merged using the plus operator;
    RETURN map1 + map2
  • Added the capability to combine
    SHOW CURRENT USER
    command with regular Cypher that can be run against the system database, for example,
    SHOW DATABASES
    and
    SHOW TRANSACTIONS
    . To ensure the command is run against the system database, prepend it with the
    USE
    clause. See Operations Manual - Manage users for details.
🛠️ Bug Fixes
  • Fixed an issue where dividing the minimum 64-bit integer (
    -9223372036854775808
    ) by
    -1
    silently returned an incorrect result due to integer overflow. Cypher now correctly detects this condition and raises an arithmetic overflow error (
    22N28
    ), ensuring consistent overflow handling across integer arithmetic operations.
For full details of all updates and fixes in this release, as well as links to relevant documentation please visit: Release Notes: Neo4j Aura Database – October 2026.

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Business Critical

Larger 5TB Adjustable storage now available on Azure!

AuraDB Business Critical and Virtual Dedicated Cloud customers running on Azure can now configure up to 5TB of storage as standard, directly through the Aura Console or Aura API.
Eligible customers can now provision higher storage capacities for both new and existing AuraDB Business Critical and Virtual Dedicated Cloud instances on Azure, within supported memory-to-storage ratios, for example:
  • 192GB instances now support up to ~3TB of storage
  • 256GB instances now support up to ~4TB of storage
  • 384GB and 512GB instances now support up to ~5TB of storage
image
Building on the adjustable storage capabilities previously introduced, this enhancement gives customers:
  • Even greater flexibility: scale storage based on workload needs without increasing compute
  • Improved cost efficiency: avoid additional compute costs when only more storage is required
  • A smoother experience: configure storage directly without manual processes, custom workarounds, or support requests
For more information on this feature, please read our documentation.

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDB Business Critical

Multiple Databases: now generally available 🎉

We're excited to announce the general availability of Multiple databases for AuraDB Business Critical and Virtual Dedicated Cloud, and we're ready for production!
A huge thank you to everyone who tried it in preview and shared feedback. It shaped what we're shipping today.
One instance, many databases
Run separate, independent databases inside a single AuraDB instance, sharing its compute and memory. No more one instance per use case. It's a lighter way to separate data for different teams, environments, or tenants, all managed from one place.
aura-multidb
What's included at GA
  • Up to 5 databases per GB of RAM, to a maximum of 250 on Virtual Dedicated Cloud and 100 on Business Critical
  • Create and manage databases in the Console or with the Aura API
  • Backup, export, and restore for individual databases
  • Bloom, Query, Import, Dashboards, metrics, and logs all work at database level
  • Works with IP filtering, single sign-on, and private endpoints, depending on tier
Billing is the same as any other AuraDB instance. Usage is charged at the standard GB-hour rate for your instance size and storage configuration, however many databases you run.
Try it today
Create a new AuraDB Business Critical or Virtual Dedicated Cloud instance and enable Multiple databases under Additional settings. Tell us how it goes with the Feedback button in the top right of the Console, or reach out to your Account Manager or Customer Support.
For more information, please see the documentation.

new

Enterprise Studio

Enterprise Studio 2026.09

New in the latest release of Enterprise Studio:
GenAI Copilots for Enterprise Studio
  • Users of Enterprise Studio can now use AI features to generate queries, dashboards, and Bloom graph patterns with natural language.
  • Administrators set up a connection to their own (self-hosted) LLM model using an OpenAI-compatible endpoint.
  • Fully supported and tested for any OpenAI-compatible LLM endpoints - including Gemini, Azure OpenAI & Bedrock models.
Major Updates in Tools
  • Query: Develop Cypher queries using the new tabbed query interface.
  • Query: Added support for visualizing results of multi-statement Cypher queries. 
  • Dashboards: Added support for rule-based styling in tables.
Improvements on operations
  • Enterprise Studio can now be evaluated without a license key.
  • Various improvements to logging and error handling.

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Enterprise

AuraDB Business Critical

Aura Graph Analytics

GDS Python Client 2.0 brings new algorithms and asynchronous execution to Aura Graph Analytics

Version 2.0 of the GDS Python client is out, with multiple upgrades specific to Aura Graph Analytics:
  • Asynchronous execution
    : projections, algorithm runs, and write-backs can now return a handle instead of blocking, so you can trigger a job and check on it later, even from a different process. This makes it much easier to orchestrate AGA jobs from tools like Apache Airflow: one task kicks off a projection or algorithm run, and a separate task polls for completion. See the async execution docs · Read the production pipeline guide
  • HITS and topological link prediction algorithms
    , available via
    gds.hits
    and
    gds.topological_link_prediction
  • Per-algorithm AGA session memory estimation
    :
    GdsSessions.estimate
    now takes an
    algorithms
    parameter, so you can estimate memory for individual algorithms instead of a given category (docs)
  • FastPath
    : the algorithm for turning event sequences into embeddings, announced separately
Heads up — this release also renames the AGA projection methods:
  • gds.graph.project
    is now
    gds.graph.project.cypher
  • gds.graph.project_native
    is now
    gds.graph.project.native
The 1.x to 2.0 migration guide covers all breaking changes, make sure to update your scripts before upgrading.
Note: GDS Python Client 2.0 also updates AuraDS Enterprise and the AuraDB Pro Analytics Plugin; see the full changelog for everything included.

new

Neo4j Aura September 2026 Release

Database
  • The performance of re-scored binary quantization (AKA High Fidelity Quantized vector search) and scalar quantization is significantly improved. A re-scored binary reduces latency by approximately 5x and increases query throughput by 5x. Indexes built before v2026.08 that aren't regularly updated, must be re-created in order to get the full benefit. See Vector indexes - Cypher Manual.
🚀 New Cypher 25 features
  • Cypher now supports native full-text search through the new
    SEARCH
    clause for simple node and relationship patterns. See the Cypher Manual -> Query full-text indexes.
  • The functions
    toString()
    ,
    toStringList()
    and
    toStringOrNull()
    have been updated to accept
    LIST
    ,
    MAP
    ,
    NODE
    ,
    RELATIONSHIP
    and
    PATH
    types. See the Cypher Manual -> String functions.
  • Introduced map comprehension, which allows the creation of a
    MAP
    value by iterating over an existing
    MAP
    or
    LIST
    e.g
    {k: v IN map | keyExpression: valueExpression}
    . See the Cypher Manual -> Map comprehension.
  • Add
    AS COMMANDS
    for
    SHOW USERS
    and
    SHOW ROLES
    , to get a create role/user or grant role to user/auth rule command string that can be executed to recreate the current setup of roles, users and their assignments. See Operations Manual -> Manage users and Manage roles.
  • Add new
    AUTH RULES
    authRule
    filter to
    SHOW PRIVILEGES [AS COMMANDS]
    to filter on privileges assigned to roles granted to the given auth rules, similar to the existing
    USERS
    or
    ROLES
    filters. Also add some useful columns to the
    SHOW PRIVILEGES AS COMMANDS
    to be able to filter the commands on. See Operations Manual -> Role-based access control.
🛠️ Bug fixes
  • The page cache now reserves its full configured memory at startup and is guaranteed never to exceed
    server.memory.pagecache.size
  • $any
    dynamic type evaluation on a list containing invalid elements in the list tail will now correctly throw instead of short-circuit accept on the list head, and the error message now no longer erroneously suggests that
    LIST<LIST<STRING NOT NULL>>
    is an accepted outer list type.
  • A division by zero is now raising a clean division-by-zero arithmetic error instead of a previous overflow/out-of-range
For full details of all updates and fixes in this release, as well as links to relevant documentation please visit: Release Notes: Neo4j Aura Database – September 2026.

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDB Business Critical

Just released: features to help you scale AI to production

Work with data where it lives using
Neo4j Virtual Graph
, now in preview.
Multiple databases
lets you consolidate workloads as individual databases within a single AuraDB instance. And you can now scale configurations up to
2TB of RAM and 5TB
of storage for growing workloads.
aura_features_fan (1)
See what's new!

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDB Business Critical

Aura Graph Analytics

FastPath is now available in Aura Graph Analytics

You can now use FastPath, a new algorithm in Aura Graph Analytics, to turn time-stamped event sequences into embeddings you can search, cluster, or feed into a model. Think customer journeys, patient histories, transaction chains, or clickstreams: anywhere timing changes what an event means. Three failed logins over a month means something very different from three failed logins in five seconds, and FastPath's embeddings capture that difference.
Use it to:
  • Retrieve
    similar journeys by searching FastPath embeddings in a vector index
  • Discover
    behavioral patterns by clustering embeddings across your population
  • Predict
    what happens next by feeding embeddings into downstream models for churn, risk, or anomaly detection
How to use it 🛠️
Call FastPath through the GDS Python Client (version 2.0 and later) or the Cypher API, same as any other GDS algorithm:
  • Python:
gds.fast_path.mutate(
G,
base_node_label="Customer",
event_node_label="Event",
mutate_property="journeyEmbedding",
embedding_dimension=128
)
  • Cypher:
CALL gds.fastPath.mutate('journeyGraph', {
baseNodeLabel: 'Customer',
eventNodeLabel: 'Event',
mutateProperty: 'journeyEmbedding',
embeddingDimension: 128
})
Full details are in the FastPath docs.

new

improved

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

New Console

AuraDB Business Critical

Instance explorer preview

Navigate your instances and databases more easily by trying our new instance explorer.
instance-explorer-preview
  • All your instances in one view (Aura, Virtual Graph, and self-managed)
  • Click an instance or database in the explore view, then see the relevant settings on the right
  • Settings now benefit from much more space, consistently using a full screen display (rather than drawers and sub-screens)
You can try the preview now by clicking the "Switch to instances explorer" button in the top-right of the instances screen. You can switch back at any time.
We hope the new experience is easy to use and makes it simpler to find your instance settings. Please do send us your feedback!

new

🌍 🇬🇧 New region for Aura Professional and Business Critical: AWS London [eu-west-2]

Neo4j Aura Professional and Business Critical are now available in AWS eu-west-2, London.
You can now run Aura Professional and Business Critical workloads in London if your data needs to stay in the UK, or you want lower latency for UK-based workloads.
Get started today in the Aura Console or the Aura API.
Team Aura 🚀
Load More
→