Neo4j Support and Consulting

Neo4j Support and Consulting for Clusters, Query Tuning and Upgrades

AceMQ supports and consults on self-managed Neo4j: Enterprise clusters, single servers and Kubernetes deployments, 24/7, alongside your Neo4j subscription or without one. Calls usually start with one of three problems: a query that scans the whole graph, a page cache and heap sized by habit, or a cluster whose leader keeps changing. We also plan the upgrades.

A senior engineer, not an SDR. No sales sequence attached.

Fastest response target, by plan
15 min
On-call cover
24/7
AceMQ customers
160+
Years in business
10+

Without a rewrite of the graph model or a move to another databaseFor production incident cover, see AceMQ Neo4j 24/7 support.

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

The Problem

Why teams call us about Neo4j

Eight Neo4j problems an AceMQ review starts from, a query that scans the whole graph and a cluster that keeps changing leader. If one describes your week, that is where the review starts.

  1. 01

    A Cypher query that was fast on test data takes minutes in production

  2. 02

    Latency spikes and long pauses under load, with heap and page cache sized by habit

  3. 03

    Transactions pile up or time out behind a few dense nodes

  4. 04

    The cluster elects a new leader repeatedly and nobody knows why

  5. 05

    Disk fills with transaction logs

  6. 06

    Backups exist but nobody has restored one

  7. 07

    An upgrade keeps slipping because the version path and the Cypher version are unmapped

  8. 08

    Bulk loads take days

A good fit if Neo4j sits behind a business-critical application and you want one team that answers at night, reads your query plans and plans the next upgrade.

Not a fit for small teams with non-critical workloads. AceMQ is not a budget consultancy: we work with enterprises running business-critical and compliance-heavy Neo4j.

Running Neo4j in production? Get a quote from a senior engineer, answered within one hour.

Contact Us

How it breaks, and the fix

What happens to a Neo4j query when the graph outgrows the page cache?

Neo4j serves reads from its page cache, which holds pages of the store files in memory. When the graph grows past what the page cache was sized for, queries that used to run from memory start reading from disk, and latency climbs for every query that touches the cold part.

Graph outgrows the page cache

One query, the page cache, the hot part of the graph and the store on disk

Illustrative
  1. The page cache holds the part of the graph the queries touch. Reads come from memory and only genuine misses go to disk.

  2. The store grew and the page cache was sized by habit. The hot part of the graph no longer stays in memory, reads fall through to disk and latency climbs.

  3. Heap and page cache are set from the measured store size, so the hot part of the graph stays in the page cache and reads return to memory speed.

Neo4j can calculate a starting point: its memory recommendation tool takes the machine's memory and suggests heap and page cache settings, and the operations manual documents the page cache default as a share of the memory left after the heap. The review then checks the settings against the real store size, garbage collection pauses and the queries that touch the most pages, because a missing index can turn a cheap read into a scan that evicts everything else.

Our Services

Neo4j Consulting & Support

AceMQ runs five Neo4j service lines: health check, query and model tuning, upgrade planning, cluster design, and backup and recovery. A senior engineer leads each one, and any of them can roll into 24/7 support with response targets from 15 minutes, by plan.

  • 01

    Neo4j Health Check

    The fixed-scope entry engagement: a written report on how your Neo4j is configured and where it is exposed, which your team can act on with or without AceMQ.

    • Heap and page cache against the store size
    • The slowest queries with their plans
    • Index and constraint coverage
    • Cluster state, backup and a tested restore
  • 02

    Query and Model Tuning

    Plan analysis of the queries that matter, and model changes that remove dense nodes, measured before and after.

    • PROFILE output read for scans and row explosions
    • Index and constraint design
    • Dense-node and relationship model review
    • Measured before and after
  • 03

    Upgrade Planning

    A written upgrade path from your version to the target, rehearsed on a copy of the store before production.

    • Version path across Neo4j's calendar releases
    • Cypher 5 to Cypher 25 impact on your queries
    • Plugin compatibility
    • A rolling upgrade, one server at a time, with a rollback
  • 04

    Cluster Design

    Primaries and secondaries placed across failure zones, with failure drills and read scaling.

    • Primary and secondary layout
    • Placement across zones
    • Leader-election and failure drills
    • Read scaling with secondaries
  • 05

    Backup and Recovery

    Backup schedules that have been restored, not just taken.

    • neo4j-admin backup schedule and chain
    • A timed restore on a clean server
    • Transaction log retention against the backup cadence
    • A written recovery runbook
  • Response targets from 15 minutes, by plan

    24/7 Neo4j Support

    Senior engineers briefed on your environment, response targets from 15 minutes, by plan, and no ticket routing.

    • Response targets from 15 minutes, by plan
    • Senior engineers, no first-line triage layer
    • Proactive CVE & health monitoring
    • Quarterly deployment reviews

