Choose Your Scenario

There are two fundamentally different integration shapes for DCVs. Pick the one that matches your business model — the on-chain technical work is the same, but the onboarding and compliance paths differ.

Scenario A — You manage your own vaults

Pick this if:

• You're holding your own treasury in DCVs, or

• You're building a product where your own business is the client of Tesseract (not your end users), or

• You're an individual or a single institutional client deploying vaults for your own account, or

• You hold the relevant licenses on your side that allow you to operate a single vault with us and pool your own clients' assets inside it — get in touch and we'll be happy to discuss this path.

What it looks like:

1. You (or your company) complete KYC/KYB with Tesseract via compliance.tesseract.fi.

2. Your wallet gets whitelisted on-chain. From that point on, it can deploy and operate vaults directly against the contracts.

3. You deploy vaults, deposit, withdraw, select strategies, and read state — using the smart contracts and the Public API directly from your own infrastructure.

There's no separate partnership required — Tesseract treats this as a direct client relationship. The only real difference from using the Tesseract app is that you drive everything from your own backend or custodial signer instead of the web UI.

Go to → Scenario A: Manage Your Own Vaults

Scenario B — You manage vaults for your end users

Pick this if:

• You're a custodian, exchange, fintech, or wallet provider offering Tesseract DCVs to your own customer base, and

• Each of your end users will become a Tesseract client in their own right (either under their own KYC or under a reliance arrangement with Tesseract).

What it looks like:

1. You and Tesseract sign a partnership agreement and agree on the compliance split (reliance on your KYC, your users go through Tesseract's KYC, or a mix).

2. You're provisioned for Auth0 M2M access so you can onboard users into Tesseract's compliance system programmatically.

3. Optionally, you embed Tesseract's compliance app into your own product so users stay within your UI during KYC. (This integration is currently available on request — contact us for the detailed spec.)

4. For each cleared end user, the on-chain flow is the same as Scenario A — how you wire it up is flexible: each end user's wallet can be whitelisted individually, or you can operate vaults on their behalf from one or a group of partner-controlled wallets under a single account. Deposits / withdrawals / strategy assignments all happen against the same contracts.

Scenario B is a proper partnership and requires a commercial conversation before you can start technical integration. Once set up, the per-user on-chain steps link straight into the Scenario A material.

Go to → Scenario B: Manage Vaults for End Users

Not sure?

If you're unsure which scenario fits, start with Scenario A — it's what most partners begin with for internal testing, and it's always a prerequisite for understanding what Scenario B delegates to you vs. to your users.

If you need Scenario B but aren't yet in conversation with us, get in touch before going further.