Free audit

View Audit Scope
Neo4jRemote DBA, support, and scoped projects

Neo4j database services for production teams.

JusDB provides Neo4j database services for scoped projects, ongoing remote DBA coverage, production support, Cypher tuning, clustering, upgrades, and migrations. Our engineers work on Neo4j AuraDB and on self-managed Neo4j on your own servers, AWS, Azure, Google Cloud, or Kubernetes. 24x7 on-call is available under your service agreement.

Or request a free audit of one database instance. Already in an incident? See how incidents are handled.

  • NDA before access
  • Read-only by default
  • Changes measured against your baseline

Neo4j version status

Pick the version you run

Neo4j 2026.10

Newest

The newest monthly release, 2026.10.1, came out on 23 October 2026; on this line, fixes ship only in the newest release.

Neo4j plans its next LTS for November 2026, the last release with the standard and High_limit store formats, so those databases need migrating first.

Plan the store format move

Version status from the Neo4j release notes, the 5.26 LTS announcement, the upgrade and migration guide, and the store formats page, checked 28 October 2026.

Platforms
Neo4j AuraDB, AWS, Azure, Google Cloud, your own servers, and Kubernetes
High availability
Autonomous clustering: Raft-replicated primaries, read secondaries, and multi-zone AuraDB Business Critical
Incidents
Initial-response targets are set in your service agreement. See the targets

Symptoms

Eight Neo4j problems we are asked to fix

Each one has a cause we can measure. The scoping call starts from your symptom, version, and edition.

  1. Queries slow down as the graph grows because data and native indexes outgrow the page cache (server.memory.pagecache.size), so traversals read from disk.

  2. A few hub nodes make traversals crawl because a node with millions of relationships, such as a shared device, multiplies the rows at every hop.

  3. A path query runs for minutes, then fails on memory because a variable-length pattern has no upper bound, so the paths it explores grow exponentially with the graph.

  4. EXPLAIN shows NodeByLabelScan or CartesianProduct because no index or constraint anchors the pattern, or two disconnected MATCH patterns multiply each other's rows.

  5. Garbage-collection pauses stall every query because growing the heap forces a full collection, or an oversized heap lengthens old-generation pauses.

  6. Graph Data Science jobs slow down transactions because GDS shares servers with primaries, while Neo4j advises a secondary-only server outside leader elections.

  7. The move off 4.4 keeps slipping after long-term support ended on 30 November 2025, because each database must move to 5.26 LTS with its BTREE indexes replaced.

  8. Bolt connections travel unencrypted because server.bolt.tls_level defaults to DISABLED, and the query log records query parameters by default.

If one of these is costing your team time, a scoping call is the place to start.

Book a 30-min scoping call (opens Google Calendar in a new tab)

Failover

How a zone outage can stop Neo4j writes

A Neo4j cluster commits a write only after a majority of that database's primaries have it. If one zone holds most of those primaries, losing that zone leaves no majority, and the database becomes read-only.

Three primaries, one zone outage, three outcomes

Choose a state to see where the writer is.

What the application sees

Drivers on neo4j:// send writes to the writer and reads to the other servers.

Writes on the writer
  • Primary 1, zone A

    Writer (Raft leader): orders every commit

    Writer

  • Primary 2, zone A

    Follower: holds each commit

    Following

  • Primary 3, zone B

    Follower: holds each commit, serves reads

    Following

A commit is acknowledged once two of three primaries have it, so any one server can fail. But two of the three sit in zone A.

Three primaries tolerate one failed server and five tolerate two, so we spread them until no zone or data center holds a majority. Each extra primary is one more server every write contacts, which can raise latency. Applications connect with neo4j://, because bolt:// ties a driver to one server with no routing.

We alert on Raft term changes (cluster.raft.term), on members whose transaction.last_committed_tx_id stops rising, and on server health in SHOW SERVERS. On a staging copy, we stop one zone's servers, time the write pause, and confirm the application retries in managed transactions. A lost writer is detected within 20 to 23 seconds by default (dbms.cluster.raft.leader_failure_detection_window).

What we cover

Full-spectrum Neo4j engineering

