Skip to main content

Configuration reference

Every Z3rno surface beyond the always-on base (store / recall / forget / audit / sessions / api-keys / conversations / limits / graph) is opt-in via a gating flag. Default values produce a working local-dev stack against docker-compose.dev.yml; flip the gates as you light up Forge / Ingest / Refine / forget-proof / OpenTelemetry / etc.
Source of truth: z3rno-server/src/z3rno_server/config.py. Variables names are case-insensitive; values are read from environment or .env file. As of v0.20.0.

Database

Valkey / Redis

Embedding

Authentication

Rate limiting

Server / CORS / logging

Celery backpressure


Phase A — Forge (DISTILL_ENABLED)

The Forge pipeline is dormant unless DISTILL_ENABLED=true. With the flag off, /v1/distill is not registered and z3rno.forge_distill self-rejects.

Phase B.1 — Ingestion (INGEST_ENABLED)

/v1/ingest, /v1/ingest/file, /v1/datasets and the z3rno.ingest_run worker register only when INGEST_ENABLED=true.

Phase B.2 — Multimodal / S3 / Tavily / Playwright

Each capability flips on independently — multimodal doesn’t require S3, Tavily doesn’t require multimodal, etc.

Multimodal (image + audio)

S3 storage backend (STORAGE_BACKEND=s3)

Tavily web search (registers /v1/ingest/search)

URL loader Playwright fallback

Phase C — Retrieval

Phase D — Refine / Ontology / Codegraph (REFINE_ENABLED)

/v1/feedback, /v1/refine, and the z3rno.refine_run worker register only when REFINE_ENABLED=true.

Refine

Ontology grounding (Forge integration)

Codegraph (Ingest integration)

Phase F — Differentiation

Memory-tier routing

Compliance-graded retrieval (PII redaction)

Forget-with-proof

Distributed worker backends

Phase G — Agent-native

Usage telemetry + budgets

Zero = no cap (default). Non-zero values trip BudgetExceededError on Forge / refine pre-flight; the job is rejected before any LLM/embedding work. Per-tenant overrides land via PUT /v1/tenants/me/budgets (v0.20.3). See Components → z3rno-server for the endpoint.

Cross-tenant admin (v0.22.1, managed-hosting)

The cross-tenant surface is off by default and stays invisible (not in the OpenAPI spec) until both vars are set. See the Managed-hosting guide for the ops playbook.

Recall counter batching (v0.22.0)

Off by default; flip on once your deployment’s benchmark numbers ratify the win. The single-process laptop bench delta is +2-4% ops/sec at high concurrency with a -19 to -25% p99 reduction at 20-30 concurrent recalls.

OpenTelemetry tracing

v0.20 — Operator polish

NOTIFY/LISTEN audit drain (v0.20.2)

Audit-drain tunables (read by the engine; surface them through chart beat.audit.*)


Reference