Changelog

Follow up on the latest improvements and updates.

RSS

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Business Critical

New Aura CLI now available!

The Neo4j Labs CLI for Aura has now graduated from Beta! As part of this milestone, the CLI has been completely rewritten in Go, now offered as a single binary executable for Linux, macOS, and Windows. This eliminates external dependencies, making it simpler than ever to integrate into CI/CD workflows, scripts, or everyday terminal tasks.
While the earlier Neo4j Labs CLI remains available for installation for now, we strongly encourage you to transition to the new aura-cli at your earliest convenience. Please note that the Labs Aura CLI repository will soon be set to read-only.
You can download the new Aura CLI here:
Best regards,
Jon Giffard
Snr Product Manager, Neo4j

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Business Critical

Introducing the Beta for GraphQL on Neo4j AuraDB!

We’re thrilled to announce the beta launch of GraphQL for Neo4j AuraDB, enabling customers to seamlessly harness the power of GraphQL with AuraDB.
The beta program is open to all Aura users and will run until just before the General Availability (GA) release, expected by the end of this quarter.
Explore the beta with our comprehensive documentation here: Neo4j GraphQL Aura Documentation.
We value your feedback! Share your insights, report issues, or suggest improvements via the #graphql channel on our Discord Community or our forums. Your input will help us shape the product to better meet your needs.
Regards
Jon Giffard and The Neo4j GraphQL Team

new

AuraDB Professional

AuraDB Business Critical

Aura regional expansion | India 🇮🇳

AuraDB Professional & AuraDB Business Critical are now available in India, across all 3 major public cloud providers.
From today, AuraDB users can launch instances in the following regions:
GCP
  • Mumbai | asia-south1
AWS
  • Mumbai | ap-south-1
Azure
  • Pune | centralindia
______________________________
AuraDB Professional & AuraDB Business Critical are now available across 25 regions in total:
AWS
- ap-south-1 [new]
- ap-southeast-1
- eu-west-1
- eu-west-3
- sa-east-1
- us-east-1
- us-west-2
Azure
- centralindia [new]
- brazilsouth
- eastus
- francecentral
- koreacentral
- uksouth
- westus3
GCP
- asia-south1 [new]
- asia-east1
- asia-east2
- asia-southeast1
- australia-southeast1
- europe-west1
- europe-west2
- europe-west3
- us-central1
- us-east1
- us-west1
If you need to run AuraDB Professional or AuraDB Business Critical in region that isn’t listed here, please let us know!
Team Aura 🇮🇳 🚀

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

New Console

AuraDB Business Critical

Unlock the Potential of Vector Search with Neo4j Aura

We’re excited to introduce a new memory-optimized configuration for Neo4j Aura, purpose-built to enhance vector search. This latest update is designed to help you fast, efficient query results, with even larger datasets.
What’s new?
Neo4j Aura now offers an optional configuration that reallocates memory to prioritize your vector index, enabling:
  • More data, same performance:
    Load up to twice as much data without compromising query speed.
  • Smaller instance, same capability:
    Achieve consistent performance with a smaller instance size.
Whether you're looking to scale your dataset or improve efficiency, this configuration ensures your vector search needs are met with reliable performance and flexibility.
Why it matters
Performance in vector search relies on memory availability for indexing. By reserving additional memory for the vector index, Neo4j Aura helps you navigate the performance challenges associated with large datasets. Early testing has shown steady performance up to the point there’s simply no more storage available on disk for more vectors.
Getting started
The vector-optimized configuration is now available for instances with 4GB or more of memory. Switching to this option is as simple as editing the configuration of your existing instance, or setting it when creating a new instance
Monosnap customer-support (Channel) - Neo4j, Inc
P.S. Curious about the technical details? Dive deeper into how vector-optimized configurations work and the benefits they unlock here

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Adaptive Email MFA enabled for all Aura customers

We’re pleased to introduce Adaptive Email MFA—a new security feature designed to enhance account protection across all Neo4j Aura tiers (Free, Professional, Business Critical, and Virtual Dedicated Cloud). Adaptive MFA challenges you with a second factor of authentication only when it detects unusual sign-in activity, ensuring a more seamless experience without compromising on security.
Key Benefits
  • Increased Baseline Security:
    Adaptive MFA continuously evaluates the risk of login attempts, providing an additional layer of protection against unauthorized access.
  • Reduced MFA Prompts:
    For day-to-day logins from familiar devices and locations, you’ll see fewer MFA challenges, resulting in a smoother login process.
  • Applies to All Aura Tiers:
    This improvement benefits every Aura user, maintaining a consistent level of security across all service levels.
How Adaptive MFA Works
Adaptive MFA monitors multiple factors to determine if a login attempt warrants an MFA challenge, some of which include:
  1. New Device:
    If you log in using a device you haven’t used in the last 30 days, the system lowers its confidence score and triggers an MFA prompt.
  2. Impossible Travel:
    If your login location changes so drastically that it suggests “impossible travel” (beyond what’s realistically achievable), an MFA prompt is triggered.
  3. Untrusted IP:
    If your IP address is flagged as untrustworthy, you’ll be asked to complete an MFA challenge.
