briqbriq
Dashboard

cookbook / neo4j

Neo4j

A graph database with a persistent volume, for data an agent should query, not paraphrase.

Run it

briq_run({
  recipe: "neo4j",
  params: {
    "version": "5",
    "size": "small"
  },
  wait: true
})

Parameters

NameTypeOptionsDefault
versionenum5"5"
sizeenumnano, small, medium, large"small"

Outputs

Returned by briq_run once the stack is healthy. Hosts resolve inside your team network; secrets are generated per run.

NEO4J_BOLT_URL
bolt://neo4j.<stack>.internal:7687
NEO4J_HTTP_URL
http://neo4j.<stack>.internal:7474
NEO4J_AUTH
none

What it runs

BriqImagePortsSizeVolume
neo4jneo4j:57474, 7687small10 GB at /data

When to use it

  • The agent's memory is relationships, not paragraphs: which service calls which, which customer hit which bug, which migration depended on which table. A graph database can answer "what's connected to this?" directly; a markdown note can only be re-read and re-summarized.
  • You want the agent to write facts as it learns them, in Cypher, and query them back later in the same session or a different one — structured, not prose.
  • You are prototyping a recommendation, fraud, or dependency-graph feature and need a real Bolt endpoint, not a mock.

The volume is 10 GB, mounted at /data, so a stopped briq keeps its graph.

Tips

  • Auth is disabled. This recipe sets NEO4J_AUTH=none, the image's own documented value for running without credentials. There is no public endpoint until you call briq_expose, and when you do, use mode: "token" — never "public" — since anyone with the URL can read and write the graph.
  • Talk to it over Bolt. NEO4J_BOLT_URL works with the official neo4j-driver in any language, or cypher-shell via briq_exec.
  • Browse it visually. NEO4J_HTTP_URL serves the Neo4j Browser. briq_expose port 7474 with mode: "token" to hand a human a link into the same graph the agent is writing to.
  • Seed it from the agent, not a file: briq_exec with cypher-shell and a CREATE/MERGE statement per fact, as the agent learns it.