Every run leaves a record you can show.
You do not have to set anything up to get this. Each run keeps its steps, tokens, and cost. The audit log is hash-chained. When someone asks what happened, you open it.
Built in. Nothing to configure.
Every step, with its cost
Inputs, outputs, status, tokens in and out, and dollars, per step and per run. Batch runs export as a file.
Hash-chained and verified
Each entry carries a hash of the one before it. A scheduled sweep re-verifies the chain so a silent edit would show.
A control library you can adopt
Controls drawn from SOC 2, HIPAA, and the EU AI Act today, with ISO 27001, ISO 42001, NIST AI RMF, and GDPR listed as frameworks to map next. Adopt the ones that apply and attach runs as candidate evidence.
Redact or mask by rule
Per workflow, choose how names, emails, phone numbers, account numbers, and card numbers are handled, and see when a rule fired.
Kept for a year, then gone
Run and audit data are swept after a year, analytics after two. Deleted projects purge after thirty days.
Spend you can see
Cost per run, per workflow, and per month on the costs page, from the same numbers in the run records.
Three steps, then it runs.
- Run the workflowThe record is written as it runs. There is nothing to enable.
- Open the runThe run inspector shows each step. The audit log shows who changed what around it.
- Show it to whoever askedExport the audit log, or attach the run to a policy as evidence for a reviewer.
Meets your team where it already works.
One workspace, the rest of the job.
See it on your stack.
30 minutes with our team. We'll walk you through governance, audit, evals — and answer everything procurement will ask. Bring your own NDA; we'll sign in 24 hours.