Extensions
Audit Logging Add-on
Every action and change in your AI product is written to a log that shows if anyone has tampered with it.
When something changes in your AI product, you need to know who did it, when, and whether the record can be trusted. This add-on writes every agreed action and change to a tamper-evident log stored in an account you own. Entries can be searched and exported, and any later edit to the log is detectable.
- Records who changed what, and when
- Makes any later edit to the log detectable
- Stores logs in an account you own, searchable and exportable
$1,500
10–20 working days
What it is
The Audit Logging Add-on adds tamper-evident logs of actions and changes to an AI product you already run, or are buying now. It records who changed what and when, and which actions the product took, in a way that makes later edits detectable. Logs stay in an account you own.
Why businesses buy it
When a customer disputes an answer, a setting changes unexpectedly or an auditor asks for evidence, plain logs are not enough, because anyone with access could have edited them. Tamper-evident logging gives you a record you can stand behind. It also discourages careless changes, because everyone knows actions are recorded. The written scope lists the events logged, how to search and export them, and a test proving tampering is detected, so the logs hold up when you need them.
Problems this solves
Something changed in the product and nobody can say who did it
The Audit Logging Add-on records who changed what and when. It also records which actions the product itself took, so you can trace both people and automation.
Ordinary logs can be edited, so they carry little weight
Logs are written in a tamper-evident way that makes later edits detectable. That gives you more confidence in the record when a question is raised.
Records of activity sit with a vendor rather than with you
The logs stay in an account you own. You keep access to the history even if suppliers change, and the documentation explains where the logs live.
A good fit if
You need to show auditors, customers or managers who changed what, and when.
Your product takes actions, such as updating records or sending messages, that you must be able to account for.
Several people change knowledge, prompts or settings, and nobody can say who changed what.
You want a record you can trust has not been edited afterwards.
Not the right fit if
You want every AI input, output and decision recorded for later review. AI Audit Trail is that fuller build.
You want structured logs across several AI workflows for debugging. AI Agent Logging adds them.
You need written documentation of data flows and controls for a compliance review. Compliance Documentation Pack provides it, though it is not a certification.
You want to decide how long logs and data are kept and when they are deleted. Data Retention and Deletion Configuration sets that up.
How it works
- Events are agreed. Which actions and changes are logged: sign-ins, setting changes, knowledge edits, actions the product takes.
- Each entry records who, what, when and the before-and-after where relevant.
- Entries are made tamper-evident, so a changed or deleted entry shows up when the log is checked.
- Logs are stored where you choose, under your own account, and can be searched and exported.
- Logging is tested with the parent product, including a check that tampering is detected, then reviewed with one revision round.
What you provide within 72 hours
Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.
- The order reference of the product being logged
- The events you need logged, and why
- Where logs should be stored, in an account you own
- Storage access, shared securely in the way we agree at intake
- One person who approves the event list
The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.
Timeline
Start
Events to log and storage location agreed
Week 1
Event list and entry format confirmed
Week 2
Logging built with tamper evidence
Week 2
Logging and tamper detection tested
Week 2
Your review and one revision round
Go-live
Audit logs live, format documented
| Option | Delivery time | Price |
|---|---|---|
| Standard | 10–20 working days | $1,500 |
What you receive at handover
- Tamper-evident logs of actions and changes added to your existing product
- Logs stored in an account you own
- Updated documentation explaining what is logged and where
- A test report, a handoff note and a short written walkthrough
Expected benefits and how to measure them
- Makes it easier to answer who changed what and when
- Helps when customers, auditors or insurers ask for evidence
- Can shorten the time spent investigating unexpected changes
- Time to trace a change
- Time how long it takes to find the source of a change, before launch and after.
- Log completeness
- Make a few known test changes each quarter and confirm each appears in the log.
- Unexplained changes
- Count changes nobody could account for in the months before and after launch.
Before you start: Note how you currently find out who changed something in the product, and how long the last investigation took.
These are things to track, not promised results. Outcomes depend on your data, your team and your market.
Running costs
Logs are stored in an account you own, so storage costs are billed there; for most products the volume is small. We charge once for the add-on and nothing per entry.
Ask about running costsCustom requirements
Streaming logs into a security monitoring tool, logging events from systems the product does not touch, or long-term archiving rules are beyond this add-on. Note them at checkout for a written Change Quote. Larger or bespoke projects go through the Custom AI request form instead.
Request a custom versionKeep it running
Audit logging is covered by the parent product's maintenance, which grows in line with the add-on's price. Adding an event type later uses its monthly change hours.
Adds $75/mo to maintenance
Covered by the main product's maintenance, which grows by this amount.
How maintenance worksHow this compares
| Do it yourself with a SaaS tool | Hire a custom agency | Upmark Labs | |
|---|---|---|---|
| Price | Audit logs on an enterprise tier, billed monthly | An agency quotes logging work | Ours is one fixed price, shown before you buy |
| Trust | Plain logs anyone with access could edit | Depends on the brief | Ours makes changes to entries detectable |
| Storage | In the vendor's account | Depends on the contract | Ours is in an account you own |
| Testing | Left to you | Set per project | Ours tests that tampering is detected |
Questions about this product
What does tamper-evident mean for these logs?
It means that if someone edits or deletes a log entry after it was written, a check of the log reveals it. It does not stop a determined administrator from trying, but it means a changed record cannot pass as the original. We test this before launch.
Which events can the audit log record?
The events agreed at intake, typically sign-ins, setting changes, knowledge and prompt edits, and the actions the product takes, such as updating a record or sending a message. Each entry shows who, what, when and, where it makes sense, the value before and after.
Where are the audit logs stored?
In an account you own, chosen at intake, so the record stays yours if you ever move away from us. Logs can be searched and exported from there. Storage costs, usually small, are billed to that account rather than through us.
Does audit logging start recording from the day it launches?
Yes. Logging starts when the add-on goes live with its parent product, and earlier activity is not recreated. It follows the delivery speed chosen for that product, and faster speeds are available, each with a fixed price and date shown before you pay. If you have an audit coming, tell us during intake.
How long are the audit logs kept?
As long as you decide. This add-on records and protects the logs, but it does not set retention periods. The Data Retention and Deletion Configuration add-on sets how long logs and other data are kept, and the two can be bought together and delivered in the same window.
Does audit logging make us compliant with a regulation?
No add-on can promise that on its own. Audit logs are evidence that many reviews ask for, but compliance depends on your wider policies. If you need your data flows and controls written up for a review, the Compliance Documentation Pack helps, though it is not a certification.
Know who changed what, and know the record has not been touched.
Add the Audit Logging Add-on and your product keeps tamper-evident logs of actions and changes, stored in an account you own and tested before launch.
Works well with
Front Line
AI Customer Support Agent
Resolves customer questions across chat and email using your knowledge base and hands off complex cases.
Business Agents
AI Executive Assistant
Triages the inbox, manages the calendar, prepares briefings and chases follow-ups for a leader.