From one slow traversal to a lost zone, query plans and Neo4j metrics drive every change.

  • Cypher query tuning

    We read the plans of your slowest Cypher before changing anything.

    • Plans read with EXPLAIN, then PROFILE on a copy
    • Indexes and constraints that anchor each pattern
    • Bounded path patterns and batched writes (CALL { } IN TRANSACTIONS)
    Database performance tuning
  • Native graph storage

    Memory and store settings sized from your graph, not from startup defaults.

    • Page cache sized to data and native indexes
    • Initial and maximum heap set to the same value
    • Moves to block format with neo4j-admin database migrate
    Store format migration
  • Autonomous clustering

    Primaries placed so one failure cannot take the write majority, then drilled.

    • Three or five primaries spread across zones
    • Secondaries for reads, with bookmarks where reads must see recent writes
    • Failover and restore drills, timed on a copy
    High availability
  • Graph Data Science (GDS)

    PageRank, Louvain, and Node Similarity for fraud rings and recommendations, kept off your transactional servers.

    • Memory checked with .estimate before each run
    • GDS on a secondary-only server in a cluster
    • Community Edition limits weighed against an Enterprise license
    Graph Data Science planning
  • Knowledge graphs

    Vector search and graph traversal in one database, so retrieval can follow relationships (GraphRAG).

    • Vector indexes queried with the SEARCH clause in Cypher 25
    • OS memory left free for vector indexes
    • Entity models designed around the questions you ask
  • AuraDB cloud operations

    Tier choice, snapshots, and restores on Neo4j's managed service.

    • Professional, Business Critical, or Virtual Dedicated Cloud
    • Snapshot schedules checked and restores tested
    • Uploads with neo4j-admin database upload, from 5.26.7 or 2025.04 onward
    AuraDB or self-managed

Incident support

A critical (P1) page, answered within your agreement's target

JusDB keeps your recovery procedures (runbooks) written down, so an incident starts from a known plan instead of a blank page.

Initial-response targets

  • 2 to 4 hours

    Business hours

    During covered business hours

  • 15 minutes

    24x7 on-call

    P1 incidents

P1 · Critical15 minutes

Production database down, primary unreachable, data corruption risk, or active failover event.

P2 · High30 minutes

Severe latency spike, replication lag climbing rapidly, connection exhaustion, or degraded HA node.

P3 · Medium60 minutes

Non-critical slow query regression, staging issue, backup warning, or replication check alert.

P4 · Low90 minutes

Configuration question, index advisory, planned schema review, or general operational request.

Our engineering team is in India; business-hours coverage is Mon–Fri 09:00–18:00 IST (UTC+5:30), and 24x7 on-call is available under your service agreement.

Initial-response targets, not resolution guarantees. The target for your engagement is set in your service agreement.

What happens on a P1 page

  1. Page

    You page the on-call engineer

    Through the escalation path your service agreement names.

  2. Triage

    Root cause from the query log and SHOW TRANSACTIONS

    Runaway traversals, heap pressure, page faults, and leader changes traced to the query or server behind them.

  3. Mitigate

    Stabilize first, from the runbook

    Terminate the runaway transaction, cap memory per transaction, or shed load, then fix the cause once production is steady.

  4. After

    A review after every P1

    What happened, why, and the change that stops it happening again.

Before and between incidents

  • Your setup, written down firstDuring onboarding we record your versions, editions, topology, store formats, memory settings, and backups, so an incident starts with context.
  • One escalation path, in writingYour service agreement names how to reach the on-call engineer, in which hours, and who approves stopping a database.
  • Reviews between incidentsWe review slow queries, page cache hit ratio, garbage collection, cluster health, and backups, and report open risks with next steps.
  • Version dates trackedWe track the 5.26 LTS support date, the next LTS, and the store formats dropped after it, and plan upgrades before support ends.

Process

How a Neo4j engagement runs, step by step

Written findings come before any change. Your team approves production changes, except routine actions you have pre-approved.

  1. Scoping call

    Your Neo4j servers or Aura instances, versions, editions, and what you need covered.

  2. Read-only review under NDA

    Our engineers use named accounts with only the permissions the review needs, then read your neo4j.conf, query log, metrics, SHOW SERVERS output, and EXPLAIN plans (which do not run the query).

  3. A written report before any change

    Each finding comes with the change we propose, how we will measure it, and a way to undo it (a rollback plan).

  4. Changes, then handover

    We rehearse risky changes, such as a store format migration, on a restored copy. Then we apply them in approved windows, measure them against the baseline, and hand over updated operating instructions (runbooks).

Ways to work

Choose the Neo4j service your team needs

Start with the responsibility you need covered. Each engagement has its own scope, deliverables, access requirements, and acceptance criteria.

Where your Neo4j runs, and the tools around it

Your team and ours

What a managed Neo4j service still leaves to your team

Managed cloud databases automate much of the infrastructure layer, but your team still owns query performance, capacity, cost, and incident decisions.

