Skip to main content
How it works

Integrate. Establish trust. Verify & audit.

The intended platform workflow, from connecting your application to verifying and recording every approval. Not all stages are publicly available yet.

  1. Step 1

    Integrate

    Connect an application to the Trustlith developer platform.

    • Server-side credentials
    • Application scope
  2. Step 2

    Establish Trust

    Enroll devices and establish credential ownership.

    • Device key pair
    • Public key enrolled
  3. Step 3

    Verify & Audit

    Validate cryptographic proofs and record security events.

    • Signed challenge
    • Verified result
    • Audit event

Intended platform workflow; not all stages are publicly available yet.

Inside an approval

What happens when a user approves an action.

An illustrative walk-through of the intended design. Your application stays in control of its session and its final decision.

  1. Your app requests a decisionA fresh challenge is created for a specific user and action.
  2. The user confirms on their deviceAn explicit biometric or passcode prompt; nothing is approved automatically.
  3. The device signs the challengeUsing a private key that stays on the device.
  4. The proof is verifiedChecked server-side for signature, expiry and replay before a result is returned.
  5. The event is recordedAppended to tamper-evident audit history.
How a Trustlith approval is designed to flow An application sends a fresh challenge to the user's device. The user confirms presence on the device, which signs the challenge with a key that stays on the device. The application verifies the signed proof, and each step is appended to a tamper-evident audit log. user presence ✓ Device key stays on device Your app verifies the proof challenge · nonce 7f3a… signed proof · sig 3045… AUDIT LOG · APPEND-ONLY #0412challenge.issued9f2c→a41d #0413presence.confirmeda41d→c07e #0414proof.verifiedc07e→5b92 #0415event.recorded5b92→e3f8
Illustrative concept of the intended flow. Not a product screenshot.
Core capabilities

One trust model, from device to decision.

Six capabilities designed to work together as a single layer, rather than six products stitched together.

Available
Publicly available today
In development
Being designed and built
  • In development

    Device-bound credentials

    Credentials are designed around key pairs generated on the user's device. The private key is intended never to leave it, using platform secure hardware where available.

  • In development

    User-presence verification

    Sensitive approvals are designed to require an explicit action on the device, such as a biometric or device passcode, before anything is signed.

  • In development

    Cryptographic proof validation

    Each approval is designed as a signature over a fresh, server-defined challenge, verified server-side with expiry and replay protection.

  • In development

    Credential enrollment and lifecycle management

    Designed to cover the full lifecycle: enrolling devices, adding another device, rotating keys, revoking credentials and recovering access.

  • In development

    Tamper-evident audit architecture

    Security events are designed to be recorded as append-only, integrity-protected history, so later changes become detectable.

  • In development

    Developer-oriented integration

    Designed to integrate through a server-side API, SDK and developer portal, so your application keeps control of its own sessions and decisions.

No Trustlith capability is publicly available yet. Status labels will be updated as each capability is released.

Get started

Start Building a More Trustworthy Digital Future.

Explore Trustlith's developer platform and follow our journey toward secure, verifiable digital interactions.