Skip to content

FEATURES

“Who did that?” always has an answer.

Every sensitive operation is recorded with the actor, the timestamp, and the precise detail of what changed. Down to the individual field, on records where that matters.

Always on. The audit trail is not a feature you switch on. It is what makes it safe to give an operator a powerful tool at all, so it is part of every installation.

What it solves

Something is wrong and nobody knows how it got that way. A price is off, a status was changed, a record was deleted. Without a trail, the investigation is a group conversation about what people remember doing three weeks ago.

What's in it

6 capabilities, in the order people ask about them.

The audit log

  • Every administrative operation is recorded with the actor, the target, and the time.
  • Sensitive operations especially — a role change, an impersonation, a manual discount, a refund, an export — are recorded with the full detail of what changed.

Field-level change history

  • On records configured for it: exactly which field changed, from what value to what value, by whom, and when. Not a summary — the specifics.

Confirmable event timelines

  • A timeline on any entity, not just orders. Workflow stages that can each be confirmed by a named person, so “was this checked?” is answerable.

Internal remarks

  • Team-only notes on any record. Visible to your people, never to the customer.

Operational labels

  • An internal vocabulary for states that aren't official yet — “needs photography”, “authentication in progress”. Teams always invent these; this gives them somewhere to live other than a spreadsheet.

Retention, stated clearly

  • Commercial, financial, and evidentiary data — orders, invoices, change history — is never deleted automatically.
  • Only purely operational logs, such as rate-limit counters, are cleaned up.
  • That separation is enforced in code from the beginning, explicitly. It isn't a policy decision someone makes later and hopes was applied consistently.
  • Even during a GDPR erasure request, a financial document survives — personal data is anonymised while the legally required fields remain intact.

Powerful tools and accountability ship together. Impersonation, bulk edits, manual discounts, exports — every one of them writes a record. That's not a constraint on the operator; it's what makes it safe to give them the tool at all.

Let's build the thing you actually want to build.

Tell us what you have in mind. We'll show you how much of it already exists.

  • We reply within one working day
  • No sales sequence, no drip campaign
  • NDA before the call if you'd prefer