Changelog
Follow up on the latest improvements and updates.
RSS
new
AuraDB Virtual Dedicated Cloud
AuraDB Professional
AuraDB Free
New Console
AuraDB Business Critical
Dark mode now available
You can now access a new theme switcher via your avatar menu in the console's global header. Here you can choose between light, dark, or use your system default.
We really appreciate all the feedback and requests on this feature. We also took some time improve the avatar menu, we hope you like it.
We’re excited to introduce Graph Analytics on AuraDB Professional—bringing the power of Neo4j Graph algorithms to your database without requiring separate infrastructure like AuraDS.
What’s New?
With the Graph Analytics plugin, you can now:
- Run parallelized graph algorithms directly within AuraDB Professional, including centrality, ranking and many others
- Use machine learning pipelines to predict missing relationships
- Enable or disable the plugin as needed for flexibility
How It Works
- Available for AuraDB Professional instances running Neo4j 5+ with at least 4GB memory
- Works across all supported cloud providers and regions
- No additional cost—just enable the plugin and start analyzing!
Key Considerations
- When Graph Analytics is active, memory is shared between analytical and transactional workloads
- Rolling updates clear all projections, and backups do not include projections (unlike AuraDS)
Get Started
- 💡 Already using AuraDB Professional? Try out the Graph Analytics plugin today! Simply enable the Graph Analytics setting when creating an instance or via the Configure menu
- 📖 Check out the documentation for further details.
new
AuraDB Virtual Dedicated Cloud
AuraDB Professional
AuraDB Free
AuraDS Professional
AuraDS Enterprise
AuraDB Business Critical
Neo4j Aura Database January 2025 Release Update
The Neo4j Aura January release has started to roll out, commencing on AuraDB Free and progressing to higher tiers later. This is our first release using our new Calendar Version scheme.
Some highlights include:
- Index Creation: Default index provider is now always used, as index providers no longer control index behavior (since version 5.0).
- Protocol Update: Introduced Bolt 5.8.
Fixes
- Resolved double-indexing of dense relationships, detectable during consistency checks.
- Fixed issues with removing the last indexed property from dense relationships, which could fail during recovery or clustering.
- Addressed transaction safety in DDL operations.
- Corrected warnings related to Java Compressed Object Pointers in 32-48GB heaps.
- Fixed a collect function bug that failed to preserve order in specific cases under parallel runtime.
Please refer to the Aura Release notes for more information on the changes.
new
AuraDB Virtual Dedicated Cloud
AuraDB Professional
AuraDB Free
AuraDS Professional
AuraDS Enterprise
AuraDB Business Critical
Aura API rate limiting January update - extension
On 4 December 2024 we advised everyone that, starting 27 Jan 2025, we will adjust the rate limiting for the Aura API /oauth/token endpoint, which is used to obtain authorization tokens.
We will be delaying this change by approximately 30 days to ensure that all Aura API users have sufficient time to implement the necessary updates
Since each authorization token remains valid for one hour, we recommend optimizing your API usage by following these steps:
- 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.
- 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.
Rate limiting for other API 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
Important Update: Calendar Versioning & Cypher 25
Calendar Versioning
Starting in January 2025, Neo4j is adopting a calendar-based versioning format (e.g., 2025.01), replacing traditional semantic versioning after the release of version 5 LTS. As an Aura customer, you’re already automatically on the latest version, and will now see the latest Calendar version in your database details. No action is required as a result of this message.
There is no change for customers using version 4; however, we advise migrating to the latest version to take advantage of great new features, such as Parallel Runtime for 10x faster query performance, Block Format, Differential Backups, and more.
Cypher 5 and Cypher 25: More Choice, Same Simplicity
When an Aura instance is upgraded to the latest version, Cypher Language Version 5, the Cypher Language in Neo4j 5.x, remains the default. When Cypher Version 25 is released this year, it will be available in all database instances on the latest release. All Aura customers on latest Calendar Version will be able to optionally:
- Choose between Cypher 5 or Cypher 25 for queries, regardless of the database version.
- Explore new Cypher features without altering your existing applications.
- Change the default version of Cypher for the database.
The Cypher API compatibility layer ensures seamless transitions and lets you adopt new capabilities at your pace.
These enhancements will roll out soon, keeping Aura at the forefront of graph database technology.
Thank you
The Neo4j Team
FAQ
What is calendar-based versioning, and why is it being introduced?
Calendar-based versioning replaces traditional semantic versioning. Future Neo4j releases will follow the format of YYYY.MM.Patch (e.g., 2025.01.00). This approach simplifies how Aura handles Fully Managed upgrades, ensuring frequent access to new features, and eliminating the need for disruptive major version migrations. More details on why calendar-based versioning is being introduced are provided in the blog post, Neo4j Takes the Lead: Transforming Graph Database Management With Cypher API Versioning and Database Calendar Versioning.
Are there any changes to how upgrades work?
No. Aura does not have any scheduled maintenance windows. It is designed to be always on and available, with all corrections, fixes, and upgrades automatically applied in the background.
Releases for the Neo4j database are also deployed when they become available. Operations are non-disruptive, and you shouldn’t experience any downtime as a result.
Will this change impact me as an Aura API user?
The Aura API will continue to accept version 5 requests. Requests using version 5 will create instances with the Latest Calendar Version.
What about deprecation of features?
Neo4j has a customer-focused deprecation policy: Features will only be deprecated if an alternative is available. Deprecated features remain supported with at least 12 months’ notice before removal.
How will the Cypher API compatibility layer help?
The compatibility layer allows you to specify the default Cypher version for your database or individual queries. This ensures that adopting new Cypher versions like 25 can happen gradually, without disrupting existing applications or workflows.
Do I need to migrate my queries from Cypher 5 to Cypher 25?
Eventually, but Cypher 5 will be supported unchanged (apart from resolving defects and security issues) for several years. We are committed to at least a year's notice before any withdrawal of a Cypher version. Cypher 25 starts as a copy of Cypher 5, with some deprecated features removed. It will then get additive features in the coming years.
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
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:
- 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.
- Impossible Travel:If your login location changes so drastically that it suggests “impossible travel” (beyond what’s realistically achievable), an MFA prompt is triggered.
- 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.
Load More
→