Follow up on the latest improvements and updates.

RSS

September 21, 2026

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.

September 3, 2026

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.

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!

August 30, 2026

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

Neo4j Aura August 2026 Release

The Neo4j Aura August release has recently started to roll out, commencing on AuraDB Free and progressing to higher tiers later.

🚀 New Cypher 25 features

Native UUID Support
: Introduced the new
UUID
type alongside new constructor functions (
uuid()
,
uuid(name :: STRING)
,
uuid(mostSigBits :: INTEGER
,
leastSigBits :: INTEGER
)) and helper functions (
uuid.leastSignificantBits()
,
uuid.mostSignificantBits()
).
String Interpolation
: You can now embed expressions directly within strings using the new literal syntax
s"..."
or
S"..."
(enclosing expressions in
{}
).
List Predicates in PBAC
: Property-based access control rules now allow predicates to check for the presence of a value in a list property (e.g.,
GRANT ... FOR (n) WHERE 'gold' IN n.clearanceLevels TO role
). Property values can also now sit on the right-hand side of predicates (e.g.,
WHERE 1 > n.level
).
Clearer Query Logs
:
LIMIT/SKIP INTEGER
and
LOAD CSV
's
FIELDTERMINATOR STRING
are no longer considered sensitive and will show up unobfuscated in query logs.

🛠️ Bug Fixes

Composite Database Subqueries
: Fixed an issue where passing an outside variable into a
CALL
subquery mistakenly injected it into every
WITH
clause as a grouping key. This previously caused query rejections due to fake memory spikes (OOM errors) and returned empty results instead of a correct count of
0
when no data was found.
Dynamic Property Assignment
: Fixed a bug where dynamic property targets could incorrectly observe earlier assignments in the same
SET
clause (e.g.,
SET n['x'] = n.y, n['y'] = n.x
now correctly swaps values instead of duplicating one).
Math Operations
:
null / 0
now correctly returns
null
instead of raising a division-by-zero error, aligning with the GQL specification.
Subqueries
: Fixed an issue where a lone
USE
was placed inside a
COUNT/EXISTS
subquery expression.

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 – August 2026

August 5, 2026

new

improved

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

Query

AuraDB Business Critical

Query Tabs: A new way to work with your queries

Query now provides tabs, giving you a dedicated space to write, edit, and run Cypher queries you want to persist. The existing stream view is retained for workflows where it is less important to retain your Cypher.
This represents a shift away from editing and invoking saved queries in the stream view, changing a few things about the sidebar, saving, and layout along the way. Here's what's new:
A renewed sidebar
The sidebar is now vertical, and Saved Cypher is now called Queries. Downloading and deleting queries is available via a right-click context menu along with other options such as running the query immediately in the stream view - useful for quick executions of your Cypher.
Save queries from the stream view
Saving a query from the stream view is now triggered via a "Save and open in tab" action. This creates a query straight to a Drafts folder and opens the query in a tab, ready to iterate on. From here you can change the default name and arrange it in your own folder structure.
Create a new query
You can create a new query from scratch by opening a new tab. Newly created tabs start out unsaved, but the moment you rename or edit a query, it's saved automatically to the Drafts folder, so you never lose work.
Editing saved queries
The interaction for editing a query is now as simple as clicking it in the sidebar and iterating on it in the tab. All changes are automatically saved.
Flexible layouts in tabs
Flexible layouts that allow you to place results to the bottom, left, or even have both table and graph views open simultaneously are now reserved for tabs, where you have maximum space to work on your queries.
Quick history, Generate with AI and formatting, wherever you're working
Quick history, Generate with AI and formatting are no longer limited to the main editor. All are now available from anywhere, whether it's a stream frame or a tab.
We want to hear from you!
We hope you enjoy the new tabbed Query experience and we'd love to hear your feedback. Share ideas or report issues at feedback.neo4j.com/query.

August 4, 2026

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura July 2026 Release

The Neo4j Aura July release has started to roll out, commencing on AuraDB Free and progressing to higher tiers later.

🚀 New Cypher 25 features

Introduced the
GROUP BY
subclause to
WITH
and
RETURN
. The
GROUP BY
clause allows the user to explicitly state the grouping keys for an aggregating operation. This is an alternative to the implicit grouping already available in Cypher, and is introduced to better align Cypher with the GQL standard. See Cypher Manual -> Group By
Adds the GQL
cardinality()
function for Cypher 25; it returns the number of keys in a
MAP
, elements in a
LIST
, or nodes and relationships in a
PATH
. See Cypher Manual -> Scalar Functions - Cardinality
Procedure calls that run against the system database can now filter results using the
WHERE
clause. See Operations Manual -> Call a procedure.

