Your audit log won't survive enterprise security review.

The question that kills your enterprise deal

On call 2 of security review, the customer's CISO asks one question:

"How do we know your agent's audit log wasn't edited after the fact?"

Every honest answer today loses the deal.

Root problem: the suspect is the signer. When one party owns the log, the chain, and the verifier, the proof has zero value to third parties who don't already trust that party.

What we ship

The audit layer that puts the proof outside your control — the only proof your enterprise prospect's auditor will accept.

Drops in with one SDK call

TypeScript, Python, Go. The rest is metadata, encryption envelopes, and chain submission — handled for you.

chartly.record({
  actor:    "agent:claude-sonnet-4-6/customer-abc",
  action:   "read_customer_record",
  resource: "crm/contact/12345",
  payload:  { ... },
  sensitivity: "pii"
})

What changes in your sales motion

Pay for what your auditor counts.

Four tiers, priced on monthly event volume and verification topology. Every tier signs to the same consensus chain — higher tiers add multi-region, dedicated witness nodes, and post-quantum co-signing.

Built for a threat model where the vendor is the suspect.

Every guarantee Chartly makes is structural, not policy. Even Chartly cannot rewrite your audit trail or read your data without your KMS releasing the key.

Threat model

Five-layer architecture

Event size & abuse protection

Chartly enforces strict per-event size limits and per-tenant rate ceilings. These exist for two reasons: (1) chain hygiene — block sizes stay predictable so witness nodes verify quickly, and (2) cost integrity — billing per event only makes sense if events are bounded.

Large artifacts (model outputs, transcripts, PDFs) → blob-by-reference. Customer uploads the blob to their own S3/GCS/Azure Blob bucket. Send Chartly only the content hash + URI:

chartly.record({
  actor: "agent:claude-sonnet-4-6/customer-abc",
  action: "generate_report",
  resource: "report/q4-2026",
  blob: {
    uri:    "s3://customer-bucket/reports/q4-2026.pdf",
    sha256: "9f86d081884c7d659a2feaa0c55ad015...",
    bytes:  4_283_991
  }
})

The chain signs the hash + URI. Your customer holds the blob. Your auditor verifies a sealed report by fetching the URI and re-hashing locally. Chain stays small, costs stay aligned.

Notification preferences

Chartly emits four event categories. Each can be routed to a different channel and a different contact. Every outbound notification is itself recorded on the chain as a notification.sent event — auditing the auditor is the whole point.

Available channels (by tier)

Customers control routing per category, per recipient, per environment. Multiple recipients per category are supported. SMS is reserved for integrity events; we don't SMS billing notifications — it trains people to ignore the channel that actually matters.

Compliance mapping