Skip to content
Neo4j Community Graph Database product logo
  • AWSAvailable on Amazon Web Services
  • AzureAvailable on Microsoft Azure
  • GCP· nextGoogle Cloud is next on the roadmap
Available

Neo4j Community Graph Database

Neo4j Community 2026.08.1 - the current stable release - with cypher-shell, on Ubuntu 24.04 LTS. Neo4j Browser and Bolt are ready the moment the instance boots, with your credential staged before any port opens so the very first connection is already yours. Heap and page cache auto-size to whatever instance type you launch.

Version
v2026.08.1
Operating system
Ubuntu 24.04 LTS
Architecture
x86_64
Support
Email support

What's installed

Every package and version on the image, identical on every cloud it ships on. Nothing else is installed.

  • Neo4j Community 2026.08.1
  • cypher-shell 2026.08.1
  • OpenJDK 21.0.12 JRE

LicensingNeo4j Community Edition (GPL-3.0), no licence key required

Deploy anywhere

Neo4j Community Graph Database on AWS and Azure.

Google Cloud is next on the roadmap. One clean-room build, one first-boot credential model, one patch cadence — identical on every cloud you run. Every identifier below is the real one; copy it and launch.

  1. AWS
    Available

    Amazon Web Services

    AMI · v2026.08.1

    AWS AMI ID

    Shown for your region on the AWS Marketplace launch page once you subscribe.

    Released
    Root volume
    gp3 · 30 GiB
    Instance types
    • t3a.large
    • t3.large
    • m6a.large
    • t3a.xlarge
    Regions34 regions· show all
    • us-east-1
    • af-south-1
    • ap-east-1
    • ap-east-2
    • ap-northeast-1
    • ap-northeast-2
    • ap-northeast-3
    • ap-south-1
    • ap-south-2
    • ap-southeast-1
    • ap-southeast-2
    • ap-southeast-3
    • ap-southeast-4
    • ap-southeast-5
    • ap-southeast-6
    • ap-southeast-7
    • ca-central-1
    • ca-west-1
    • eu-central-1
    • eu-central-2
    • eu-north-1
    • eu-south-1
    • eu-south-2
    • eu-west-1
    • eu-west-2
    • eu-west-3
    • il-central-1
    • me-central-1
    • me-south-1
    • mx-central-1
    • sa-east-1
    • us-east-2
    • us-west-1
    • us-west-2
    Launch on AWS MarketplaceAWS launch steps

    5-day free trial, then from $0.04/hr software charge (larger instance sizes cost more) plus your own EC2 costs, billed by AWS.

    Subscriptions are open to AWS India (AISPL) accounts. Outside India? Ask us for a private build.

  2. Azure
    Available

    Microsoft Azure

    Compute Gallery image · v2026.08.1

    Azure Compute Gallery image ID

    Selected for you when you create the VM from the Azure Marketplace listing.

    Released
    OS disk
    Premium_LRS · 30 GiB
    VM sizes
    • Standard_D2as_v7
    • Standard_D2as_v5
    • Standard_B2ms
    • Standard_D4as_v7
    Regions50 regions· show all
    • eastus
    • australiacentral
    • australiaeast
    • australiasoutheast
    • austriaeast
    • belgiumcentral
    • brazilsouth
    • canadacentral
    • canadaeast
    • centralindia
    • centralus
    • chilecentral
    • denmarkeast
    • eastasia
    • eastus2
    • francecentral
    • germanywestcentral
    • indiasouthcentral
    • indonesiacentral
    • israelcentral
    • italynorth
    • japaneast
    • japanwest
    • jioindiawest
    • koreacentral
    • koreasouth
    • malaysiawest
    • mexicocentral
    • newzealandnorth
    • northcentralus
    • northeurope
    • norwayeast
    • polandcentral
    • qatarcentral
    • southafricanorth
    • southcentralus
    • southeastasia
    • southindia
    • spaincentral
    • swedencentral
    • switzerlandnorth
    • uaenorth
    • uksouth
    • ukwest
    • westcentralus
    • westeurope
    • westindia
    • westus
    • westus2
    • westus3
    Launch on Azure MarketplaceAzure launch steps
AWS

Getting started on Amazon Web Services

