macOS
Homebrew Caskverified · 100%
brew install --cask neo4j-desktoplocal Homebrew cask metadata
cask
Install neo4j-desktop with Homebrew Cask
Developer IDE or Management Environment for Neo4j instances. Version 2.3.1 via Homebrew Cask; verified from local package data.
install
Additional install commands
overview
Package summary
Developer IDE or Management Environment for Neo4j instances
Project links
Commands and aliases
No executable aliases were found in the local package database.
history
Project history and usage
Neo4j Desktop is Neo4j's graphical local development and management environment for creating DBMS instances, managing graph databases, running Cypher, importing data, visualizing graphs, and connecting to remote Neo4j services.
Project history
Neo4j Desktop began as a desktop packaging of the Neo4j graph platform with a bundled JVM, Developer Edition database, and graph applications. The official project repository describes it as a client containing everything needed to start working with Neo4j.
Desktop 2.x is described by Neo4j as an evolution of the original Desktop, with a redesigned and more unified experience that mirrors the Neo4j Aura console. It consolidated local instance management with Import, Query, Bloom, and Dashboards in Desktop Studio.
Adoption history
Neo4j Desktop packages a local developer environment around Neo4j rather than requiring users to assemble a database server, JVM, query UI, import tooling, and visualization tools separately. It supports macOS, Windows, and Linux and can manage local databases while also connecting to remote Neo4j and Aura instances.
Desktop includes a Developer edition license for local single-user use and supports installing plugins through its interface, making it a common entry point for graph application development and Cypher experimentation.
How it is used
Developers create projects and local DBMS instances, select a Neo4j version, start or stop instances, edit each instance's `neo4j.conf`, install plugins, import data, and query or visualize graphs from the bundled Studio tools.
The official UI exposes each local instance's folder, log, configuration file, data path, connection URI, security controls, backup actions, and upgrade workflow.
Why package nerds care
Neo4j Desktop is the batteries-included desktop distribution in the Neo4j ecosystem. Package users care about it because the application manages multiple DBMS versions and instance directories while bundling import, query, Bloom visualization, and dashboard tools.
It differs from the standalone Neo4j server package: Desktop prioritizes an interactive local workspace and lifecycle management, whereas the server and Cypher Shell packages better suit services, scripts, and headless environments.
Timeline
- The original Neo4j Desktop combined a local Neo4j developer installation with bundled graph applications.
- Desktop 2.x introduced a redesigned workspace aligned with the Aura console and unified Import, Query, Bloom, and Dashboards as Desktop Studio.
- Desktop 2.x added migration support for cloning compatible instances from Desktop 1.x.
Related projects
- Neo4j DBMS is the graph database managed locally by Desktop.
- Neo4j Aura supplies managed remote Neo4j instances that Desktop can connect to.
- Cypher Shell provides a command-line path for running queries and administrative commands.
- APOC plugins can be installed into compatible local instances from Desktop.
Sources
security posture
No protected-tool coverage found yet
No matching local secret-handling manifest was found for neo4j-desktop. Package metadata is still published here so future coverage has a stable package URL.
Install behavior
- No Homebrew post-install hook is recorded in formula metadata.
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- Unix
<Neo4j Desktop instance folder>/conf/neo4j.conf- Windows
<Neo4j Desktop instance folder>\conf\neo4j.conf
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
| No executable data was present. | |||
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-11-04
manager version2.3.1
manager updated
local dataok
upstreamnot checked
latest detectednot detected
- infoNo package-manager update timestamp was available.low confidence
- infoRelease/tag comparison is only available for GitHub repositories.https://neo4j.com/download/none confidence
install metadata
Package metadata
| Package key | cask:neo4j-desktop |
|---|---|
| Version | 2.3.1 |
| Package manager | Homebrew Cask |
| Package manager page | https://formulae.brew.sh/cask/neo4j-desktop |
| Homepage | https://neo4j.com/download/ |
| Upstream docs | https://neo4j.com/download/ |
| Source archive | https://dist.neo4j.org/neo4j-desktop-2/mac/neo4j-desktop-2.3.1-universal.dmg |
| SHA-256 | 045005b2c6d651ecfae6deabfffb807873933a9b484c8c478ae9f7c95c1214f0 |
| Bottle | not recorded |
| Homebrew post-install | not defined |
| Service | none declared |
registry facts
Source database details
| Source Database | Homebrew cask API |
|---|---|
| Tap | homebrew/cask |
| Full Token | neo4j-desktop |
| Names |
|
| Old Tokens |
|
| Depends On | |
| Artifacts | |
| Deprecated | no |
| Disabled | no |
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- package relationship graph
- package version freshness
- package-page enrichment