What is custody portability?
Custody portability is the ability to change, add, or operate multiple wallet and custody providers without rebuilding product flows, compliance controls, finance operations, risk processes, and audit evidence around each provider's model.
Provider lock-in usually hides inside operations, not contracts.
When a company integrates a wallet or custody provider, the provider model spreads into product, compliance, finance, risk, support, and engineering workflows. The switching cost becomes operational long before a contract renewal arrives.
Lock-in surfaces
- Wallet, vault, account, and address object models.
- Provider-specific transaction states and webhooks.
- Approval policy and risk review evidence.
- Finance reconciliation and reporting exports.
- Customer support and audit trails.
A neutral control plane gives teams leverage before migration day.
The goal is not to hide every provider difference. The goal is to standardize the workflows your business owns while preserving escape hatches for provider-specific operations.
Questions to ask before adding a second provider.
Transaction state
Can your team explain one canonical transaction lifecycle across all providers, including failed, canceled, replaced, and delayed states?
Policy evidence
Can you prove why a transaction was approved, rejected, escalated, or manually overridden?
Reconciliation
Can finance reconcile provider state, chain state, customer balances, and internal ledger state without manual cleanup?
Exit path
If a provider blocks a route, changes pricing, loses geography support, or fails an audit requirement, can you move without rewriting product operations?
Custody portability questions.
Is custody portability the same as multi-custody?
No. Multi-custody means using more than one provider. Custody portability means the business owns the operating layer well enough to add, switch, or combine providers without rewriting core workflows.
Does custody portability require self-custody?
No. A company can use Fireblocks, BitGo, Copper, Safe, self-hosted wallets, or future providers. The point is to keep business controls outside one provider's model.
Who should care first?
Teams moving stablecoins, running broker or exchange-like operations, entering new geographies, preparing audits, or adding redundancy to a single-provider wallet stack.
Map your custody portability risk with Alloy.
If you have one provider live and a second-provider trigger, Alloy wants to learn from your workflow.
This page is designed to be readable by buyers, search engines, and AI agents. Share it with engineering, compliance, and ops stakeholders.