How OpsCodex uses AI
AI in OpsCodex is an optional assistant that proposes — a human always approves. It uses the model provider and key you choose, and it never stores the content of your prompts.
AI proposes, humans approve
Every AI output — a drafted model, a review suggestion, generated documentation — is a proposal. Nothing moves through the approval → review → publish workflow, and nothing is published, without an authenticated human signing off. There is no fully-automated path from a model's output to an approved process.
Bring your own key, your choice of provider
OpsCodex does not bundle a model. An administrator configures the provider and API key — Anthropic, OpenAI or Google, or a private/self-hosted endpoint. Requests are made with your own key against your own provider account, so the provider relationship and its data terms are yours. In an on-premise deployment the request goes directly from your instance to the provider you chose; it does not pass through any service we operate.
Your data is not used to train models
OpsCodex trains and fine-tunes no models and adds no learning loop of its own. Whether the provider you configure may use API inputs is governed by your own contract with that provider, not by us. On the major providers' API and enterprise tiers, training on API inputs is off; consumer and free tiers can differ, which is one reason OpsCodex expects an organisational API key rather than a personal account.
What we store — and what we don't
OpsCodex persists AI telemetry only: which provider and model ran, token counts, status and timing, and a one-way hash of the prompt used for change-detection. We do not store the text of your prompts or the model's responses — not in the database, not in application logs. AI telemetry is tied to its process draft and is deleted together with it.
Turn it off
AI is inert until an administrator configures a provider key — the deterministic governance product works fully without it. AI-assisted features are opt-in, and you configure exactly the one provider you permit; no other is reachable.
Private & air-gapped inference
Because the provider endpoint is configurable, you can point OpsCodex at a private, regional or self-hosted model — Azure OpenAI, an internal gateway, or your own hosted model — so that prompts never leave your perimeter.
Auditability
Each AI invocation records a telemetry entry — when AI ran and how much — giving you a reviewable trail without exposing any content.
Questions about AI data handling? Email [email protected]. See also our Security & trust page.