Deploy and Host Neo4j on Railway

Neo4j is the most widely used open-source graph database. It stores data as nodes and relationships and is queried with Cypher. This template runs Neo4j Community with a persistent volume, a generated password, and a public HTTPS endpoint for the Query API.

About Hosting Neo4j

This template runs the official neo4j image (pinned by digest). Data lives on a volume mounted at /data, so graphs survive redeploys. Authentication is enabled at boot: the username is neo4j and the password is the GRAPH_PASSWORD variable, generated for you at deploy time. The HTTP port is bound to Railway's $PORT; Bolt listens on 7687 inside the project network and is published to your other services as GRAPH_BOLT_URL. The JVM is capped to the container (heap and page cache sized explicitly, ActiveProcessorCount=2) so it does not read the host's resources.

Agent contract:

Base URL: https://
Username: neo4j
Password variable: GRAPH_PASSWORD
Bolt URL variable (private network): GRAPH_BOLT_URL
Health path: /
Query endpoint: POST /db/neo4j/query/v2 (HTTP basic auth)

curl -s -u neo4j:$GRAPH_PASSWORD -X POST https:///db/neo4j/query/v2 \
  -H 'content-type: application/json' \
  -d '{"statement":"CREATE (n:Note {text:\"hello\"}) RETURN n.text AS text"}'

Why Deploy Neo4j 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 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.

Secure by default — the password is generated per deploy and unauthenticated requests get 401.
Data survives redeploys — the volume is preconfigured and verified with a write, redeploy, read.
Zero configuration — no variables to fill in; the contract above is everything a client needs.
Standard drivers work — official Neo4j drivers connect over Bolt, and any HTTP client can use the Query API.

Common Use Cases

Knowledge graphs and agent memory — store entities and relationships for AI agents and RAG pipelines.
Recommendations and fraud detection — traverse connected data that is awkward in relational tables.
Network and dependency mapping — model infrastructure, org charts, and supply chains.

Dependencies for Neo4j Hosting

A volume mounted at /data (included in this template).

Deployment Dependencies

neo4j/neo4j — upstream server
neo4j on Docker Hub — the pinned image this template deploys