Want AceMQ to take this off your team's plate? Tell us about your Neo4j estate.

Contact Us

24/7 Support

Neo4j Support When It Matters Most

AceMQ Neo4j support gives you an AceMQ engineer and response targets from 15 minutes, by plan, when a database is failing, 24/7. It runs beside a Neo4j subscription or on its own, and it covers Community Edition as well as Enterprise Edition.

  1. From 15 min (by plan)first responseEmergencyProduction down, messages not flowing, queue manager failure
  2. 1 hourfirst responseCriticalSevere degradation, high error rates, approaching capacity
  3. 4 hoursfirst responseHighPerformance issues, configuration problems, non-critical failures
  4. Next Dayfirst responseStandardQuestions, guidance, best practices, non-urgent improvements

Response targets by plan; your contract sets the tier.

P1 escalation path

A replay of one P1, from the first page to the written root-cause analysis

SLA 15:00
T+Elapsed15:00
Engineer on your bridge

Response targets from 15 minutes, by plan; 24/7.
A response time, not a resolution time.

  1. T+00:00

    P1 opened, on-call engineer paged

    Phone, email or Slack reaches the on-call senior engineer directly, whether the incident is in RabbitMQ, Kafka, Redis, PostgreSQL or Kubernetes. No web form, no tier-1 queue.

    Paged
  2. T+15:00

    Senior engineer on your bridge

    A senior engineer who already knows your environment joins a live bridge, so nobody has to re-explain your topology.

    Live
  3. T+30:00

    Specialists across the stack join

    When an incident crosses components, the engineers who know each one join. For RabbitMQ, the path runs to the core team.

    If needed
  4. After

    Written root-cause analysis

    Root cause, the fix applied and the prevention steps, delivered after every P1.

    Every P1

How Our Support Actually Works

Beyond SLAs — the model behind senior-only, zero-cold-start expert access.

  • Engineers Who Know Your Environment

    Tickets go to senior engineers briefed on your environment, not an anonymous queue. The proposal states who does the work.

  • Live Escalation on Any Ticket

    Any ticket can be escalated to a live session with an engineer through calendar booking. No gatekeeping and no approval step.

  • Proactive Risk Mitigation

    Scheduled health checks on your deployment and alerts on risks in the versions you run, so problems surface before they reach production.

  • Critical Bug & CVE Intelligence

    Proactive alerts on critical bugs and CVEs affecting your exact version, with version compliance monitoring so you're never caught off guard.

How It Works

What actually happens next

An AceMQ Neo4j engagement runs in four stages: a scoping call with a quote within 1 hour, an environment review, a written plan, then the work or a handover. Each stage ends in writing.

Quote within 1 hour

Scoping call and quote

A senior AceMQ engineer asks what you run: the Neo4j version and edition, whether it is a single server or a cluster, how it is deployed, and the queries that hurt, and what has prompted the question. A quote request is answered within 1 hour.

Scoped per estate

Environment review

The deployment read end to end: memory settings against the store, the slowest queries with their plans, indexes and constraints, cluster state, transaction logs, and the backup and restore evidence. Findings are written down and your team keeps them.

Scoped per estate

Written plan

A recommendation in writing: the query and index changes, memory settings, cluster layout and the upgrade path, with who runs what afterwards. The plan includes a rehearsal on a copy and a rollback that has been tested, not assumed.

Ongoing or fixed scope

Run the work or hand over

Changes staged one server at a time with a rollback for each, measured before and after. The work ends with a runbook for backups, restores and the next upgrade. You can stop there, add 24/7 cover, or have AceMQ run the estate for you as a managed service on your infrastructure.

  • Written findings before any change
  • Changes staged and reversible, with a rollback plan
  • Your engineers in the room
  • Ad hoc engagements or an annual partnership

