Compliance
The evidence trail, an append-only audit log of organisation-level change, plus the retention and privacy controls that decide how long data lives and how much of it is kept.
The Compliance pillar is the evidence side of the product: what changed, who changed it, how long data is kept, and what content is retained.
Audit log
Key rotations, invites, role changes, ownership transfers, sign-in attempts and
operator actions are written to an append-only log scoped to your organisation.
It answers “who changed this, and when”. Admins read it from the dashboard or
GET /audit-logs. Entries carry no TTL and are never aged out. See the full
audit log reference for the entry shape, what is and is
not captured, and how to page through it.
Retention
Events and traces carry a TTL and are aged out on your retention schedule by the cron Lambda. The raw retained events are the single source of truth; analytics and search projections are derived and rebuildable. See retention.
Privacy
The telemetry policy governs how
much prompt and tool content is captured, defaulting to metadata_only.
Credential-shaped keys are always redacted. The policy applies before an event is
persisted and again before it is delivered anywhere.
Related
- Audit log
- Events model, retention and the privacy boundary
Govern
The controls that bound and gate LLM traffic — governance policies that rewrite or reject non-compliant requests, spend policies, quotas, model allow-lists, API keys, members and SSO — plus environments, the telemetry policy and export destinations.
Connect
Get data into axonpush and connect a coding agent. The Integrations page has the endpoints, headers and snippets for the SDKs, OpenTelemetry, Sentry and webhooks; MCP wires an agent in over the Model Context Protocol.