Tell your auditor what your agent did. Prove it independently.
Whatever governs your agents emits decisions; Krynix holds them in independent, tamper-evident custody and independently re-checks what your enforcer claimed — because an enforcer can't audit itself. Roll it up into an evidence bundle on demand: who decided what, when, against which policy, which approval chain, and where an enforcer's claim and the record disagree. Export, hand off, move on.
The pain
Your auditor asks. Your team writes SQL for a week.
SOC2 wants a sample of automated decisions and the controls around them. HIPAA wants proof PII never reached unauthorized models. The EU AI Act wants risk-classified logs and human oversight evidence. None of it is in one place. Most of it isn't structured. Some of it doesn't exist yet.
Stitching it together for every audit is the kind of work that absorbs an engineer for a week and doesn't scale to the next audit.
What Krynix does
One command. One bundle. Auditor-ready.
Every decision Krynix holds is a structured event with policy reference, agent identity, decision, approver chain, and a redacted payload reference — plus Krynix's own independent re-check and any discrepancy it found. Events accumulate as you ship.
When the auditor asks, you scope by date range, agent, policy, or risk class, then export. The bundle is a portable directory with a signed manifest. The signature is verifiable without Krynix running — your auditor can verify the bundle is intact on their own machine.
Evidence bundle — krynix export --range 2026-Q1 --agents support-* --out evidence/
evidence-2026-Q1-support/
├── manifest.json # bundle index + period + scope
├── manifest.sig # Ed25519 signature over manifest.json
├── policies/ # policy versions in effect during the period
│ ├── redact-pii.v1.2.yaml
│ └── refund-approval.v2.0.yaml
├── decisions/ # all governance events, partitioned by day
│ ├── 2026-01-15.jsonl
│ ├── 2026-01-16.jsonl
│ └── ...
├── approvals/ # approval chains with approver identity + timestamp
│ └── refund-over-500.jsonl
└── README.md # how an auditor verifies the bundleWhat an auditor sees
- Period
- 2026-01-01 → 2026-03-31
- Agents in scope
- support-agent-prod, support-agent-staging
- Decisions recorded
- 184,231
- Approvals routed to human
- 412
- PII redactions
- 27,891
- Manifest signature
- verified · key id 7f1a…b3d2
Mock — evidence export ships in W9 with the paid governance dashboard.
Frameworks & insurers Krynix evidence maps toward
SOC 2 Type II
CC7.2, CC8.1
EU AI Act
Art. 12, Art. 14
FINRA / SR records
Retention + audit trail
AI insurability
AIUC-1 · evidence-backed
Want to try Krynix on your stack?
Request early access