Neo4j & graph store

Repository topology and risk context persist as graph snapshots alongside Postgres audit records.

Repository topology and risk context persist as graph snapshots alongside Postgres audit records.

Local setup

  • pnpm run docker:up starts Neo4j and Postgres via docker-compose.yml.
  • Default Bolt: bolt://localhost:7687, user neo4j, password from compose file.
  • Graph writes occur during audit ingest when NEO4J_URI is reachable.
Local dev

Set NEO4J_DISABLED=1 only for temporary local troubleshooting when Neo4j is unavailable. Audits still run, but graph context is reduced.

Start local graph + Postgres
pnpm run docker:up

Environment variables

  • NEO4J_URI: Bolt connection string (Aura or local).
  • NEO4J_USERNAME, NEO4J_PASSWORD: credentials.
  • NEO4J_DISABLED=1: skip graph persistence during local development troubleshooting.

Runtime behavior

  • Ingest builds nodes/edges for repo tree and CI topology.
  • GET /api/audits/:id/graph returns snapshot for Workflow Canvas.
  • Specialist agents consume graph payload in swarm lanes.

Disable graph

  • When Neo4j is down, set NEO4J_DISABLED=1 to avoid connection errors during local development.
  • Audits complete without graph artifact; canvas graph panel shows awaiting state.
  • Production: keep Neo4j configured and treat graph persistence as part of the core audit path.

View source on GitHub

Related links

Announcement updates version release today!

ReleasesPrivacy
Terms