A record nobody can rewrite.

Every sandbox, command, approval, secret and change is written to an audit log where each entry is chained to the one before it, so an edit shows.

Govern › Audit log

Audit log

Every sandbox, command, approval, secret and change is written to an audit log where each entry is chained to the one before it, so an edit shows.

Audit loghash-chained · export
TimeWhoActionEntry
14:02:11maya via Claude Codesandbox.create9a1c3f
14:02:31maya via Claude Codetool.blockedd07a91
14:03:20lee@acme.devapproval.grantede2f5b8
14:04:02schedulerbuildhost.release5a6e17
Covers
Runs, agent sessions, policy, approvals, secrets, sign-ins, changes
Integrity
Hash-chained; an edit or a gap shows
Export
A checked file per period
Retention
By plan

How it works

What happens, in order.

01Record

Each action becomes an entry with who, what, where and when.

02Chain

Each entry carries the hash of the one before it.

03Check

Verify the chain and export a period as evidence.

Which plans

A basic audit log comes with every plan. Exporting it comes with Team and Enterprise.

See pricing →

Give every agent
a box of its own

Start free with 100 vCPU-hours a month. Upgrade when your agents need more.

A Firecracker microVM for every runNo network by defaultPause and resume with state keptVault keeps secrets out of promptsSSO, roles and audit logBring your own cloudWorks over MCP and the CLI