---
title: "Deploy Neo4j 2026.10 Community"
description: "Neo4j graph database with APOC, Browser, Bolt TCP proxy and a volume"
category: "Storage"
url: https://railway.com/deploy/neo4j-202610-community
---

# Deploy Neo4j 2026.10 Community

Neo4j graph database with APOC, Browser, Bolt TCP proxy and a volume

**[Deploy Neo4j 2026.10 Community on Railway](https://railway.com/template/neo4j-202610-community)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/neo4j-202610-community/manifest.json

- **Creator:** My Projects
- **Category:** Storage

## Template content

### Neo4j https://cdn.jsdelivr.net/gh/selfhst/icons/svg/neo4j.svg

- **Image:** neo4j:2026.10.1-community
- **Health check:** /
- **Public domain:** Yes

## Documentation

# Deploy and Host Neo4j 2026.10 Community on Railway

Neo4j is the most widely used graph database. You store data as nodes and relationships and query it with Cypher. It is used for knowledge graphs, GraphRAG and AI agent memory, recommendations, fraud detection and network analysis. This template runs Neo4j Community 2026.10 with APOC, Neo4j Browser over HTTPS, and Bolt for your drivers.

## About Hosting Neo4j 2026.10 Community

A Neo4j server needs a persistent volume, a password, and memory limits. Without explicit limits, the JVM sizes its heap and page cache from the container limit, not from your data. Drivers need a Bolt port they can reach, and Neo4j Browser needs a connection that works over HTTPS. Many Neo4j templates still run with `NEO4J_AUTH=none`, use the `latest` tag, or expose Browser with no working connection.

This template runs the official `neo4j:2026.10.1-community` image with a volume at `/data`, a generated password, the APOC core plugin, and a heap and page cache sized for the Hobby plan. Neo4j Browser and the HTTP Query API are on the public HTTPS domain, and both ask for the password. Drivers connect over Railway's private network, or from outside through a password-protected TCP proxy.

## Common Use Cases

- Knowledge graphs and GraphRAG backends for LightRAG, Graphiti, LangChain, LlamaIndex and neo4j-graphrag
- Long-term memory for AI agents, and MCP servers such as mcp-neo4j-cypher
- Recommendation engines, fraud and identity graphs, and network or IT dependency maps
- Learning Cypher, or a Neo4j development and staging database next to your app on Railway

## Dependencies for Neo4j 2026.10 Community Hosting

- Neo4j 2026.10.1 Community Edition (official `neo4j` image)
- APOC core 2026.10.1 (bundled in the image)

### Deployment Dependencies

- Neo4j: https://neo4j.com/
- Neo4j Docker image: https://hub.docker.com/_/neo4j
- Neo4j Operations Manual (Docker): https://neo4j.com/docs/operations-manual/current/docker/
- APOC: https://neo4j.com/docs/apoc/current/

### Implementation Details

**What you set:** nothing. The password is generated.

**After deploy:**

1. Open `BROWSER_URL` from the Neo4j service's Variables. It opens Neo4j Browser with the connection form filled in (protocol `https://`, port 443). Log in as `neo4j` with `DB_PASSWORD`.
2. From another service in this project, set:

```
NEO4J_URI=${{Neo4j.BOLT_URL}}
NEO4J_USERNAME=${{Neo4j.DB_USER}}
NEO4J_PASSWORD=${{Neo4j.DB_PASSWORD}}
```

3. From outside Railway, use `BOLT_PUBLIC_URL` (for example `bolt://:`) with user `neo4j` and `DB_PASSWORD`:

```python
from neo4j import GraphDatabase
driver = GraphDatabase.driver("bolt://:", auth=("neo4j", ""))
```

**This template:**

- Uses the official Neo4j 2026.10.1 Community image, pinned
- Generates a 32-character password, so the database is never open
- Keeps databases on a volume, so your graph survives redeploys
- Loads APOC from the image itself, with no download at start
- Sets heap (512 MB) and page cache (256 MB) explicitly, adjustable with variables
- Serves Neo4j Browser over HTTPS, connected through the HTTP Query API, so no extra port is needed
- Listens on IPv6, so services on Railway's private network reach Bolt
- Offers ready-made variables (`BOLT_URL`, `DB_USER`, `DB_PASSWORD`, `HTTP_URL`) for your apps

**Notes:** the password is set on the first start. To change it later, run `ALTER CURRENT USER SET PASSWORD FROM '' TO ''` in Browser, then update `DB_PASSWORD`. The TCP proxy checks the password but is not TLS-encrypted, so prefer the private network for sensitive data, or remove the TCP proxy. Neo4j idles at about 1.3 to 1.7 GB of RAM with these settings. Community Edition is a single server (no clustering, no role-based access control).

## Why Deploy Neo4j 2026.10 Community on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Neo4j 2026.10 Community on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.


## Similar templates

- [RustFS | (Just Updated) S3 Object Store, Public URL and Keys Set](https://railway.com/deploy/rustfs-or-just-updated-s3-object-store-p) — S3-compatible object store, keys and public URL preset, volume kept
- [TimescaleDB](https://railway.com/deploy/timescaledb-railway-template) — A PostgreSQL-based time-series database for analytics on Railway.
- [Garage S3 Storage](https://railway.com/deploy/garage-s3-storage) — Ultra-light S3 server: fast, open-source, plug-and-play.

Open this page in a browser: https://railway.com/deploy/neo4j-202610-community