Observe. Detect. Explain. Propose. Remember.
Five stages, all inside your AWS account. Read-only observation in, pull requests out. Nothing else crosses the boundary.
Kubernetes, VMs, and kernel-level eBPF. Installed in an afternoon. No re-instrumentation, no agents in your request path.
Latency drift, error-rate change, saturation, all caught by math before users feel them. No model in this loop.
Runs on your AWS Bedrock, over a bounded evidence bundle assembled in your account. Every claim cited.
Where Krenox is confident, a proposed fix arrives in your repo. Your team approves; your CI/CD ships. No credentials to your infrastructure.
Every outcome (merged, dismissed, rejected) becomes evidence for the next investigation. In your account only.
How the AI actually works
Krenox draws a hard line between what is deterministic and what is a model, and gives the model a very short leash.
Deterministic engineering watches your systems: explainable, testable, never hallucinated. Alerts fire from math, not from a model's mood. You can read the rule that paged you.
When something breaks, the AI investigates a bounded evidence bundle assembled inside your account. Every causal claim cites its evidence; uncited claims are rejected before a human sees them. Low confidence is stated plainly, and the system names what's missing and how to fix that.
No credentials to your infrastructure. Your team approves; your pipeline ships. Every action is reviewable, auditable, and reversible, and a closed PR is a lesson, not a failure.
"An AI that says 'I don't know, and here's what would help me know' beats one that's confidently wrong."
From first symptom to reviewed fix
Krenox learns your systems and your history
Every resolved incident, merged fix, and dismissed false alarm becomes institutional memory in your account. The tenth similar incident is diagnosed with the first nine as evidence. Rejected theories aren't re-proposed. It knows who owned a service at the moment something broke, not just today.
An afternoon, not a quarter
One Helm chart for Kubernetes, one lightweight agent for VMs, one read-only IAM role. No SDKs to add, no code changes, no traffic to reroute. If you decide Krenox isn't for you, removal is just as fast, and your data goes with you, downloaded from your dashboards.
Read the security architecture →