Platform
Send every event to your own log system
Stream audit events to the SIEM you already use, so security sees review activity next to everything else.
Destinations
- Security data lakeHTTPS · signed batchesLive
- SIEM collectorHTTPS · 12,480 sent todayLive
- Archive bucketDaily filesPaused
One event
- Decision made
- Signed and queued
- Delivered, receiver verified
- Retried if it failed
Event
{ type: 'review.decided', agent: 'refund-agent', outcome: 'approved' }Why it matters
What audit streaming changes
- Stream audit events to the SIEM you already use.
- Security sees review activity beside everything else.
- Events carry hashes, not your content.
- Review activity sits in its own silo.
- Security cannot see it next to everything else.
- Exports are a manual job.
The resultOne place to watch everything.
What you get
Audit streaming, in practice
Your tools
Events land where your security team already looks.
Every event
Decisions, changes and refusals.
Verified at both ends
The hash chain lets you check what arrived.
How it works
Step by step
- 1
Event happens
A decision, a change, a refusal.
- 2
Queued safely
Written together with the change, so none are lost.
- 3
Sent on
To your log system.
- 4
Checked
Against the chain.
Questions
About audit streaming
Can events be lost?
Events are stored with the change that caused them and sent on by a queue that retries.
Is it included?
On Pro and Enterprise.
Next
Works well with
Know what your agents did.
Start free. Guard your first agent in a few minutes, and keep a record anyone can check.
- Free plan, no card
- Signed, chained decisions
- Checked offline, without us
Signed decision
- Decision
- Approved, 2 of 2
- Action
- refund.issue, £540
- Rule
- Two reviewers must agree
- Sealed
- 14:09, key 7f2c
- Hash
- 5be2…7c44
Checked on your own machine
- Signature matches the public key
- Decision is in the log
- Every link before it adds up