Skip to main content
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

None of these require Musubi-specific integration.

​
Architecture

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

​
The three pages in this section

Deploy

Canton participant + Musubi backend in your infrastructure. Provisioning, connectivity, TLS, Day-2 operations.

Console

How your ops team works in the Musubi console — proposal inbox, quote review, co-signature, dashboards. No code.

Audit Exports

CSV / JSON / PDF downloads by date range, intent, or status. The default integration path for your archive.

Programmatic Access

REST + SSE for custodians with real-time reconciliation needs. Java / Spring examples included.
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.