LoginSign Up
← Back to all sparks
N

Neo4j

ANALYTICS
Velocity5.0

Neo4j pushes Aura toward operational maturity — concurrency, billing observability, and GQL-standard Cypher.

graph-databaseaura-cloudcypher-25gql-standardsbilling-observabilityconcurrency
◆Current state
Neo4j's recent work is almost entirely about Aura, its managed graph-database cloud. The cadence is a monthly database release advancing Cypher 25 / GQL-standard features, wrapped in a steady stream of platform plumbing: billing APIs and a new billing dashboard, project lifecycle controls, larger adjustable storage on AWS, native graph projections for analytics, and tooling that connects Desktop and a new CLI to Aura. The product is maturing from an engine into a fully operable managed service.
◆Where it's heading
Two threads run in parallel: engine work hardening high-concurrency and analytics workloads (deadlock prevention, native projections), and platform work making Aura easier to run and pay for (billing observability, project deletion/recovery, storage scaling, API-driven automation). GQL standards compliance via Cypher 25 is the connective theme on the language side. The direction is operational depth on the managed cloud, not a new product category.
◆Prediction
Expect the monthly Aura database releases to continue extending Cypher 25 / GQL coverage and concurrency performance, alongside more Aura API surface for automating org, billing, and instance management. The entries point to incremental platform maturation rather than an imminent directional shift.

◆Recent moves

  1. 3d ago

    Aura June release: DISJOINT BY prevents parallel-write deadlocks

    The June Aura release adds DISJOINT BY, a scheduling-time deadlock-prevention mechanism for CALL IN CONCURRENT TRANSACTIONS that resolves lock contention before transactions run — directly targeting the parallel-write and high-concurrency ingestion pain that has long plagued graph merges. A substantive engine improvement delivered through the regular monthly channel.

  2. 4d ago

    Aura Project Deletion now available

    Self-serve project deletion arrives in the Aura Console, with a 30-day recovery window and automatic instance resumption on restore. A practical project-lifecycle gap filled, part of the broader push to make Aura fully self-operable.

  3. 7d ago

    Neo4j Desktop 2.2.0 connects to Aura via the Aura API

    Neo4j Desktop 2.2.0 connects to Aura accounts via the Aura API, easing discovery of orgs, projects, and instances and smoothing migration between local and cloud, plus query-authoring and Bloom/Dashboards fixes. Reinforces the local-to-Aura workflow continuity theme.

  4. 24d ago

    Native projections speed bulk loading in Aura Graph Analytics

    Aura Graph Analytics gains native projections, loading graphs directly from underlying database storage into GDS sessions rather than via query-based approaches — a meaningful performance gain for bulk loading of large graphs. Strengthens the analytics surface on Aura.

  5. 1mo ago

    🚀 New Billing API available

    Two new Aura API endpoints — /usage and /ledger — make billed usage and historical credit balances programmatically extractable, letting teams feed spend data into their own warehouses for tracking and forecasting. Part of the billing-observability thread running through recent releases.

  6. 1mo ago

    🚀 New Billing API in Aura API v2beta1

    A near-duplicate of the same Billing API announcement (/usage and /ledger endpoints in Aura API v2beta1), carrying identical content and timestamp. No additional change beyond the entry already covered.