The book of record
Customers, the licence keys they hold, the hosted deployments you operate for them, and the append-only event log every commercially meaningful action lands in.
Customers & licences
Every customer is one record: their deals, invoices, licences, feedback and mail hang off it. The licence ledger answers the questions a growing product company keeps asking — who holds which key, on what tier, expiring when — from data, not from a spreadsheet someone half-maintains.
Keys are minted signed, revealed only under audit, and revoked in place. Because verification is offline on the customer's side, the ledger is your truth about what you issued, not a runtime dependency your customers' installs need alive.
The tenant registry
If you operate hosted deployments for customers, each one is a registry row — slug, plan, state, substrate, version — with provisioning, credential recovery and health polling attached. The registry is the record of your hosted fleet the way the licence ledger is the record of your self-hosted one.
The event log
Every commercially meaningful action — a mint, a reveal, a revoke, an invoice, a provisioning act — lands in an append-only event log with who did it and when. One function writes it; nothing edits it.