Neo4j Self-Managed
Self-managed graph database available in open-source Community and commercial Enterprise editions.
8 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Neo4j Graph Data Science Guava denial-of-service dependency
Graph Data Science 2026.10.2 upgrades Guava to 33.7.2 to fix CVE-2026-102554, an uncontrolled-memory-allocation issue during attacker-controlled Java deserialization.
Scope: Guava 4.0 through 33.7.1 is affected and 33.7.2 is fixed. Neo4j does not identify which earlier GDS releases expose the path or claim that core Neo4j is affected.
Requires the optional GDS component and a reachable attacker-controlled Java-deserialization path.
Action: Use GDS 2026.10.2 or later and assess whether any Java-deserialization path is exposed.
Primary source · GDS 2026.10.2 notes · Reviewed 2026-11-18
What lands where
Supplied by
Vendor or project
Official Helm charts on EKS, AKS or GKE; cloud marketplace and VM options also exist
Runs in
Documented customer environment
Customer-operated standalone or clustered graph database servers with persistent volumes
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Your team
Customer manages compute, storage, networking, security, backups, monitoring, capacity and upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Neo4j Helm deployments on EKS, AKS and GKE ↗ · Source checked 2026-11-14
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Neo4j Helm deployments on EKS, AKS and GKE ↗ · Source checked 2026-11-14
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Neo4j Helm deployments on EKS, AKS and GKE ↗ · Source checked 2026-11-14
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Official Helm charts on EKS, AKS or GKE; cloud marketplace and VM options also exist |
|---|---|
| Infrastructure | Servers / containers Neo4j runs persistent standalone or clustered database servers with attached storage. Kubernetes and cloud placement do not remove state, backup or upgrade responsibilities. |
| Licensing model | Open Source / Open Core Neo4j Community Edition is GPLv3. Enterprise Edition is commercially licensed and adds clustering, advanced security and operational capabilities. |
| License | GPLv3 Community Edition; Enterprise Edition uses a commercial Neo4j license. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
6 of 12 fields researched (50%) · 6 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Edition-dependentEvidence and scope for Single sign-on
Neo4j documents OIDC single sign-on for Enterprise Edition, including role mapping and multiple providers. The server must be able to reach its identity provider; this is not a Community Edition entitlement.
Self-managed Neo4j Enterprise Edition · Source ↗ · Reviewed 2026-11-14
Edition-dependent · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
Current advisory review: Graph Data Science 2026.10.2 upgrades Guava to 33.7.2 to fix CVE-2026-102554, an uncontrolled-memory-allocation issue during attacker-controlled Java deserialization. Use GDS 2026.10.2 or later and assess whether any Java-deserialization path is exposed.
Guava 4.0 through 33.7.1 is affected and 33.7.2 is fixed. Neo4j does not identify which earlier GDS releases expose the path or claim that core Neo4j is affected. · Source ↗ · GDS 2026.10.2 notes ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The vendor publishes Helm charts and values for a Kubernetes cluster, including an Enterprise three-member example and cloud storage classes. Enterprise requires licence acceptance; select compatible chart/database versions and configure secrets, volumes and backups.
Official Enterprise cluster Helm deployment · Source ↗ · Deployment artifact ↗ (Choose compatible chart and Neo4j versions) · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The current Helm guide enforces at least 0.5 CPU and 2 GB memory per Neo4j instance and shows a three-member Enterprise cluster. These are deployment floors, not production sizing for a dataset. Graph/index size, page cache, query memory, storage and failure headroom require separate sizing.
Helm per-instance floor; cluster and workload capacity not validated · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The vendor separates Community GPLv3 terms from the self-managed Enterprise Software Agreement and commercial support terms. Enterprise clustering/features require the corresponding entitlement; do not apply Aura hosted per-GB rates or the Community licence to an Enterprise deployment. Obtain a self-managed quote.
Self-managed Community versus commercial Enterprise licensing · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
Neo4j 2026.10.2 was released November 6, 2026. Its compatible Graph Data Science 2026.10.2 component upgrades Guava to 33.7.2 for CVE-2026-102554; that conditional component finding is not a core DBMS claim.
Neo4j Database and optional Graph Data Science 2026.10.2 · Source ↗ · GDS 2026.10.2 ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
Show all fields (6 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
Community Edition is designed for standalone deployments. Clustering, advanced security and online backup features require Enterprise Edition. This entry does not cover the managed Neo4j Aura service. Deployments that install Graph Data Science should use GDS 2026.10.2 or later, which moves Guava to 33.7.2 for CVE-2026-102554. The advisory concerns attacker-controlled Java deserialization in GDS's dependency; it does not establish that core Neo4j or a default deployment exposes the vulnerable path.
Community & maintenance
The upstream open-source project documents its public contribution process and sustained participation from multiple contributors. Vendor release notes record database 2026.10.2 on November 6, 2026, establishing current maintenance. This evidence concerns the project and database release history; it does not make Enterprise-only clustering, backup or bundled tools part of the Community license.
Category fit
- Databases & vector
- Provides a graph database with Cypher queries, graph traversal and vector-index capabilities in customer-operated deployments.
Compare within Databases & vector
- Apache Doris Self-HostedApache-licensed analytical database with upstream AWS EKS/Alibaba ACK/ACS guides and a separately packaged cloudimg Azure VM path.
- AWS
- Azure
- Alibaba Cloud
- ClickHouse BYOCManaged analytical database with its data plane in your cloud account.
- AWS
- Azure
- Google Cloud
- CockroachDB BYOCVendor-managed CockroachDB service deployed into the customer's AWS, Azure or Google Cloud account.
- AWS
- Azure
- Google Cloud
- Couchbase Server Enterprise EditionSelf-managed distributed NoSQL database deployed in customer-controlled Kubernetes with the Couchbase Operator.
- AWS
- Azure
- Google Cloud
- Elastic Cloud EnterpriseCommercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.
- AWS
- Azure
- Google Cloud
- Elastic Cloud on KubernetesElastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.
- AWS
- Azure
- Google Cloud
- Meilisearch Community EditionSelf-hosted search engine for typo-tolerant full-text, semantic and hybrid retrieval.
- AWS
- Google Cloud
- DigitalOcean
- MilvusVector database for similarity search and retrieval over embedding collections.
- AWS
- Azure
- Google Cloud
Showing 8 of 18 other listings in Databases & vector. These products address related workflows; read their category-fit notes before comparing scope. See all of Databases & vector →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Self-managed editions ↗neo4j.com
- Kubernetes deployments ↗neo4j.com
- Cloud deployment options ↗neo4j.com
- Open-source project and contributor participation ↗neo4j.com
- Neo4j 2026.10.2 release notes ↗neo4j.com
- Upstream contributor history ↗github.com
- Graph Data Science 2026.10.2 release notes ↗neo4j.com
- Guava CVE-2026-102554 advisory ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Neo4j Helm deployments on EKS, AKS and GKE ↗ · AWS, Azure, Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.
Neo4j's Operations Manual documents standalone and clustered Helm deployments on Amazon EKS, Microsoft AKS and Google GKE. Edition and license requirements differ between standalone Community and clustered Enterprise deployments.
- Neo4j Helm deployments on EKS, AKS and GKE ↗ · AWS, Azure, Google Cloud
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked