> ## Documentation Index
> Fetch the complete documentation index at: https://musubinetwork.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration Overview

> Three things Musubi adds to your custody stack — Deploy, Console, Download.

Musubi doesn't ask you to rebuild your custody stack. It adds three things your organization operates: a backend you **Deploy**, a **Console** your ops team uses, and **Audit Exports** you download into your archive.

## What stays exactly as it is

| Existing system          | Role unchanged                                                                      |
| ------------------------ | ----------------------------------------------------------------------------------- |
| **Key management + HSM** | Your existing signing infrastructure protects the Canton Party ID key               |
| **Whitelist tooling**    | Whitelist the Musubi settlement address once, same model as every other destination |

None of these require Musubi-specific integration.

## Architecture

```mermaid actions=false theme={null}
graph LR
  subgraph NEW[Musubi — net-new in your infra]
    BE[Musubi backend<br/>REST + SSE]
    CP[Canton participant<br/>your Party ID]
    UI[Musubi console<br/>ops team logs in here]
  end

  subgraph DOWN[Your downstream systems]
    ACCT[Accounting]
    CRM[Client reporting]
  end

  UI -->|ops team review + co-sign| BE
  BE -->|audit exports| ACCT
  CP <-->|Canton protocol| SN[Settlement network]
  BE --- CP
```

Settlement records flow *out* of the Musubi backend as downloadable audit exports into your archive and accounting systems.

## The three pages in this section

<CardGroup cols={2}>
  <Card title="Deploy" icon="server" href="/custodian/integration/deploy">
    Canton participant + Musubi backend in your infrastructure. Provisioning, connectivity, TLS, Day-2 operations.
  </Card>

  <Card title="Console" icon="desktop" href="/custodian/integration/console">
    How your ops team works in the Musubi console — proposal inbox, quote review, co-signature, dashboards. No code.
  </Card>

  <Card title="Audit Exports" icon="download" href="/custodian/integration/audit-exports">
    CSV / JSON / PDF downloads by date range, intent, or status. The default integration path for your archive.
  </Card>

  <Card title="Programmatic Access" icon="code" href="/custodian/integration/programmatic-access">
    REST + SSE for custodians with real-time reconciliation needs. Java / Spring examples included.
  </Card>
</CardGroup>

For most custodians, Deploy + Console + Audit Exports covers the integration. Programmatic Access is the advanced path for custodians with downstream systems that can't consume scheduled downloads.