OperativeOps

Your building. Your models. Your data.

OperativeOps is a self-hosted AI operations platform. It answers from your documents with source citations, acts through your systems over MCP, and writes an audit entry for every model decision.

DOCKER · ON-PREM · AIR-GAPPED
YOUR PERIMETER — IHR PERIMETEROperativeOps coreretrieval · agents · policydocker compose upModel runtimeOllama / vLLM · your GPUsVector storeembeddings never leaveAudit ledgerappend-only · per decisionMCPSlackJiraSalesforceNotionConfluenceHosted model APIoptional · off by defaultegress gate · TLS · loggedthe only line that may cross.Air-gapped: it does not exist.
FIG. 01 — DEPLOYMENT TOPOLOGY · NOTHING ELSE CROSSES

OPERATIVEOPS

SHEET 01 · REV 01

Installed inside.
Stays inside.

Try the demoRead the datasheet

CONNECTS OVER MCP: Slack · Jira · Salesforce · Notion · Confluence

AIR-GAP MODE: NO OUTBOUND CALLS

FIG. 02 — REQUEST PATH

From question to cited answer.

  1. 01

    Question

    From Slack or the web UI, in your language.

  2. 02

    Retrieval

    Search over your documents, in your own vector store.

  3. 03

    Answer + sources

    Every claim carries its source path.

  4. 04

    Action

    Optional, permission-checked, over MCP.

  5. 05

    Audit entry

    Written append-only. Always.

FIG. 03 — PERMISSION SCOPE

Agents bounded by permission, not by promise.

Each agent has its own scope: what it reads, what it may do, and what it can never touch. Scopes are granted by your admin and every grant is itself an audit entry.

Operations

READS
Confluence · Notion · Slack
ACTS
create Jira tickets · post summaries
NEVER
Salesforce · finance data

EVERY ACTION → AUDIT LEDGER

Engineering

READS
Jira · Confluence · repos via MCP
ACTS
triage issues · draft runbooks
NEVER
HR records · CRM

EVERY ACTION → AUDIT LEDGER

Analytics

READS
Salesforce · warehouse exports
ACTS
scheduled reports, with citations
NEVER
write access, anywhere

EVERY ACTION → AUDIT LEDGER

FIG. 04 — THE RECORD

The record, not a screenshot.

AUDIT LEDGER — LIVE FRAGMENT
TIMEACTORACTIONSCOPERESULT
09:41:02.114agent.opsretrieval.queryconfluence://ops-handbuch/*4 sources
09:41:03.590agent.opsanswer.citejira://OPS-1182 · sha 9f3a71clogged
09:44:19.007admin.kmpermission.grantagent.finance → salesforce.readgranted
09:47:55.302agent.engaction.executejira://create · OPS-1183logged

Append-only. Exportable. Written whether or not anyone is watching.

ANSWER — WITH ITS SOURCES

Q: How many vacation days carry over into next year?

Up to 10 days carry over and must be taken by 31 March. Approval goes through your team lead in HR-Portal.

  • [1] confluence://hr-handbuch/urlaub.md §4
  • [2] notion://policies/carry-over-2026

FIG. 05 — DATASHEET

Runs where you say.

A

Docker Compose

One host. Evaluation to small-team production, running in minutes.

B

On-prem cluster

Kubernetes on your hardware, in your region, behind your firewall.

C

Air-gapped

No outbound calls. Local models only — Ollama or vLLM on your GPUs.

MODEL PROVIDERS: OpenAI · Anthropic · Ollama · vLLM

SWITCHABLE PER AGENT. Your keys, your endpoint.

FIG. 06 — REGULATION

Built for European regulation.

Not a badge wall — a control mapping for each framework, written for the people who have to sign it.

See it running in your own terminal.

$ docker compose up—running in under 10 minutes

Try the demoTalk to engineering