Frequently asked questions

Yes — it supports your obligations, without claiming to certify them. The EU AI Act expects organizations to know how AI is used, keep records, and apply human oversight. MoorAI produces content-free usage records — a category, a risk level, and a keyed one-way hash per event — plus a control-mapping to the frameworks auditors reference (NIST AI RMF, ISO/IEC 42001, OWASP LLM Top 10, MITRE ATLAS). Its coach / alert / block / require-justification flow is human-oversight enforcement at the point of use. That gives you evidence and an audit trail that support and evidence EU AI Act obligations — MoorAI does not certify, guarantee, or by itself make you compliant, and it is not legal advice. It's control-mapping and records, not certification.

MoorAI lets your team use AI tools while keeping your company's information out of them. It runs on each computer, checks what an employee is about to send to an AI tool like ChatGPT, Claude, or Copilot, and warns or blocks before anything sensitive — source code, passwords, customer data — leaves the machine. Security teams get to see and control what's happening without ever reading what people type. The community version is free and open source.

It can. Depending on the tool and the plan, anything sent to an AI service may be stored, reviewed by humans, or used to train the model — which can surface it to other users as answers. Free and personal accounts are the biggest risk. That's exactly the gap MoorAI closes: it catches sensitive company material before it's sent, so it never reaches a service that could keep or leak it.

Three steps. First, the prompt is reviewed on the device — checked locally against policy, a 67-threat matrix plus content rules — and the content never leaves the machine. Second, MoorAI coaches, alerts, or blocks, per policy, per tenant, per device. Third, a central web console shows posture, device inventory, alerts, and compliance, built from redacted metadata only.

Redacted, content-free signals — a category, a risk level, and a keyed one-way hash — never the actual prompts or conversations. The console gives teams posture and compliance without exposing what anyone typed.

MoorAI is designed to sit in front of the AI agents teams already use, including Claude, Codex, and GitHub Copilot. Depth differs by agent, and it's worth being precise: on Claude Code, MoorAI hooks the agent's PreToolUse path, so it can actively block a file read or an MCP tool call that would pull secrets or PII into the model's context. Codex and Copilot CLI expose no equivalent deny hook, so on those the same checks run but are detection-only — you get the alert and the record, not the block. Prompt-stage review works across all of them.

Most guardrails only look at what a person types. But a coding agent reads files on its own — and a single .env can carry a dozen live credentials straight into the model's context without anyone typing a character. MoorAI hooks the agent's Read tool, plus conservative file-reading Bash, and inspects mcp__* tool-call arguments, so that content is checked before it becomes context. It runs on-device, reports content-free, and fails open — if the check can't run, work continues. This is governance, not a sandbox: it's built to stop mistakes and give you an accurate record, not to contain a determined attacker with local code execution.

By default, no. Review happens on the device and content stays there — that's the key difference from cloud DLP: MoorAI keeps the actual prompts and conversations local, and only redacted metadata is shared upstream. Two exceptions you control: an administrator can enable a capture tier, which stores the matched text it was turned on to collect, and on platforms without built-in OS text recognition a pasted image is sent to your own AI provider to be read — direct from the device, never through MoorAI.

The community agent runs standalone with local policy control and no account required — it's open source under MIT, for macOS and Windows (Rust + a Tauri native host and webview detection core). Centralized fleet management — a multi-tenant console, SSO, and compliance reporting — is a separate, proprietary MoorAI management server.

The community agent is open source under MIT and runs standalone with no account required. The code is on GitHub. The centralized management server is a separate, proprietary product.