From launch to signed in, step by step.

  1. Subscribe on AWS Marketplace and launch in your region with TCP 22, 7474 and 7687 open; wait for the health checks to pass.

  2. Open http://<instance-public-ip>:7474 for Neo4j Browser and sign in with username neo4j and your EC2 Instance ID as the password, exactly as the console shows it (for example i-0123456789abcdef0).

  3. Drivers connect at bolt://<instance-public-ip>:7687 with the same credentials. HTTPS on 7473 is off by design; put TLS in front for production.

  4. SSH as ubuntu with your key pair. Change the password with sudo bash /home/ubuntu/iscripts/pass_neo4j.sh; neo4j_status.sh prints version, service state, sockets and your URLs.

  5. Open 7474 and 7687 only to the addresses that need them.

Security posture

What this AWS image does and does not ship with, one fact per line.

  • Clean-room build on Canonical's official Ubuntu 24.04 LTS image: every component comes from its own official repository or release, nothing is copied from any third-party image, and the finished image was scanned for third-party vendor strings before capture.

  • No usable credential ships in the image; passwords are set on your instance at first boot from EC2 instance metadata (IMDSv2) and the scripts that set them delete themselves afterwards.

  • SSH is key-only, root login over SSH is refused, and build-time SSH keys, shell history and logs were removed before imaging.

  • The published image contains no Neo4j system database and no password: provencloud-neo4j-firstboot.service runs Before=neo4j.service, reads the Instance ID from IMDS and calls neo4j-admin set-initial-password before a single port opens, which removes the window in which a build-time password could be accepted.

  • A second, idempotent first-boot pass confirms the credential and repairs it if IMDS was slow, without ever touching users you created in the meantime.

  • Packages come from Neo4j's own signed apt repository.

  • Bolt and HTTP are the only listeners; open 7474 and 7687 only to the addresses that need them.

  • The bundled password tools enforce at least 10 characters with upper- and lower-case letters, a number and a symbol, and verify the new credential with a real sign-in before reporting success.

  • The image is HTTP-only by design so it works at a bare IP with no certificate warnings: terminate TLS at a load balancer or add a certificate before exposing it publicly, and restrict port 22 and any admin ports to trusted IP ranges in your security group.

Azure

Getting started on Microsoft Azure

From launch to signed in, step by step.

  1. Create the VM from the Azure Marketplace listing with TCP 22, 7474 and 7687 open in your network security group. Choose ubuntu as the administrator username so SSH and the script paths match. Wait a few minutes for first boot.

  2. Open http://<vm-public-ip>:7474/ and sign in with the username neo4j. Allow about three minutes after the VM starts.

  3. Applications connect over Bolt at bolt://<vm-public-ip>:7687 with the same credentials.

  4. SSH as ubuntu with your key. Change the password with sudo bash ~/iscripts/pass_neo4j.sh.

  5. The password for each console is your VM ID. Your VM ID is in the Azure portal: open the virtual machine, choose Properties and copy VM ID - a 36-character value such as 02aab8a4-74ef-476e-8182-f6d2ba4166a6, typed exactly as shown in lower case. Every deployment derives its own passwords from that value on first boot, so no two virtual machines share a credential.

Security posture

What this Azure image does and does not ship with, one fact per line.

  • Clean-room build on Canonical's official Ubuntu 24.04 LTS image from the Azure Marketplace: every component comes from its own official source and the image was scanned for third-party vendor strings before capture.

  • Nothing guessable ships in the image - the pre-image cleanup randomises every credential the build set and proves the build's own password no longer authenticates; first boot then sets each password from the new VM's own vmId read from Azure IMDS, and regenerates the per-instance secrets so no encryption key is shared between deployments.

  • The ubuntu login account ships password-locked with an empty authorized_keys, and cloud-init installs your own SSH key at deploy time.

  • The initial password is staged before the database ever starts, so Neo4j never runs with its default credential.

  • All 24 JVM tuning flags are preserved intact.

  • Verified against Microsoft's documented Linux certification test cases on a VM deployed from this exact gallery version - 13 passed, 0 failures - with VM extension provisioning confirmed and the customer sign-in path exercised end to end.

  • The bundled password tools require at least 10 characters with upper- and lower-case letters, a number and a symbol, and verify the new credential with a real sign-in before reporting success.

  • The image is HTTP-only by design so it works at a bare IP with no certificate warnings: terminate TLS at a load balancer or add a certificate before exposing it publicly, and restrict port 22 and any admin ports to trusted IP ranges.