# Step-by-step Guide for Integrating Tesseract Dedicated Client Vaults

Integrating Tesseract Dedicated Client Vaults into your own infrastructure can be streamlined by following these steps.

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

- [**Scenario A**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-a) — 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**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/scenario-b) — 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.

## Additional Resources
See also [**Indexing Vaults**](https://docs.tesseract.fi/dedicated-client-vaults/integration-guide/indexing-vaults) 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](https://docs.tesseract.fi/dedicated-client-vaults/reference).

Last updated 2 months ago.