# Integration Guide

Step-by-step instructions for integrating Tesseract Dedicated Client Vaults into your own infrastructure.

Start with [**Choose Your Scenario**](/dedicated-client-vaults/integration-guide/choose-your-scenario.md) to pick the right path based on your business model. The rest of this guide is organized into two scenarios:

* [**Scenario A**](/dedicated-client-vaults/integration-guide/scenario-a.md) — you're managing vaults for yourself (treasury, own product). You onboard directly through Tesseract's compliance, your wallet gets whitelisted, and from there you deploy and operate vaults against the contracts directly.
* [**Scenario B**](/dedicated-client-vaults/integration-guide/scenario-b.md) — you're managing vaults on behalf of your own end users (custodian model). You become a Tesseract partner, align on a compliance model, onboard users through an M2M integration, and then run the same on-chain operations per-user.

Both scenarios converge on the same technical surface. Scenario B layers additional partnership and compliance steps on top of everything in Scenario A.

See also [**Indexing Vaults**](/dedicated-client-vaults/integration-guide/indexing-vaults.md) for data-consumer use cases — pulling vault lists for your own addresses via the Public API, or indexing every vault Tesseract creates on-chain.

For canonical addresses, method signatures, and API references used throughout this guide, see [Reference](/dedicated-client-vaults/reference.md).