QVTM developer platform

Build verifiable trust flows without shared passwords.

Integrate customer provisioning, operator approval, runtime sessions and evidence verification through a small set of purpose-built SDKs.

Application
QVTM
Verified evidence

SDKs

Choose what you need to build

Choose the SDK based on the job your application needs to perform. Each SDK keeps the underlying protocol details behind a focused integration surface.

@qvtm/control-plane TypeScript
RC1

Provision customers, tenants, operators, users and invites from a backend or SaaS workflow.

npm install @qvtm/control-plane@0.1.0-rc1
qvtm-control-plane-swift Swift
RC1

Integrate mobile approval, challenge lifecycle and customer invite acceptance.

Swift Package Manager: sdk/swift/control-plane
qvtm-client-core Rust
RC1

Plan protocol and runtime requests or embed QVTM primitives into systems code.

cargo add qvtm-client-core --version 0.1.0-rc1
@qvtm/trust-verifier TypeScript
RC1

Verify signed evidence, trust status and transparency-backed proofs.

npm install @qvtm/trust-verifier@0.1.0-rc1
@qvtm/runtime-protocol TypeScript
RC1

Use runtime protocol sessions and message workflows.

npm install @qvtm/runtime-protocol@0.1.0-rc1

Integration model

Customer integration journey

Understand the integration by responsibility: what INFINITRUST prepares, what your developers implement, and what is validated together before production.

01

INFINITRUST

Foundation and provisioning

Establishes the customer boundary and issue the short-lived provisioning material your integration needs.

  1. 1

    Create customer

    Create the account that owns tenants, users, applications and invite workflows.

    Control Plane
  2. 2

    Create tenant

    Establish the boundary for devices, operators, policies and applications.

    Control Plane
  3. 3

    Issue provisioning token

    Issue a short-lived backend token. It must never be embedded in browsers or mobile apps.

    Control Plane
02

YOUR TEAM

Application integration

Installs the SDKs and connect QVTM to the identities, invites and application flows you control.

  1. 1

    Install SDK

    Install the control-plane, runtime and trust clients needed by the target integration.

    SDK distribution
  2. 2

    Create operator

    Create an operator identity that can receive access packages and approve QVTM login flows.

    Control Plane
  3. 3

    Create customer invite

    Create invite material the customer or operator can accept through the portal or mobile app.

    Control Plane
  4. 4

    Protect application

    Use QVTM state for application requests instead of shared passwords.

    Runtime Protocol + Trust
03

TOGETHER

Approval and trust validation

Execute the real approval path and verify the resulting evidence before the application relies on it.

  1. 1

    Scan QR and approve challenge

    Approve the SaaS login challenge without a password.

    Swift SDK + Control Plane
  2. 2

    Verify trust

    Check signed evidence and device or operator state before access is granted.

    Trust Verifier

Get started

Quickstarts

Run the smallest relevant workflow first, then expand into the full integration.

Backend customer invite

TypeScript

npm install @qvtm/control-plane@0.1.0-rc1
export QVTM_CONTROL_PLANE_URL=http://127.0.0.1:3100
export QVTM_PROVISIONING_TOKEN=<short-lived-token>
node sdk/examples/typescript/customer-integration-e2e.mjs

Mobile challenge lifecycle

Swift

cd sdk/swift/control-plane
swift test
swift package describe

SDK release gate

Multi-SDK

cd sdk/typescript && npm ci && npm run validate
node sdk/scripts/validate-distribution-manifests.mjs
node sdk/scripts/prepare-internal-release.mjs --dry-run
cd rust && cargo test -p qvtm-client-core