Skip to main content
Tally gives compliance-driven teams a single, authoritative store for identity data. Every time you submit identity information about a business or person, Tally records an immutable, versioned snapshot that is cryptographically linked to its predecessor — forming a tamper-evident ledger you can audit at any point in time. You can share that data across organizational boundaries through scoped grants, so counterparties and downstream systems always read from the same verified source of truth.

​
What is Tally?

Modern KYC and KYB pipelines collect identity data from many sources — government registries, document scans, beneficial ownership attestations — and that data changes over time. Storing it in a mutable database makes it hard to prove what you knew, and when. Tally solves this by treating identity as a versioned ledger. Your organization (a tenant) tracks businesses and individuals as subjects. Each time you update a subject’s identity information, you submit a new snapshot. Snapshots are stored immutably, hash-chained using RFC 8785 canonicalization and SHA-256, so you can independently verify that no historical record has been altered. When another organization needs access to a subject’s data — say, a bank needs to verify a supplier’s KYB record — you create a grant that gives their tenant scoped, time-bounded read access. They read directly from your verified snapshot chain rather than receiving a static export that can go stale.

​
Key concepts

Subjects

The entities and individuals whose identity data you manage. Each subject has a type (entity or individual) and a stable subject ID that anchors its entire snapshot history.

Snapshots

Immutable, versioned records of a subject’s identity at a point in time. Each snapshot is cryptographically hash-chained to the previous one, forming a verifiable audit trail.

Tenants & Roles

Your organizational workspace in Tally. Members of a tenant hold roles (tenant_owner, tenant_admin, tenant_editor, tenant_proposer, tenant_reader) that control what they can read and write.

Grants

Scoped, time-bounded access tokens that let you share a subject’s snapshot data with another tenant. Grants carry explicit read scopes such as read_latest, read_lineage, and read_diff.

Data Integrity

Every snapshot envelope is canonicalized with RFC 8785 and hashed with SHA-256. The resulting hash is stored alongside a pointer to the previous snapshot’s hash, so you can independently verify the full chain.

Webhooks

Subscribe to real-time events such as identity.snapshot.created and refresh_request.fulfilled so your systems react the moment identity data changes.

​
Who uses Tally?

  • KYC/KYB platforms that need a durable, auditable store for identity data collected during onboarding — Tally replaces ad-hoc database tables with a structured, hash-chained ledger.
  • Financial institutions that must demonstrate to regulators exactly what identity information was on file at a specific date — Tally’s immutable snapshots make that trivial.
  • Compliance teams sharing verified identity records with partners or auditors — Tally’s grant system lets you give counterparties direct, scoped access without emailing spreadsheets or PDF exports.
Ready to submit your first snapshot? Head to the Quickstart to create a tenant, submit an identity snapshot, and read it back in under five minutes.