Who Is Affected
Adaptive MFA applies to all users who log in to Neo4j Aura with a username and password. If you typically access Aura from the same device, browser, and location, you’ll rarely encounter additional MFA challenges.
No Action Required
This feature is non-disruptive and will be enabled automatically. Users do not need to take any steps to benefit from enhanced security and a more convenient login experience.
For more information or assistance, please contact our support team. We’re committed to keeping your Neo4j Aura environment secure and easy to use.

new

improved

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Aura CLI - open beta

I’m pleased to announce the open beta for the new, Go-based Aura CLI.
You can find it here: https://github.com/neo4j/cli/releases, with native binaries available for all major platforms.
Feedback is welcome via the GitHub issue page here: https://github.com/neo4j/cli/issues.
The Aura CLI will replace the Labs Aura CLI and offers equivalent functionality, with the addition of commands for customer-managed keys (CMK).
The open beta will run for a short period before GA at the end of December 2024. At that time, the Labs Aura CLI will become read-only and marked as deprecated. It will still be installable and usable, but you are advised to transition to the new Aura CLI.
Thank you, and I look forward to your feedback!
Jonathan Giffard
PM, Drivers, CLI, GraphQL & Query API
We are updating all AuraDS users about an upcoming change to the snapshot retention policy for Neo4j AuraDS instances.
Effective from
13 January 2025
onwards, new and existing user-initiated ‘on-demand’ snapshots will now be retained for
30 days
from the date of creation.
What is an AuraDS snapshot?
A snapshot is a copy of the data in your instance at a specific point in time. They are listed in the
Snapshots
tab of the AuraDS instance. Neo4j regularly takes snapshots of your AuraDS instance, and you can request a snapshot to be taken on-demand.
What is changing?
We currently retain AuraDS user-initiated 'on-demand' snapshots for 180 days. From after 13 January 2025 we will retain these for 30 days, and this will be applicable for both newly created and existing user-initiated snapshots.
Why is it changing?
To better align with AuraDB and ensure consistency across our Aura Tiers, we are refining our backup retention policy to establish a standard approach.
Will there be any changes to scheduled snapshots?
The retention period for scheduled snapshots is currently 7 days and will remain unchanged at this time.
Who can I contact for more information?
If you have any further questions, please don’t hesitate to reach out to our support team.
Thanks
The Aura Team
We are updating all AuraDS Enterprise users about an upcoming change to the snapshot retention policy for Neo4j AuraDS Enterprise instances.
Effective from
13 January 2025
onwards, new and existing user-initiated ‘on-demand’ snapshots will now be retained for
90 days
from the date of creation.
What is a Neo4j AuraDS snapshot?
A snapshot is a copy of the data in your instance at a specific point in time. They are listed in the
Snapshots
tab of the AuraDS Enterprise instance. Neo4j regularly takes snapshots of your AuraDS Enterprise instance, and you can request a snapshot to be taken on-demand.
What is changing?
We currently retain AuraDS Enterprise user-initiated 'on-demand' snapshots for 180 days. From after 13 January 2025 we will retain these for 90 days, and this will be applicable for both newly created and existing user-initiated snapshots.
Why is it changing?
To better align with AuraDB and ensure consistency across our Aura Tiers, we are refining our backup retention policy to establish a standard approach.
Will there be any changes to scheduled snapshots?
The retention period for scheduled snapshots is currently 14 days and will remain unchanged at this time.
Who can I contact for more information?
If you have any further questions, please don’t hesitate to reach out to our support team.
Thanks
The Aura Team

new

Advanced Warning Aura Platform

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Aura API rate limiting update!

We currently set a global rate limit of
125 requests per minute
per client ID for all Aura API endpoints.
Starting 27 Jan 2025, we will adjust the rate limiting for the Aura API /oauth/token endpoint, which is used to obtain authorization tokens. The new limit will be set to
15 requests per hour
.
Since each authorization token remains valid for one hour, we recommend optimizing your API usage in advance by following these steps:
  1. Retrieve the token once per hour
    : As tokens remain valid for an hour, reduce the frequency of token requests and reuse the same token for multiple API calls.
  2. Implement token caching
    : Store the token securely within your system to reuse it for subsequent requests during its validity period, minimizing unnecessary calls to the endpoint.
If you need additional guidance or help, please reach out to Neo4j Aura Support. Our priority is to ensure fair and equitable access to our APIs for all customers.
We will provide confirmation of this update in January, along with a link to the relevant documentation. Rate limiting for other endpoints will remain unchanged at this time.
Thank you,
The Aura Team

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura Database December release update!

The latest Neo4j Aura Database release has started to roll out, beginning on AuraDB Free, then progressing to higher tiers from later this week.
Updates include:
Language
  • Added support for dynamic expressions in
    CREATE
    ,
    MATCH
    , and
    MERGE
    .
  • Enabled dynamic CSV column referencing in
    LOAD CSV
    .
  • Deprecated HTTP API; use Query API for executing Cypher statements.
Fixes
  • Kernel: Fixed issues with dense relationship property removal during recovery.
  • Cypher: Fixed missing nodes in queries with indexes and null properties.
  • Cypher: Resolved errors: key not found: VariableSlotKey and Type mismatch.
Full details of updates and fixes are available in the Neo4j Aura Release Notes
Load More