Other relevant updates

High-Fidelity Quantized vector search is now generally available. The default index configuration for new indexes is Scalar quantization with an expansion factor of 1.5, existing indexes are unaffected until they're rebuilt. See Vector indexes - Cypher Manual.

🛠️ Bug fixes

Fixed an issue where notification filters set on the driver session were dropped when a query was forwarded via server-side routing, causing suppressed notifications to still be returned to the client.
Fixed an issue where creating a vector index when setting
vector.quantization.enabled
:
false
without
vector.quantization.type
:
'NONE'
in the index configuration.
The backup correctly picks the most recent valid chain when restoring from a folder, which would previously fail if the last backup was an orphaned diff.
Clustering - When the raft prefetch buffer is reset, the size of the buffer is also now reset
Cypher - Fixed a bug where
EXISTS
expression nested in a quantified path pattern would trigger a class cast exception.

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 – July 2026

July 15, 2026

new

AuraDB Virtual Dedicated Cloud

AuraDS Enterprise

AuraDB Business Critical

🎉 New in Aura: Self-Service Single Sign-On (SSO)

Securing your Neo4j Aura environment just got a whole lot easier! We are excited to announce that Single Sign-On (SSO) configuration is now fully self-service, most importantly no support tickets are required
!
What’s new?
Organization Owners and Admins could already integrate Aura with Identity Providers (IdPs) like Okta and Microsoft Entra ID using the OpenID Connect (OIDC) protocol. Now we have enhanced this experience to provide complete, granular control to configure SSO exactly how your team needs it:
Organization-Level SSO
: Centralize authentication and manage how users log in to the Aura Console.
Instance SSO
: Configure login methods specifically for instances within your projects. This includes role mapping which allows per instance configuration to map existing IdP groups to specific database roles, ensuring users automatically get the exact access they need.  Importantly -- this configuration can apply to both new and existing instances!
Take control of your organization's security today. Head over to Organization > Security > Single Sign-On in the Aura console to set up your configuration!
Read the Aura SSO Documentation for more details.

July 3, 2026

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

New Aura User Management APIs

Neo4j is thrilled to introduce the new Aura User Management REST APIs, bringing comprehensive programmatic control to user lifecycle management across both Organization and Project levels!  Previously driven primarily through the Aura Console UI, this new programmatic capability eliminates operational friction for enterprise teams looking to scale efficiently.  We've built this feature specifically to support automated deployments and modern DevOps workflows,
These new APIs allow you to seamlessly integrate Neo4j Aura into your existing Identity and Access Management (IAM) workflows, CI/CD pipelines, and Internal Developer Platforms (IDPs). This unlocks "Zero-Touch" user onboarding, where automated API calls handle provisioning and align with Aura's unified organization-level identity model. 
Refer to the Aura API Specification documentation  for information on using each endpoint and the Aura API Overview documentation for how to access the Aura API.
The Organization-level endpoints, admins can programmatically manage invitations (GET, POST, DELETE /organizations/{org_id}/invites) and oversee the entire user directory: including fetching metadata, adjusting global organization roles, or offboarding users entirely (GET, PATCH, DELETE /organizations/{org_id}/users). 
To support granular access control, Project-level endpoints empower development teams to manage memberships natively within their specific project workloads. You can programmatically list project users, grant access, update project roles, or revoke specific project memberships (GET, POST, PATCH, DELETE /organizations/{org_id}/projects/{project_id}/users). 
This dual-layer framework ensures that project-level access can be granted instantly or cleanly terminated during onboarding and offboarding workflows, eradicating manual entry errors and significantly elevating your security posture. 

June 30, 2026

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura June Database Release

The Neo4j Aura June release has started to roll out, commencing on AuraDB Free and progressing to higher tiers later.

Cypher 25 Features

CALL { ... } IN CONCURRENT TRANSACTIONS
now supports
DISJOINT BY
, a deadlock prevention mechanism that eliminates lock contention in parallel write workloads natively. High concurrency ingestion, particularly when merging nodes with unique constraints or creating relationships, has always been vulnerable to deadlock, as parallel threads compete for the same locks simultaneously.
DISJOINT BY
resolves contention at scheduling time, before any transaction is attempted. See the Cypher Manual → Batch scheduling and deadlock prevention with DISJOINT BY.
GRAPH TYPE
moves from public preview to GA in this release. You can now define, enforce, and validate your graph schema at the database level in production workloads with the stability guarantees that come with a fully supported feature. See the Cypher Manual → Graph types.
Extend
SHOW CURRENT GRAPH TYPE
to be able to return lists of virtual nodes and relationships representing the graph type (similar in format to the output of db.schema.visualization()) instead of the current string representation. To get the graph version of the command, use
SHOW CURRENT GRAPH TYPE AS GRAPH
. See the Cypher Manual → SHOW CURRENT GRAPH TYPE AS GRAPH.
For customers using Change Data Capture (CDC), we have added a
txCommitTime
column to the
db.cdc.current()
procedure. This update allows clients to conveniently identify the commit time of their most recent transaction alongside the transaction identifier.
Vector
SEARCH
queries now support
IN
for filtering, allowing queries like:

