About MoorAI
MoorAI is open-source (MIT), on-device guardrails for AI coding agents. Nothing leaves the machine. It reviews what developers send to AI coding agents, and what those agents read, run and reply, on the device, before anything is exposed.
The problem
AI coding agents don’t just read what a developer types. They read files into their context (a stray .env, for example), call MCP tools with whatever arguments they were given, and reply with whatever the model generates. Reviewing prompts alone misses most of that.
The usual way to inspect this traffic is to send the prompts to someone else’s servers. MoorAI is built not to make that trade: secrets, personal data and source code are checked where they already are, on the developer’s machine.
How it works
- On-device checks. A small native host wraps the agent’s terminal, and a local detection engine checks prompts, file reads, tool calls and outputs against a 67-threat matrix in 17 categories, plus content rules and detector packs your organization defines. All of it runs on the device.
- Policy actions. Per policy, MoorAI can coach, alert, block, require a justification, or end the agent session.
- Content-free signals. If a device is enrolled in a management console, the console receives a category, a risk level and a keyed one-way hash. It never receives the prompt, the file or the matched text.
- No account required. The community edition runs standalone, with local policy control.
The exact fields a console receives are listed on the trust page.
Open source, so you can check
The on-device agent is open source under the MIT license, including the whole detection and reporting path. You don’t have to take the “nothing leaves” claim on trust: read the code, run it, and watch what it sends.
Open core
MoorAI is open core. The agent is MIT. The management console is a separate product, source-available under the Elastic License 2.0: it adds a multi-tenant dashboard, SSO, fleet policy, and content-free compliance exports.
Security disclosures
When we find a security-relevant defect in MoorAI, we publish an advisory with a vendor-assigned identifier (MOORAI-YYYY-NNN). These are not CVE identifiers. To report a vulnerability, follow the disclosure policy or use the contact listed in security.txt.
Contact
Questions about MoorAI, pricing or a deployment? Send us a note through the contact page.