Who handles each part of running Neo4j on AuraDB and on your own servers or Kubernetes
QuestionManaged cloud serviceYour own servers or Kubernetes
Servers, storage, and patchesNeo4j runs them.Your team, or JusDB under your agreement.
VersionsAura always runs the latest server version, so there is no LTS to stay on.Monthly releases, or 5.26 LTS until June 2028. Neo4j does not support downgrades.
Backups and restoresScheduled snapshots, set by tier. Testing a restore is still your team's job.Your team runs neo4j-admin database backup (Enterprise Edition) and keeps the chain a point-in-time restore needs.
FailoverNeo4j runs it; Business Critical spans zones, and Professional runs in one zone.You place primaries and secondaries across zones, and Raft elects the writer.
Cypher, graph model, and indexesYours. Neo4j runs the service, not your queries or model.Yours.
Moving off laterExportable snapshots download as .backup files, so your team keeps a copy.Dumps and backups restore on another Neo4j server, or upload to Aura from 5.26.7 or 2025.04 onward.

Your team keeps control

  • Set business priorities, application requirements, and release plans
  • Approve production changes, except routine actions you have pre-approved
  • Own your cloud accounts, access policies, and vendor relationships
  • Decide when maintenance can happen and how quickly service must recover
  • Move the work in-house or to another provider after your agreement's notice period, with your data returned or deleted and the transition help your agreement sets out (Terms, section 8)

JusDB handles the agreed database work

  • Monitor database health, investigate alerts, and involve the right people
  • Review query performance, replication, capacity, and backup health
  • Carry out approved changes and update the operating instructions they affect
  • Report completed work, open risks, and recommended next steps

Weighing AuraDB against running Neo4j yourself? We compare both against your workload on a scoping call.

Book a 30-min scoping call (opens Google Calendar in a new tab)

Further reading

Neo4j use cases, recursive SQL, and choosing a database

Use cases and Cypher patterns, recursive SQL, and where graph databases fit.

FAQ

Common Neo4j questions

What buyers ask about fit, Cypher, AuraDB, GDS, alternatives, and licensing.

Still have a question?

Ask it on a scoping call. No production access needed.

Book a 30-min scoping call (opens Google Calendar in a new tab)

What is Neo4j and when does it fit?

JusDB runs and tunes Neo4j, a native graph database of nodes, relationships, and properties, with ACID transactions in both editions. It fits questions that follow relationships several hops deep, such as fraud rings and recommendations. For shallow hierarchies, recursive SQL in PostgreSQL (WITH RECURSIVE) is often simpler.

Cypher vs SQL: when is the graph query language worth it?

JusDB recommends Cypher when queries follow relationships of varying depth: one MATCH pattern describes a path of one to many hops, where SQL needs a recursive common table expression (WITH RECURSIVE). Cypher also covers most mandatory features of GQL, the ISO graph query language (ISO/IEC 39075:2024). For joins and aggregates, SQL stays the better fit.

Neo4j AuraDB vs self-managed: how to decide?

JusDB compares both against your workload on a scoping call. AuraDB has Free, Professional, Business Critical, and Virtual Dedicated Cloud tiers and always runs the latest server version, without composite databases or neo4j-admin database backup. Self-managed Neo4j can stay on 5.26 LTS. Uploading a database into Aura needs 5.26.7 or later, or 2025.04 or later.

What about Graph Data Science (GDS) library?

JusDB sizes and places Graph Data Science (GDS), Neo4j's plugin of parallel graph algorithms such as PageRank and Louvain. GDS loads graph projections onto the Java heap, so we check each job with .estimate first. GDS Community Edition stops at 4 CPU cores and 3 models in its model catalog; Enterprise needs a license key.

Neo4j vs alternatives: ArangoDB, JanusGraph, Amazon Neptune?

JusDB compares graph databases against your queries, scale, and cloud. Amazon Neptune is a managed AWS service queried with Gremlin, openCypher, or SPARQL. JanusGraph, open source under Apache 2, uses Gremlin and stores graphs too large for one machine in backends such as Apache Cassandra or HBase. ArangoDB queries documents and graphs with one language, AQL. Neo4j's sharded edition is Infinigraph, a separate subscription.

License: what is the GPL vs commercial situation?

JusDB can explain the split; your legal team should confirm the terms. Neo4j Community Edition is open source under GPLv3, for single servers. Enterprise Edition is commercial, under the Neo4j Software Agreement, and adds clustering, online backup and restore, multiple databases, role-based access control, and block format. GDS Enterprise needs its own license key.

Next step

Talk to a Neo4j engineer about your databases

Tell us what is slow, fragile, or due to change. The first 30-minute call covers your databases, current ownership, and required coverage. No production access is needed. Or request a free audit of one database instance, subject to availability: mutual NDA before read-only access, a prioritized report within one week after access is ready, and no obligation.

NDA before access, read-only by default, and written scope first