Four gates before any model sees your data
Every AI request passes a default-deny egress gate, masking, a per-tenant rate limit and an audit record — in that order. Local endpoints on your own network are recorded as zero-egress.
Governed AI
The kymeer AI analyst reads the evidence around an alert, explains what it sees and recommends next steps beside the records it relied on. It is advisory by design: response stays with your analysts and your approval policy.
How it works
Every AI request passes a default-deny egress gate, masking, a per-tenant rate limit and an audit record — in that order. Local endpoints on your own network are recorded as zero-egress.
AI-drafted detection rules are backtested on your recent events with the production engine, and stay inactive until a person approves them.
The analyst can draft a response playbook. Drafts are never saved automatically: a person reviews and publishes them.
Specifications
| Role of AI | Advisory: explains, recommends, drafts |
|---|---|
| Model options | Local OpenAI-compatible model (Ollama, vLLM, llama.cpp) · Anthropic · OpenAI · OpenRouter · Unoblox |
| Zero-egress | Local endpoints audited as zero-egress |
| Data protection | Default-deny egress · built-in masking with numbered stand-ins · per-tenant token budgets |
| Keys | Provider keys per tenant, AES-256-GCM encrypted, set by a platform administrator |
| Kill switch | Platform-controlled; effective within 60 seconds |
| Audit | Every AI call recorded |