MATCH (movie:Movie)
  SEARCH movie IN (
    VECTOR INDEX moviePlots
    FOR $queryVector
    WHERE movie.genre IN ["Horror", "SciFi"]
    LIMIT $topK
  )
RETURN movie.title AS title, movie.rating AS rating

See the Cypher Manual → Predicates for vector search with filters.

Other relevant updates

Preview feature

: an improved vector search that uses our new Hi-Fidelity Quantized Vector Search method. HFQ performs an initial expanded search on the quantized vectors, then re-ranks the results using the full precision vectors. This should make queries faster, reduce memory requirements, and increase recall accuracy when compared to the previous default quantized vector index. HFQ adds the following options to

CREATE VECTOR INDEX

, vector.quantization.type and vector.default_search_expansion_factor.

To try the preview of HFQ:

CREATE VECTOR INDEX moviePlots IF NOT EXISTS
FOR (m:Movie)
ON m.embedding
OPTIONS { indexConfig: {
  `vector.quantization.type`: 'binary',
  `vector.default_search_expansion_factor`: 2.0,
  `vector.dimensions`: 1536,
  `vector.similarity_function`: 'cosine'
}}

HFQ requires an index re-build and is expected to be GA in the next release.

Aura Graph Analytics (AGA)

Native projections are now available in AGA via both Cypher and the GDS Python client.
Project-level Machine Learning model publishing is now supported, automatically granting model access to all members of a project.

Security

Upgraded netty to version
4.2.15.Final
in order to resolve several CVEs.

Bug fixes

Fixed a bug that allowed cached pages to exceed the configured limit.
Fixed a bug where outbound network chunks for secondaries were not flushed properly. This could lead to a buffer overflow in the outbound.
Fixed a bug in the pipelined runtime where an
OR EXISTS
subquery containing ordering could silently drop a result row:

MATCH (c:Customer)
WHERE c.vipStatus = true OR EXISTS { MATCH (c)-[:PLACED]->(o:Order) RETURN o ORDER BY o.total DESC }
RETURN c.name

Fixed a record format bug where undirected scans of multiple relationship types omitted sibling relationships, resulting in a ~50% undercount in the output.
Fixed an issue that let a User Defined Function (UDF) be defined as part of a Property-Based Access Control (PBAC) privilege. This isn't supported and wouldn't have worked as a user might have expected.

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 – June 2026.

June 29, 2026

new

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Aura Graph Analytics

Neo4j Fleet Manager

Aura Project Deletion now available

We are happy to announce that project deletion is now available within the Aura Console for all self serve users.

Required roles:

Project Administrator, Organization Administrator (with Project Administrator role), Organization Owner

Delete a project

Go to Project settings → Delete Project
Select Delete Project
A warning modal appears.
Type the name of the project to confirm, then select Confirm Deletion.

Recover a deleted project

A project can be restored within the 30 day recovery window that begins when the project is deleted. Aura instances will automatically resume. Compute billing will resume once the resources are active.

Go to Organization settings → Recover deleted projects
Locate the project you wish to recover.
Select Restore Project.

See documentation for details: https://neo4j.com/docs/aura/managing-projects/delete-and-restore-projects/

June 1, 2026

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

🚀 New Billing API available

We are excited to announce the general availability of two new Aura API endpoints designed to give you full control over your billing data:

/usage
: Extracts billed usage for a specific period and Aura organization.
/ledger
: Extracts historical credit balances for a specific period and Aura organization.

Automate Your Billing Insights

Say goodbye to manual UI exports. You can now automatically feed your billing data directly into your own data warehouse to:

Track trends over highly customized timeframes.
Isolate costs by identifying the exact projects, services, resources, or providers driving your spend.
Forecast effectively by predicting and acting on credit balance depletion before it impacts your workflows.

Availability

: These endpoints are live today for all paying customers via Aura API v2beta1. Setup instructions can be found in the Aura public documentation.

→