01 / SurfaceFind the AI you weren’t told about.
Read supported local signals to find AI apps, coding agents, local models and MCP connections. Discovery needs no per-tool API integration, traffic interception or execution of the tools it finds.
- See work, personal or unknown account context.
- Identify credential presence without reporting the secret.
- Connect tools to declared repositories and MCP access.
Explore the 21 signals ↗
02 / MonitorInspect where the request begins.
For supported enforcement paths, a local TLS gateway reads the request on the device and re-encrypts forwarded traffic. Policy checks use deterministic rules and trained classifiers, with no language model required.
- Check prompts for sensitive content before sending.
- Evaluate the interaction against your published rules.
- Keep local inspection separate from conversation collection.
Understand the data boundary ↓
03 / GovernMake the policy a decision.
Let approved work continue. Warn, redact or block supported interactions when a rule applies. The action follows the policy your organisation publishes.
✓ Allow! Warn / redact× Block
Request controls are distinct from stopping an application or removing it. App removal needs an administrator; coverage depends on the tool and operating system.
04 / EvidenceKeep the reason behind the result.
Build a versioned, redacted record on the endpoint. Evidence is saved locally, then delivered through an encrypted outbound route to the platform.
- Link the decision to the policy version behind it.
- Give teams reviewable findings and evidence for audits.
- Retain unknown results when a check cannot complete.
Framework mappings support control reviews; they do not establish certification or guarantee compliance.
Follow the evidence ↗