For Platform & Engineering Teams

One policy + audit layer under every AI coding tool your team runs.

Claude Code, Cursor, Codex CLI, Hermes, Claude Desktop, Continue — each captured through its own native path: an MCP tool proxy, the vendor's official hooks API (prompt + reply, no MITM), or the LLM egress broker. MCP and broker tool calls hit a policy gate — allow, deny, redact, or route to a human; hooks add full prompt/reply content and a local deny gate on dangerous shell commands. The hash-chained audit is on by default. Runtime intervention catches drift, hallucination, tool loops, and cost runaway mid-stream — an operator reviews and approves the fix from Slack or the desktop tray.

This is the Build plane — governing how your developers build with AI. Need to govern how your business operates with AI? See the Run plane →

The integration in one block of JSON

For MCP-speaking hosts (Claude Desktop, Continue), drop one block into the MCP config, relaunch, and tool calls route through the policy gate into the audit chain. Local agents are one command each — airgov_daemon install-cursor-hooks / install-claude-hooks / install-hermes-hooks — and Codex + non-MCP automators route through the egress broker. The full template — org token issuance, host-specific variants, onboarding scripts — ships inside the customer workspace after organisation verification.

{
  "mcpServers": {
    "proofpane": {
      "command": "proofpane",
      "args": ["mcp"],
      "env": {
        "PROOFPANE_ORG":   "<your-org>",
        "PROOFPANE_TOKEN": "<issued-token>"
      }
    }
  }
}

What the audit log looks like

Cryptographically chained. One event per tool call, decision, approval checkpoint, or redaction — scoped per tenant so cross-org tampering is structurally detectable. Every event is linked to its parent run so the entire decision tree is navigable in the operator UI.

{
  "event_type":  "tool.deny",
  "actor":       "agent",
  "tool":        "shell",
  "decision":    "deny",
  "reason":      "Destructive operation against shared infrastructure",
  "approval":    "required, not granted",
  "vendor":      "<host>",
  "verifiable":  true
}

Why engineering teams pick us

The features above are the surface. These three are the substrate — what holds up when you scale past one team or one agent vendor.