Platform · Trust & Control
Append-only. Searchable. Every change captured.
A TMS without a real audit log is a black box. When a load status flips, when a payment voids, when a bulk import overwrites a driver record — somebody needs to be able to answer who did it and when. Keelway's audit log captures every meaningful state change in the platform, append-only at the architecture layer, searchable by user, action, or entity. The log enterprise procurement teams ask about before signing — and the log a controller checks before signing off on a quarter.
Every
Status change, payment, bulk action
Loads · invoices · settlements · drivers · trucks · admin
Append-only
Architectural guarantee, not UI
No edit, no delete, ever
SIEM
Stream to Splunk / Datadog / Sumo / S3
Enterprise tier
Captures
Every meaningful change
Load status, invoice events, payment events, settlement events, driver / truck / trailer changes, compliance uploads, bulk CSV operations, admin actions, integration changes. Each entry: user, timestamp, before/after diff.
Append-only
No edits, no deletes, ever
Architectural guarantee, not a UI affordance. Even the danger-zone admin operations write their own audit entries — the deletion itself is captured.
Searchable
Action, user, summary, entity type
Full-text search across action description, user, entity summary. Filter by entity type (Load, Invoice, Payment, etc.). Time-window selector. Controllers run it as a Friday spot check.
Stream
SIEM integration on enterprise
Stream to Splunk, Datadog, Sumo Logic, or any S3 bucket the customer owns. Near-real-time. Configurable retention (12 months minimum, 7 years available).
Frequently asked questions
What gets logged?+
Every state change in the platform — load status changes (Booked → In Transit → Delivered), invoice events (Draft → Sent → Paid), payment events (received, matched, voided), settlement events (drafted, finalized, paid), driver and truck changes, compliance document uploads, bulk operations (CSV imports, status batch updates), and admin actions (user added, role changed, integration connected/disconnected). Each entry carries the user identity, the timestamp, and the diff (before/after values where applicable).
Is the log truly append-only?+
Yes. Entries cannot be edited or deleted by any user, including admins. Even the danger-zone admin operations (clear old loads) write their own audit entries — the deletion is logged. This is a hard architectural guarantee, not a UI affordance.
How searchable is it?+
Full-text search across the action description, user identifier, and entity summary. Filter by entity type (Load, Invoice, Payment, Settlement, Driver, Truck, Trailer, User, Integration). Time-window selector. Most controllers run it as a Friday-afternoon spot check for the week's unusual activity.
Can audit logs stream to SIEM?+
Yes, on enterprise tenants. Stream to Splunk, Datadog, Sumo Logic, or any S3 bucket the customer owns in near-real-time. Retention configurable to customer policy (12 months minimum, 7 years available). See /security for the full posture.
What about the AI agent decisions?+
Those live in a separate log — the AI agent log — for clarity. Human actions go to the audit log; AI actions go to the agent log. Both are queryable from the same admin surface but kept distinct so an auditor can see what a person did vs. what the AI did without untangling them.
Auditor asking who changed the invoice?
