Skip to main content
Your Musubi integration runs on your own infrastructure with strict data isolation. The settlement network enforces visibility boundaries at the protocol level — you cannot see data you’re not entitled to, and no one can see your data without authorization. One boundary is worth reading before the table below: co-signing a settlement makes you a party to it, so what reaches you after winning is wider than what reaches you while quoting.

​
Authentication

In production, JWT issuance integrates with your organization’s identity provider.

​
Data Isolation

Your backend and database run in your infrastructure. They contain only your data: No participant can access another participant’s backend or database. Communication between participants flows exclusively through the settlement network protocol.

​
Visibility Boundaries

The settlement network enforces what data reaches your node:
The Never rows are enforced at the network protocol level: that data is not transmitted to your infrastructure at all, and no access-control setting stands between you and it.Counterparty identity is different, and we state it plainly. It does not reach you while quoting. It does reach you at settlement, because settlement is one atomic transaction you co-sign and the settled order — naming both institutions and both custodians — is disclosed to every co-signer’s node. Musubi’s market-maker API and console read a separate identity-free record and return none of it, but the underlying data is in your read store, and in anything you export or back up from it. See the Privacy Model.

​
What You Control