Platform / Audit Log
A record of everything, written by the platform.
Every Maestra app writes an append-only audit trail it never has to implement. Sign-ins, permission changes, data reads and writes, deploys, and every method call are recorded by the platform as structured, meaningful events, across the workspace and inside each app, ready to export to any SIEM.
What gets recorded
The log captures who did what, to which record, through which interface, and whether it was allowed. People, agents, and API callers all go through the same door, so they all appear in the same record.
Semantic, not just technical
Most logs tell you a POST hit an endpoint. Maestra knows the endpoint is approveInvoice, that the record is invoice 2231, and that the caller held the approver role. That is the difference between a log you can grep and one an auditor can read.
Append-only by construction
- Immutable
- Events are written once and can’t be edited or deleted by builders or admins.
- Complete
- Written by the platform at the edge, so an app can’t forget to log or choose not to.
- Retained
- Kept for your plan’s retention window, with longer retention available.
Export to any SIEM
Events export in OCSF, the open schema most security tools ingest natively.
The guarantees
- Every interface
- Web, API, MCP, voice, email, and scheduled jobs all write to the same log.
- Every actor
- People, understudies, and API keys are recorded with the same fields.
- Every app
- One log across the workspace, filterable by app, person, or method.
Start building on Maestra.
Everything you just read is standard in every app, running from the first deploy.
Start building →← Back to the Platform