security & sovereignty

Nothing leaves. That's the architecture, not a setting.

Krenox deploys entirely inside your AWS account. Telemetry, code context, incident memory, and AI inference all stay behind your boundary. There is no toggle to get this wrong.

your AWS account vpc · your region · your KMS keys
collectors Read-only. K8s, VMs, eBPF.
telemetry store Your S3, your keys.
detection Deterministic engines.
evidence bundles Assembled and stored here.
AI inference Your AWS Bedrock, your model choice.
incident memory Yours. Downloadable from your dashboards.
krenox (vendor) Ships signed update artifacts and receives operational health pings: version, uptime, license.
→signed updates, inbound only
⊘telemetry egress: 0 bytes
⊘code context egress: 0 bytes
⊘prompts & inference egress: 0 bytes
least privilege

Read-only by construction

The IAM role Krenox runs under contains no write actions; you can audit the policy before you grant it. Collectors observe; they never mutate. The only artifacts Krenox produces are findings in your account and pull requests in your repository.

✓No kubectl write verbs, no SSH, no exec
✓Repo access limited to branch + PR creation
✓Every API call it makes is in your CloudTrail
"Effect": "Allow",
"Action": [
  "eks:Describe*", "eks:List*",
  "ec2:Describe*",
  "cloudwatch:Get*", "cloudwatch:List*"
]
// no Create*, no Update*, no Delete*.
// the full policy is published. Read it first.
Your models, your terms

Inference runs against Bedrock in your account: you choose the model, your data-use agreement with AWS applies, and prompts containing your telemetry never transit our systems. Inference cost lands on your AWS bill, visibly, not hidden in ours.

Action only via pull requests

Krenox holds no credentials to your runtime. Its one write path is a pull request your team reviews and your CI/CD ships. Reviewable, auditable, reversible: the same guarantees you demand of every engineer.

Exit on your terms

Your incidents, findings, and reports download from your dashboards. Uninstall is one command. There is no data hostage scenario, because your data never left your account.

no shared brain

No cross-customer learning. Ever.

What Krenox learns from your incidents stays in your account and improves only your diagnoses. Nothing about your systems (not patterns, not embeddings, not "anonymized aggregates") feeds anyone else's deployment. Your operational history is a competitive asset; we treat it that way.

early access, honestly

Ask us the hard questions

We're an early-stage product and we'll answer your security questionnaire directly, including the places where the honest answer is "not yet." The architecture above is the part we will never compromise on; certifications and audits follow from it, on request we'll share where each one stands.

Send us your questionnaire →