Platform Overview

XKOVA is digital asset management for regulated institutions. This page shows how the pieces fit: the two product pillars, the orchestration layer they run on, the non-custodial model underneath, and the tenancy that isolates each institution.

Two product pillars

XKOVA ships two first-class products that share one set of rails.

• XKOVA SPS, the Stablecoin Payment System, moves value: payments, escrow and claims, treasury, settlement, and off-ramp.
• XKOVA TAMS, the Tokenized Asset Management System, issues and manages digital assets: programmable tokens, real-world assets, cap tables, distributions, and corporate actions.

The orchestration layer

XKOVA owns the orchestration: policy, ledger, audit trail, trusted identity-proof verification, scoped session authorization, and settlement state. The financial institution or authenticated digital channel remains authoritative for member identity. Around that core, every external connection is a swappable adapter, so an institution plugs in the providers it already trusts and is never locked into one stack.

flowchart TB
  subgraph CORE["XKOVA orchestration"]
    direction LR
    P["Policy and firewall"]
    L["Ledger and audit"]
    I["Identity proof and scoped session"]
    S["Settlement state"]
  end
  CB["Core banking"] --- CORE
  SC["Screening, KYT and BSA"] --- CORE
  KV["Identity, KYC and KYB"] --- CORE
  CV["Conversion and ramps"] --- CORE
  WP["Wallet providers"] --- CORE
  NW["Blockchain networks"] --- CORE

See Integrations and Orchestration for each connection and the vendors it supports.

Wallet custody and signed settlement

XKOVA never receives or exports human MPC private-key material. Every value transfer still needs a valid signature from the configured owner address, or the configured N of M quorum on a multisig Safe, before the XKOVA Relayer can submit and pay gas. Thirdweb MPC human wallets use a protected custom-JWT issuer that can bootstrap a general provider signing session, so XKOVA also freezes the business payload and verifies the exact signer and signature before acceptance. Externally controlled EOAs sign independently of that issuer. See the Non-custodial Model.

Tenants, workspaces, and actors

A tenant is an institution using XKOVA. A workspace is the operational scope inside a tenant where payments, treasury, tokens, and fees live. Every customer request is restricted to its authorized tenant and workspace. See Tenants and Workspaces.

Actor	Role
Member or account holder	An end user who holds balances and signs their own transfers.
Institution staff	A teller, operations, treasury, compliance, or commercial user entering through institution SSO or contextual launch.
Customer backend	A confidential server that calls customer APIs with a workspace credential.
XKOVA management user	A platform-management user of the private XKOVA Console.