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, member identity, and settlement state. 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["Member identity"]
    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.

Non-custodial by construction

XKOVA is an orchestration layer, not a custodian. The asset owner signs every value transfer in their own wallet using EIP-712 typed data, the XKOVA Relayer submits the signed instruction on chain and pays gas, and XKOVA confirms the on chain result. Because the owner signs and the relayer submits, the application never holds a private key, and the transfer still settles on chain. Treasury movements follow the same idea with an N of M signer quorum on a multisig Safe. 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. Isolation is enforced in the database, so one tenant can never read another tenant's data. See Tenants and Workspaces.

Actor	Role
Member	An end user who holds balances and signs their own transfers.
Operator	Staff who run a tenant from the console.
Integrator	A backend that calls the API with a tenant API key.
Partner	A multi tenant integrator managing tenants on behalf of others.