Kinegraph does not ship a Neo4j password. Generate a unique value and keep it only in the untracked .env file or a production secret manager:

openssl rand -base64 32
docker compose --env-file .env -f infra/docker-compose.yml up -d

infra/docker-compose.yml fails closed when NEO4J_PASSWORD is absent. The application also requires at least 16 characters.

The historical development password was committed to version control. Removing it from the current tree does not revoke it or erase Git history. Rotate the password in every Neo4j deployment that ever used it, update the corresponding secret store, restart dependent services, and invalidate any derived snapshots or credentials. Rewriting public Git history is a separate repository-owner decision and does not replace rotation.

LLM-generated Cypher is treated as untrusted input. Only a single read-only MATCH or OPTIONAL MATCH statement with RETURN is accepted. Comments, multiple statements, procedures, administrative clauses, write clauses, and LLM-provided pagination are rejected. Kinegraph executes the validated query in Neo4j read access mode and applies its own parameterized result limit.

Production should additionally use a Neo4j account whose database privileges are read-only for retrieval workloads. Application validation is defense in depth, not a replacement for database authorization.

Allowed browser origins are explicit and comma-separated:

CORS_ALLOWED_ORIGINS=https://app.example.com,https://admin.example.com
CORS_ALLOW_CREDENTIALS=true

Wildcard origins cannot be combined with credentials. The development default allows only the local UI origins and disables credentialed cross-origin calls.