Platform overview

What Ananke Labs does

Ananke Labs lets you issue documents (credentials, certificates, contracts) that anyone can verify. Each document is cryptographically signed at issuance time and can optionally be anchored to a distributed ledger for tamper-proof integrity.

Verification is the central idea: anyone with a document reference, a content hash, or a scanned barcode can confirm whether the document is authentic and what its current status is.

Two products

Ananke Labs provides two core products, each designed for a different verification scenario:

• Ananke Trust — digital credential issuance and verification. Issue documents through the API, manage their lifecycle, and let recipients or third parties verify them online.
• Ananke TCode — physical document stamping and verification. Stamp PDFs with a DataMatrix barcode that encodes metadata and a cryptographic signature. Scanners can verify the document from the barcode alone.

See Ananke Trust vs Ananke TCode for a detailed comparison of when to use each.

How Ananke Trust works

With Ananke Trust, you define templates that describe the document schema (fields, validity rules, presentment settings). You then issue documents against those templates. Each issued document gets a unique reference, a cryptographic signature, and an optional chain anchor.

Documents have a lifecycle: Active → Suspended → Revoked (or Expired). Verification endpoints return the current status along with issuer metadata.

How Ananke TCode works

With Ananke TCode, you create a TDoc template that defines which fields go into the barcode payload, and a Placement template that controls where the barcode is rendered on the PDF. You then stamp a PDF, which generates a DataMatrix barcode containing the encoded payload plus a cryptographic signature.

Verification can happen by scanning the barcode (offline signature check) or by calling the verification API with the document reference or hash.

Using them together

Ananke Trust and Ananke TCode can be used independently or together. A common pattern is to issue a Ananke Trust credential for digital distribution and stamp an Ananke TCode barcode on the PDF version for physical distribution. Both link back to the same source of truth.

Public verification

Verification endpoints are designed for public access. They do not require tenant authentication — anyone with a reference or hash can verify a document. The API key is still passed for rate-limit identity, but verification works without it for public verification pages.