Skip to main content
Technology · the trust layer

Nine layers. Eight standards.No proprietary format.

A single trust layer sits under every product. It is organized as a chain of nine layers, from establishing the actor to producing a verifiable proof. Every element listed is implemented and tested in the product.

01

Identity

Establishing whether the actor is a person or a machine; full life cycle. An account alone is not an identity.

X.509 · Argon2
02

Access

Roles, permissions, scopes; centralized policies rather than ones scattered through features.

Centralized policies
03

Organizations

Strict isolation between organizations: perimeters, settings, data.

Isolation (RLS)
04

Assets

Encrypted storage with separation of duties.

AES-256-GCM
05

Cryptography

Fingerprints and signatures.

SHA-256 · ECDSA
06

Documents

Long-term verifiable digital signatures and signer certificates.

PAdES B-LTA
07

Provenance

Provenance manifest bound to the content.

C2PA
08

Verification

Electronic timestamping, attestations, public verification.

RFC 3161
09

Audit

Sealed, chained log, checkpoints, public anchoring.

Merkle · OpenTimestamps
Two sides of the same file
What stays hidden · security

The vault

The encrypted contentKeys and secretsAccess controlAuthenticationIsolation between organizations
What becomes demonstrable · proof

The fingerprint

A SHA-256 fingerprint (e.g. sha256:1ebb…c9e4)An RFC 3161 timestampThe signer's X.509 certificateA C2PA provenance manifestA Merkle history log

The same file is protected on one side and demonstrable on the other, without being revealed: only the 32-byte fingerprint leaves the vault. Published when anchoring: the fingerprint, not the document, its name, its size or its type.

The evidence bundle

Verifiable without IRON ID.

Each certified document exports as a self-contained bundle, verifiable with an open source tool. Since the format is published, a third party can also write its own verification.

ClaimedIndependently verifiable proof of integrityDetection of any alterationRFC 3161 electronic timestampProofs verifiable without IRON ID
Explicitly not claimed"Tamper-proof"Legal equivalence to a handwritten signatureQualified timestamp, until the provider is named100% compliance with a regulation
ironid-evidence-{bundleId}.zipOpen format
manifest.jsonSigned index of the bundle
document/content-hash.txt and the original file
attestations/timestamp.tsr (RFC 3161), anchor.ots (OpenTimestamps), c2pa.manifest
certificates/chain-attest.pem
audit/entries.jsonl, inclusion-proof.json, checkpoint.json
verification/Offline verification instructions