A senior engineer, not an SDR. No sales sequence attached.

Typical engagements

How Neo4j engagements run

Neo4j work from AceMQ will appear here as engagements are published. Each card links to the full write-up.

All use cases

Solutions

Every way AceMQ works with Neo4j.

AceMQ covers Neo4j end to end. Projects: consulting and implementation, health checks and migrations. Ongoing cover in four tiers, from 24/7 support and incident management to proactive monitoring, managed Neo4j on your infrastructure and fully managed Neo4j on AceMQ infrastructure, plus end-of-life versions.

Projects

Build, fix or move Neo4j

Fixed-scope work led by a senior engineer: architecture and new builds, a health check of what you run today, or a migration with a reversible cutover.

Side by side

Neo4j support, AceMQ independent support or both: what changes?

Neo4j supplies releases and defect fixes under its support terms. AceMQ supplies engineers who work your queries, memory settings and clusters, beside a Neo4j contract or on its own. Each row answers one question about the choice.

Neo4j support and AceMQ independent support compared on who is covered, hours and response, product defects, day-to-day operations and how each is bought
QuestionNeo4j supportAceMQ independent support
Who is covered?Customers with a valid Enterprise Edition licence and AuraDB subscribers. Community Edition is not covered (neo4j.com/terms/support-terms, read 17 November 2026).Self-managed Enterprise Edition and Community Edition, on virtual machines, bare metal and Kubernetes.
What are the hours and response targets?By package. Severity 1 initial response runs from 30 minutes on the Signature package to 2 business hours on Essential (same page).24/7 across Americas, EMEA and APAC; response targets from 15 minutes, by plan.
Who fixes product defects?Neo4j supplies the fix.We reproduce the problem, work the case with Neo4j on your behalf where you hold a subscription, and apply the fix.
Who works queries, memory and clusters?Questions about the product, under the support terms.Core of our work: query plans, heap and page cache, transaction logs, backups and cluster behavior.
How is it bought?Through a Neo4j subscription.$24,000 to $72,000 a year (USD), set by SLA, scope and deployment. Quote reply within 1 hour.

For the wider picture across databases, read database consulting.

Not sure which option fits? A senior Neo4j engineer will scope it with you.

Contact Us

One partner, not five

We Support Your Entire Tech Stack

Neo4j rarely fails in isolation. AceMQ covers the full surrounding infrastructure — so one team owns the whole path instead of pointing at each other.

See all the technologies we supportShow fewer

What we check first

Neo4j problems teams bring to AceMQ, and what we check first

Each row starts from what you see. The commands are Neo4j's own, checked against its operations and Cypher manuals on 17 November 2026.

Neo4j symptoms and what AceMQ checks first
What you seeWhat we check first
A Cypher query that was fast on test data takes minutes in productionThe PROFILE plan, which runs the query, so on a copy or off-peak: an index seek or a label scan, where rows multiply, and whether an index or constraint is missing (SHOW INDEXES, SHOW CONSTRAINTS)
Latency spikes and long pauses under loadHeap and page cache against the store size (neo4j-admin server memory-recommendation), garbage collection pauses, and how much of the graph fits in the page cache
Transactions pile up or time outSHOW TRANSACTIONS for long-running and blocked transactions, lock contention on dense nodes, and db.transaction.timeout, which defaults to no timeout
The cluster elects a new leader repeatedlySHOW SERVERS and SHOW DATABASES for each server's state and each database's role, network latency between primaries, and the server logs
Disk fills with transaction logsdb.tx_log.rotation.retention_policy (default 2 days 2G) against the backup cadence, since differential backups need older logs
Backups exist but nobody has restored oneThe backup schedule and chain (neo4j-admin database backup), a timed restore on a clean server (neo4j-admin database restore) and a written recovery procedure
An upgrade keeps slippingThe version path across calendar releases, plugin compatibility, and whether queries run on Cypher 5 or Cypher 25
Bulk loads take daysOffline import (neo4j-admin database import, which needs the database offline) against the transactional LOAD CSV path, batching and index timing

Versions

Neo4j versions we support

We support the release each of your servers runs on and plan the move to a current one.

