Neo4j
Home
Feedback
Changelog

Changelog

Follow up on the latest improvements and updates.

RSS

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.

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,
Aura-UserMgMt-Apis
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.

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)
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.

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/

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.

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura May Database Release

The Neo4j Aura May release is rolling out now, starting with AuraDB Free and progressing to higher-tier instances.
It includes Fleet Manager discovery, expanded Cypher 25 GQL compliance, new native string functions, and runtime fixes.
🚀 New Cypher 25 features (GQL standards)
  • Composable SHOW commands: Combine multiple Cypher commands in one query and mix them with other Cypher statements. Supported commands include
    SHOW INDEXES
    ,
    SHOW CONSTRAINTS
    ,
    SHOW FUNCTIONS
    ,
    SHOW PROCEDURES
    ,
    SHOW DATABASES
    , and more.
  • ACYCLIC
    with
    SHORTEST
    and
    ANY
    paths: You can now combine
    ACYCLIC
    with
    ANY
    ,
    SHORTEST
    ,
    ALL SHORTEST
    , and related path selectors.
  • New native string functions:
    string.indexOf
    ,
    string.join
    , and
    string.regexReplace
    are now native Cypher functions. Related
    apoc.text.*
    functions are deprecated.
🛠️ Bug fixes
  • Fixed a network channel concurrency issue that could cause out-of-order messages and slower writes.
  • Disabled a parallel runtime planner behavior that could increase memory use for some variable-length patterns. Re-enable per query with
    CYPHER parallelRepeatHeuristic=enabled
    .
  • Fixed
    COUNT(DISTINCT)
    overcounting in the pipelined runtime.
  • Auth rules with invalid time functions now fail at creation time.
  • Fixed
    stDev()
    returning 0 instead of null for empty input.
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 – May 2026.

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

🚀 New Aura Billing Experience is now available for all customers with a payment method

What’s new?
Managing your organization’s spend just got a lot easier. Starting today,
Organization Admins
and
Owners
will see two new pages under the
Organization Billing
menu:
  • Billing Overview
    : Your new financial dashboard. Get a month-to-date usage snapshot at a glance, featuring a brand-new burndown chart and credit balance tracking for prepaid accounts.
  • Cost Explorer
    : An interactive tool to slice and dice your historical usage. Customize your view with interactive charts and export your data to CSV for deeper analysis.
How to get the most from the new pages
💳 Billing Overview: Your Daily Snapshot
As your new billing landing page, this view gives you an immediate look at current-month consumption and remaining credit balances - no digging required.
🔍 Cost Explorer: Granular Spend Tracking
Understand exactly what is generating costs and when. The
Cost Explorer
aggregates data across all projects and billing accounts in your organization, empowering you to:
  • Analyze spending patterns
    : Track trends over custom timeframes and bucket data by day or month.
  • Pinpoint cost drivers
    : Identify the exact projects, services, resources, or providers driving up your bill.
  • Investigate financial impact
    : Deep-dive into the your resource consumption cost to optimize your budget.
Check out our documentation for more details.

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Tidy Up Your Org with Automated User Pruning 🧹

Keep your security tight and your member list tidy without the manual effort. Our new
Inactive Organization Member Pruning
feature lets you automate the clean-up for users who no longer require access to your Aura Organization.
The Highlights:
  • Set Your Rules: Define a period (
    30
    –
    365
    days) after which inactive members are automatically removed from the Org.
  • Fair Warnings: Aura optionally sends up to
    three email notifications
    to users before they lose access, giving them plenty of time to log back in.
  • Activity Defined: Any action in the Console or via the Aura API resets the inactivity timer.
  • Built-in Safety: We’ll never remove the last Owner or Project Admin, and you can mark specific VIPs as Exempt.
  • Easy Recovery: Users automatically pruned can be re-invited to the org if they need to regain access.
Ready to declutter? Head to the Organization Security page to configure your policy. For further reading, our documentation page on inactive organization member pruning gives additional details.
(Note: This feature is unavailable for organizations using SSO as their exclusive login method. We recommend using the SSO provider's user management tools in these cases)

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:
  1. Log in to the Aura Console using email/password.
  2. Go to Account > Settings > Preferences > Security.
  3. Enable Multi-Factor Authentication (MFA).
  4. 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!

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.
Load More
→