Integrations

Events and proofs out, and checking a proof offline.

Updated

krupiq fits around what you already run. Its output is events and proofs you can send anywhere.

Events out

Engagement events and epoch summaries are available as JSON, for your SIEM, your ticketing system or a spreadsheet. Each event carries the deployment, the epoch and the proof reference it belongs to.

Proof verification

krupiq-verify checks a deployment’s record of epochs offline, with the deployment’s public key:

krupiq-verify --process record.jsonl --key <public key, hex>

It exits 0 when every epoch verifies, 1 when one fails or the record is empty, and 2 for bad arguments. Without --key it can only say the record is consistent with itself, and exits 3.

What is deliberately missing

There is no webhook into your production systems. krupiq on each machine presents and watches the decoy; your real sessions are counted, never recorded.