Neo4j version lines and what AceMQ does on each
Version lineWhat Neo4j says (read 17 November 2026)What AceMQ does on it
2026.x and 2025.x calendar releasesSince 2025.01.0 Neo4j versions as YYYY.MM.Patch; the operations manual lists 2026.10 as the current release (neo4j.com/docs/operations-manual/current/introduction)24/7 support and upgrade planning
5.26 and 4.4Both appear in the operations manual's version selector (same page)24/7 support and upgrade planning to a current calendar release

Cypher is versioned separately from the server. Cypher 5 receives fixes and performance work only, and new features go to Cypher 25, which is the default for new databases from 2026.02 (neo4j.com/docs/cypher-manual/current/queries/select-version, read 17 November 2026). You can set the version per database or per query.

FAQs

Neo4j Questions Answered

Answers on Neo4j from AceMQ: who provides enterprise support, what a health check includes, why queries are slow, how an upgrade is planned and what Community Edition gets.

Still have questions about Neo4j? Email an Expert

Who provides enterprise support for Neo4j?

Neo4j provides technical support to customers with a valid Enterprise Edition licence and to AuraDB subscribers; Community Edition is not covered by its terms (neo4j.com/terms/support-terms, read 17 November 2026). AceMQ provides independent support for self-managed Neo4j, 24/7 across Americas, EMEA and APAC with response targets from 15 minutes, by plan, alongside a Neo4j contract or on its own.

Who offers Neo4j consulting and professional services?

Neo4j and its partners offer consulting, and independent firms such as AceMQ consult on query tuning, cluster design, upgrades and health checks. Our engineers are the same people who work the 24/7 rota.

What does a Neo4j health check include?

Heap and page cache sizing, the slowest queries with their plans, index and constraint coverage, transaction and lock behavior, cluster and database state, transaction log retention, backup and tested restore, and a ranked plan.

Why is my Neo4j query slow in production?

Usually the plan differs from what you tested: a label scan instead of an index seek, a missing constraint, or a dense node that multiplies rows. We read the PROFILE output, fix the index or the query shape and measure the result.

How do you plan a Neo4j upgrade without downtime?

We start with the version path and the Cypher version your queries use, check plugins, rehearse on a copy of the store and upgrade a cluster one server at a time with a rollback. The first step is an inventory of versions, editions and plugins.

Does AceMQ support Neo4j Community Edition?

Yes. Neo4j's support terms cover Enterprise Edition licence holders and AuraDB subscribers; AceMQ supports Community Edition operations and troubleshooting as well, as a single server. Neo4j publishes Community Edition under GPL v3 (neo4j.com/licensing, read 17 November 2026).

Can you help with Neo4j on Kubernetes?

Yes: persistent storage, memory limits against heap and page cache, rolling restarts of a cluster and backup jobs.

What is the difference between Neo4j Community and Enterprise Edition?

Neo4j describes Community Edition as single-instance, and Enterprise Edition as adding clustering, online backup, failover, role-based access control and LDAP support (neo4j.com/docs/operations-manual/current/introduction, read 17 November 2026).

Can you help us choose between Neo4j and another database?

Yes. We assess the access patterns of the workload and compare the options against it. For some workloads a relational or document store such as PostgreSQL or MongoDB is the simpler answer, and we will say so.

Can we work with AceMQ on Neo4j without a long contract?

Yes. AceMQ works on Neo4j in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual contract that covers 24/7 support and proactive reviews. Many teams start ad hoc and move to an annual contract once the first engagement is done.

How much does AceMQ Neo4j support or consulting cost?

Every AceMQ proposal is tailored to your requirements: your Neo4j environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how Neo4j is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.

Let's talk

Find the Query That Scans Your Whole Graph

Send us your Neo4j version, edition and the queries that hurt. We reply to quote requests within 1 hour.

A senior AceMQ engineer, not a sales queueAbout your Neo4j estate, not a pitch deckQuote requests answered within 1 hour

Production incident right now?Email a Neo4j Architect

Get in Touch

Talk to a Neo4j Expert

Send us a message and we'll follow up within 1 hour — or book a free 30-min consultation directly.

305-204-2607
info@acemq.com
66 W. Flagler St. 9th Floor
Miami, FL 33130

Prefer to talk now? Call us directly or use the consultation tab to find a time that works.

We respond within 1 hour.

Pick a time that works — no pressure, no pitch. Just 30 minutes with an expert.

We respond within 1 hour.