A record of who did what,
built before you need it, not after
The question that actually matters after something goes wrong is 'who did this and when,' and a system without a proper audit log cannot answer it, no matter how good its backups are. We build logging that records every sensitive action at the point it happens, in a form nobody can quietly edit afterward.
What it is
An audit log and compliance trail is a structured, append-only record of sensitive actions in your system: who changed a price, who issued a refund, who viewed a customer’s personal data, who altered another user’s permissions. The value is specific: when something goes wrong, a real dispute, a security incident, a regulator’s question, this is the record that answers “who did this and when” with evidence instead of someone’s memory of what probably happened.
When you need it (and when you do not)
You need this for any system handling money, personal data, or administrative access where “who did this” is a question that will eventually get asked, whether by a customer dispute, an internal review, or a compliance framework like SOC 2 or GDPR that explicitly requires it. It is worth building proactively, since retrofitting a trail after an incident means the incident itself has no record.
You do not need a formal audit trail for low-stakes internal tools where mistakes are cheap and reversible and no external party will ever ask for the record; standard application logging for debugging is enough there. It becomes necessary once real money, real personal data, or real compliance obligations enter the picture.
How we build it
We start by identifying which actions in your system actually matter: usually a specific, bounded list, refunds, permission changes, data exports, price edits, account deletions, rather than logging everything indiscriminately, which produces noise nobody reads. Each logged event captures who performed the action (tied to an authenticated account, not just an IP address), what the action was, what changed (before and after values where relevant), and when, stored in an append-only table in PostgreSQL, often with a write-once storage pattern or a cryptographic chain between entries for cases where tamper-evidence matters most.
The log is searchable from your admin panel, filterable by user, action type or time range, so a real investigation does not mean grepping a raw log file. For specific high-risk actions, a large refund, a bulk data export, an alert fires immediately rather than waiting for someone to review the log after the fact. Retention is set to match whatever compliance framework or internal policy applies, since keeping everything forever is its own liability.
What to watch
An audit log is only as good as the list of actions it actually covers; we review this with you periodically, since new features add new sensitive actions that need their own logging, and a feature shipped without it is a silent gap. Append-only storage has a real cost in data volume over time, which retention policy addresses but does not eliminate. This system supports a compliance program; it is not, by itself, a certification, and we say so plainly rather than overselling the scope of a logging feature.
Price and timeline
| Option | Price | What it covers | Timeline |
|---|---|---|---|
| MVP | from $1,200 | Logging for your highest-risk actions, searchable admin view | 1 to 3 weeks |
| Production | from $3,200 | Full action coverage, alerting on high-risk events, retention policy, export for review | 4 to 6 weeks |
Related
This pairs with role-based access control for the permission layer it logs, and with GDPR consent and data lifecycle for personal-data-specific trails. It is part of the development and audit services. This is the same discipline applied in factory ERP recovery and across the ProBay AI agent team platform.
Ready to find out what your system currently fails to log? Get in touch and we will review it with you.
FAQ
How much does an audit log and compliance trail cost?
From $1,200 to add structured, append-only logging of sensitive actions to an existing application; a full compliance-grade trail across multiple systems costs more and depends on which framework you are targeting.
How long does it take?
1 to 3 weeks, most of which is identifying which actions in your system actually need logging.
Does this make us SOC 2 or ISO 27001 compliant?
It covers the audit-logging control those frameworks require, which is a real piece of the work, but full certification involves policies, processes and an external audit beyond what a logging system alone provides; we are explicit about that boundary.
Can logs be edited or deleted?
No, by design. Entries are append-only; a correction is a new entry referencing the old one, not an edit, which is what makes the log actually trustworthy as evidence.
Who can see the audit log?
Access to the log itself is role-restricted, usually to admins or a compliance role, since the log often contains sensitive detail about what other users did.