Who changed what, and when
A durable record of platform mutations across projects, users, resources and credentials.
- Actor, action, resource
- Across every resource type
- Survives the session
Every mutation, attributed
Creating a database, rotating a credential, deploying an application, granting a permission. Each entry names the actor and the target.
API keys are actors too
Automation shows up in the audit log the same way a person does, so an unexpected change is traceable to the integration that made it.
Separate from container logs
Application stdout is a live stream over realtime. The audit log is a durable record of control-plane actions. Different questions, different tools.
Read access is a permission
The audit log is only useful if it is trustworthy, so who can read it is itself controlled.
What it is not
It is not a data-change log. Row-level history inside your own tables is something you design with triggers or an append-only table, because only you know which changes matter.
Build the whole backend in one project
One plan, one dashboard, one command line interface. PostgreSQL, applications, functions, storage and realtime.