chartly.com

What It Is

Chartly positions itself as an “auditable record layer” for AI Agent providers. It records every Agent action and uses a multi-party BFT consensus chain, customer-held keys, and cryptographic signatures so that customers, auditors, or regulators can verify audit logs have not been tampered with after the fact—without having to trust the vendor. The problem it addresses is not traditional log collection, but the non-repudiation issue in enterprise security reviews: “Are these logs maintained by the party under scrutiny?”

Core Capabilities

For protection mechanisms, Chartly uses a dedicated Antelope chain, hash chains, block co-signing, witness nodes, BYOK, AES-256-GCM, ABAC, read audits, and crypto-shredding. On-chain data is limited to timestamps, pseudonymous actors, action types, resource types, encrypted payload hashes, and KMS envelope references; no PII or plaintext payloads are stored. Medium and above support AWS KMS, GCP KMS, Azure Key Vault, and HashiCorp Vault. Large allows customer, auditor, and regulator nodes to join, and provides ML-DSA/SLH-DSA post-quantum co-signing plus optional on-prem deployment.

Pricing and Scale

Pricing is tiered by monthly event volume and verification topology. Free includes 10,000 events/month. Small is $197/month billed annually, aimed at early-stage SaaS companies. Medium is $997/month billed annually and includes 1M events, multi-region BYOK, ABAC, and a 24h SLA. Large starts from $30K/year and targets regulated SaaS, F500 companies, and the public sector. Overages do not trigger a hard shutdown; after three consecutive months above the tier limit, Chartly will notify the customer, with options to pay $2/1,000 events or upgrade.

Pros and Cons

The main advantage is a very clear threat model: it directly addresses the audit-trust problem that arises when AI Agents enter enterprise environments. The design—customer-held keys, multi-party witnessing, and storing only metadata on-chain—also fits well with regulatory audit scenarios. SDK coverage includes TypeScript, Python, and Go, keeping integration costs relatively manageable. The downside is that the copy still indicates open design-partner slots, so maturity, formal customer references, and production stability are not yet proven. The compliance section appears to be a mapping rather than disclosure of formal certifications such as SOC 2 or ISO. Key capabilities are concentrated in Medium/Large, so full deployment costs and organizational coordination costs may be significant.

Best Fit and Access from China

Chartly is best suited for teams selling AI Agents or regulated SaaS into large enterprises, finance, healthcare, or the public sector—especially vendors frequently asked by CISOs and auditors about tamper-resistant logging. Access from China, payment methods, data residency, and local compliance support are not disclosed, so these remain unknown. For China-facing customers, additional evaluation is needed around network connectivity, KMS/cloud regions, cross-border data transfer, and local MLPS/audit requirements. Alternatives may include local cloud log auditing, blockchain-based evidence preservation, SIEM solutions, or building an in-house audit chain.