Standards & technology.

The open standards under Foundry, and how your systems reach them. Technical depth for architects and security teams.

Book a demo

How the proof works

Every approval stands on three open standards, not a closed black box. Anyone can verify the result without asking us.

  1. 01KERI

    The signer's keys

    Each authorized signer holds their own keys, with a history of every key change that cannot be quietly rewritten.

    Key Event Receipt Infrastructure

  2. 02vLEI

    Who may approve

    The company's verifiable legal identity in the GLEIF system, and the official role each officer holds in it.

    Verifiable Legal Entity Identifier, under GLEIF

  3. 03ACDC

    What was approved

    A sealed, signed record of exactly this change, chained to the signer and their role.

    Authentic Chained Data Containers

Open trust foundation

Digital Trust Foundry implements cryptographically verifiable trust using standards adopted through the open ecosystem.

KERI
Key Event Receipt Infrastructure: autonomous identifiers with verifiable key rotation.
vLEI
Verifiable Legal Entity Identifier, under GLEIF: an organization's verifiable legal identity and its officers' official roles.
ACDC
Authentic Chained Data Containers: tamper-evident, self-addressing digital artifacts (trustables).

Trustables combine artifact content, cryptographic signatures, lifecycle events, and verification endpoints your applications call at execution time.

Integration surface

The Trustables API is the primary integration path: create, verify, lifecycle-manage, and export trustables.

ServiceNow and Salesforce integrations use this API. So can any custom application.

Works with your platforms

Deployment

Foundry is available as SaaS, dedicated cloud, or on-premise deployment.

Contact us for architecture and deployment details specific to your environment.

How it works, the business view

Walk through a payment change impersonation scenario

15 minutes. Live demo. No jargon required.

Book a demo