When an internal tool touches operational data, the question after an incident is what changed and who did it. Relpin captures row-level audit in the data model by default.
tenant roles hold SELECT + INSERT only · captured by AFTER triggers
Audit-ready means evidence is part of the data model, not an afterthought. Relpin records field-level changes with the actor and audits lifecycle and promotion decisions too.
AFTER INSERT, UPDATE, and DELETE triggers on every user table capture field-level before and after diffs together with the actor. The audit table is append-only, enforced by database privilege: tenant roles get SELECT and INSERT only.
Control-plane, lifecycle, and promotion mutations are recorded alongside data changes, so operators can tie a record change back to a specific governed release decision.
The audit feed is a cursor-paginated SQL pull. Relpin does not provide realtime audit streaming, SIEM integration, or outbound webhooks, and does not hold compliance certifications. Audit-ready describes the recorded evidence, not a certification.
All category guides for internal tool builders, AI agents, low-code limits, and production data.
Audit TrailHow Relpin records governed operational changes.
Production Data Internal ToolsWhy audit matters when internal tools touch real data.
Governed Internal ToolsHow audit fits the broader governance model.
Platform GlossaryDefinitions for content-addressed releases, audit, and promotion.
In Relpin, audit-ready means row-level audit is part of the data model. Database triggers record field-level before and after diffs with the actor, the audit table is append-only by privilege, and lifecycle and promotion mutations are audited too.
No. Audit-ready describes the recorded evidence in the data model. Relpin does not claim compliance certifications, and the audit feed is a cursor-paginated SQL pull rather than realtime streaming.