Audit Trail | An immutable record of every action | Velt

How it works

Three steps to the first record.

01Install

npm install @veltdev/react

02Wrap

<VeltProvider
  apiKey={VELT_API_KEY}>
  <YourApp />
</VeltProvider>

03Mount

// enable Activity Logs in the Velt Console first
// document scope set via useSetDocumentId('filing-q3')
<VeltActivityLog />

With Velt

The mechanics

Once enabled, Velt records activity across features automatically: comments, reactions, recordings, CRDT edits, and approval state changes. Every approval state change appends a statusHistory entry: who changed it, when, and the note they left, written synchronously with the status change. Each record carries judgment fields: reasoning, confidence, judge type (human or agent), authority, prior judgments, and content context. Enrichment runs async, so logging adds no latency.

// getAllActivities streams records live · console toggle per docs

Build it yourself

What an in-house version requires

• capture hooks inside every feature
• an append-only store
• attribution and timestamps on every write
• status-transition triggers
• query indexes by document, user, time range
• an export pipeline
• retention and GDPR deletion
• tamper evidence
• a feed UI with filters

Teams that build it budget a quarter for the first version and keep paying for the long tail. The 3 steps above replace the first quarter; the capability wall below replaces the long tail.

Capabilities

Who approved what, on the record.

Little big details

The long tail, already built.

Make it yours

Your timeline, your privacy posture.

In production

The trail, in products like yours.

SummaryNext StepsDemoCustomer Stories

Proof

The regulated deal, unblocked.

Install @veltdev/react, wrap your app in VeltProvider with your API key, enable Activity Logs in the Velt Console, and add the VeltActivityLog component for a prebuilt, filterable timeline. The setup guide walks through it.

Comments, replies, reactions, recordings, multiplayer edits, and every approval state change, recorded automatically. Your own product events join the same trail through the createActivity API, with judgment fields validated on write.

Yes. Pull any record set through the Get Activity Logs REST API as structured JSON, filtered by document, user, feature type, or time range. Audit report PDFs and CSV packages are coming to the same chain.

Article 14 applies to high-risk AI systems defined in Annex III (credit, insurance, hiring, critical infrastructure, and essential services among them), enforceable from August 2, 2026; it is not a universal obligation on every AI feature. If your product or your customers operate in that scope, Velt provides the mechanism (approval before action) and the evidence (a record of who approved what, when, and why). Talk to your counsel about whether you are in scope; see /governance.

Immutability is on by default for new accounts: edits create new records linked to the original, and deleting source content leaves the record standing. GDPR deletion runs through a dedicated compliance API and is itself logged.

Every record carries a judge type of human or agent. An agent’s finding, its confidence score, and its reasoning sit in the same trail as the human decision that accepted or rejected it, so the oversight chain is explicit.

No. The status record is written synchronously with the status change itself; everything else enriches asynchronously after the user-facing write completes. Records exist within a second, and user actions gain no latency.

Yes. The self-host activity data provider keeps log content, entity snapshots, and custom fields on your infrastructure while Velt stores only minimal identifiers. See /self-hosting.

Velt is priced on usage, not seats: you pay for documents with review activity in a month, and there is a free tier for development and early production. The audit trail is part of the SDK, not a separately priced add-on.