01
Tenant isolation
Every event, filter, export, and viewer session must stay inside the correct customer organization.
Identity + data modelAUDIT / 01CUSTOMER-FACING AUDIT LOGS
Enterprise buyers ask for audit logs before they trust your product.
Do not spend two quarters building the viewer, tenant isolation, retention, exports, SIEM streams, and verification layer behind one security checkbox. Send the event once. Give every customer a complete, signed audit log.
One event API Hosted or embedded viewer Signed, exportable, streamable
ENTERPRISE SECURITY REVIEWAcme Global · $84K ARR
BLOCKEDRequired controlCustomer-accessible audit logs
admin.acme.com/audit
Audit Logs
SIGNEDFilter by actor, action, target, or date
ACTORACTIONDATE AND TIME
REQUIREMENT ANSWEREDViewer, export, retention, and SIEM delivery ready
01CaptureAction, actor, targets, context
02ProtectHash, sequence, and Ed25519 signature
03DeliverViewer, export, stream, and proof
02THE CHECKBOX HIDES A PRODUCT
“We need audit logs” sounds small. The build behind it is not.
Recording an event is the easy part. Enterprise-ready audit logs become a customer-facing product with security, data-lifecycle, and delivery obligations your team has to own for years.
SECURITY QUESTIONNAIRE · CONTROL 7.4
REQUIREDDoes your application provide customer-accessible audit logs?
Not yetRoadmap item · Q4
YesAvailable on enterprise plan
DEAL IMPACTProcurement cannot approve without this control.
02
Customer viewer
Enterprise users expect search, filters, pagination, event details, and a polished experience inside your product.
Frontend + permissions03
Exports and retention
Security reviews ask for CSV or NDJSON exports and contractual retention windows measured in months or years.
Jobs + storage lifecycle04
SIEM streaming
Larger customers want signed events continuously delivered into their own security and monitoring stack.
Delivery + retry system05
Tamper evidence
A database row shows what it says today. It does not prove the record was not quietly changed after the event.
Canonicalization + keys06
Audit handoff
Your customer needs a scoped way to inspect and verify history without receiving access to your internal systems.
Portal + session security03THE CUSTOMER EXPERIENCE
Give every customer a log they can actually use.
Not a raw database export. A tenant-scoped audit experience where customers can find the action, understand the context, and check that the record still matches what was signed.
admin.acme.com/audit
Audit Logs
SIGNEDFilter by actor, action, target, or date
ACTORACTIONDATE AND TIME
YOUR ID → AUDIT ORG
One log per customer
Use the organization ID already in your application. Every event and access path remains tenant-scoped.
SEARCH · FILTER · OPEN
Useful on day one
Search and filter by action, actor, target, IP, and date without building an event-query interface.
SHA-256 + ED25519
Signed at ingestion
Every accepted event is hashed and Ed25519-signed against your registered issuer key.
30 → 365+ DAYS
Retention by org
Apply the customer’s retention requirement within the maximum supported by your plan.
CSV · NDJSON · HTTPS
Export or stream
Queue CSV or NDJSON exports, or continuously send signed webhooks to a customer’s SIEM endpoint.
PORTAL · REACT VIEWER
Hosted or embedded
Mint a private hosted viewer link or place the native React viewer directly inside your application.
04BUY THE OUTCOME, NOT THE BACKLOG
Your team should define the events. It should not rebuild the platform around them.
ENTERPRISE REQUIREMENT
BUILD IT YOURSELF
INVOANCE AUDIT LOGS
Customer-scoped history
Custom authorization on every query
Organization isolation is built into the API
Self-service viewer
Design, build, maintain, and theme it
Hosted portal or native React viewer
Long-term retention
Lifecycle jobs and storage tiers
Set per org, bounded by your plan
Security exports
Async jobs, storage, and download security
CSV and NDJSON with filtered export jobs
SIEM delivery
Webhook signing, retries, and observability
Signed HTTPS streams with delivery controls
Tamper verification
Key management and a frozen canonical schema
Online or offline signature verification
05THE PRODUCTION PATH
From application action to customer evidence in one straight line.
Keep your existing database, auth model, and application workflow. Add the audit write after the action succeeds and let Invoance carry the record through the customer-facing lifecycle.
01
Your action succeeds
A user signs in, changes a role, exports data, updates billing, or performs another security-relevant action.
your application02
Send one event
Write the action, actor, targets, and context with an SDK or raw HTTP. Safe retries do not create duplicates.
POST /v1/audit/events03
Invoance signs it
The event is normalized, hashed, timestamped, sequenced inside its org, and signed as one atomic ingest operation.
invoance.audit/104
Your customer uses it
They search, filter, export, stream, and independently verify their own history without asking your team for evidence.
viewer · export · SIEM06FOR DEVELOPERS
One write after the action. The rest is already a product.
The SDKs default the timestamp and generate the required idempotency key. Send the stable organization ID your application already knows, then store the returned event ID only if it helps your own workflow.
Nine integration choices Eight SDKs plus raw HTTP.
Strict event envelope Bad shapes fail before they reach the log.
Safe retries Required idempotency prevents duplicate events.
const event = await client.audit.events.ingest({
organizationId: "org_acme",
action: "user.role_changed",
actor: { type: "user", id: "usr_42" },
targets: [{ type: "user", id: "usr_87" }],
metadata: { from: "member", to: "admin" },
});
console.log(event.event_id);SDKs set the timestamp and idempotency key for you. Safe to call from an at-least-once pipeline.
Instrument the actions that matter.
Send product, admin, billing, and data-access events directly from your backend.
Audit APIConnect Clerk or Auth0 first.
Start collecting mapped sign-in, membership, and role events before broader instrumentation.
Auth integrationsPut the viewer inside your app.
Use the native React component for a branded customer experience without an iframe.
Viewer setup07ONE PRODUCT, THREE WINS
Close the requirement without creating a permanent distraction.
Product & sales
Stop losing the deal on one security checkbox.
Show a production-ready audit-log experience during the evaluation, not a roadmap promise after procurement has stalled.
Engineering
Own the event. Not the entire audit-log product.
Your team decides what happened and sends the event. Invoance handles the viewer, isolation, signatures, exports, retention, and delivery.
Security & success
Give customers answers without opening a ticket.
Customers can investigate activity, produce evidence, and verify records themselves while your internal systems remain private.
08AUDIT LOG QUESTIONS
Add the customer-facing layer without changing how your app works.
SIGNED AUDIT INFRASTRUCTURECapture once. Answer customers for years.
Customer-scoped access
Ed25519-signed events
Offline verification
No. Keep internal logs for debugging and operations. Send the customer-visible security and business actions that need a durable, tenant-scoped history.
09AUDIT LOG PRICING
Move the volume. The right plan follows.
Drag the monthly event volume to see the lowest plan whose included Audit Logs allowance covers it. No separate audit-log platform bill to calculate.
MONTHLY AUDIT EVENTSDrag to estimate
Every included event is signed and independently verifiable.
RECOMMENDED PLANBuilderBest included allowance for this volume
FULL PLATFORM PLAN$149/ monthIncludes every Invoance product
INCLUDED AUDIT EVENTS1,000,000
ROOM TO GROWAt plan limit
READYANSWER THE AUDIT-LOG CHECKBOX
Ship the audit log your next enterprise buyer already expects.
Start with one customer and one action. Add the viewer, exports, retention, streaming, and independent verification without adding six systems to your backlog.