A crypto startup can hold customer assets itself, rely on a regulated custodian or keep users in control throughout each transaction. That decision affects security, recovery, compliance and the product experience from the first release. How should a founder decide where custody belongs?
Custody Starts With the Private Key
Private-key control defines the basic difference between custodial and non-custodial models. Custodial exchanges hold the keys for customer assets, while non-custodial services leave control with users. Kraken, Sumsub and Stripe all place key ownership at the center of their comparisons.
That choice determines the company's operational workload. A custodial exchange needs wallet infrastructure, withdrawal permissions, reconciliation, access controls and account recovery procedures. A non-custodial product needs secure wallet software and reliable transaction processing, with users handling key protection and transaction approval.
The same architecture shapes the customer experience. Custodial platforms can offer password resets and account support, while self-custody relies on recovery phrases or other key-management methods. Stripe also notes a practical distinction in transaction handling: custodial services can assist with certain errors, while a signed blockchain transaction generally creates a final settlement event for a self-custody user.
Custody therefore sets the boundaries of responsibility. The choice determines who handles lost credentials, compromised accounts, transaction failures and user mistakes.
The User Experience Changes With Custody
Convenience has a technical source. A custodial platform can maintain an internal ledger, so transfers between users on the same platform may happen without an on-chain transaction. External withdrawals then require blockchain settlement and can involve network fees and confirmation time. Kraken and Sumsub both identify this distinction when discussing transaction speed and fees.
Self-custody creates a more direct relationship with the blockchain. The user approves transactions from a wallet they control and pays the relevant network costs. This suits DeFi applications, on-chain trading and products where direct asset control forms part of the user experience.
Privacy also follows the architecture, although it should be described carefully. Custodial services commonly connect transactions with an account and may apply KYC and AML controls. A self-custody wallet can interact with blockchain applications without an exchange account, while blockchain transactions themselves can remain publicly visible. Kraken and Sumsub both distinguish account-based compliance from self-custody transaction control.
For a founder, this creates a useful design question: what kind of friction does the target customer actually accept? A beginner-facing financial app may benefit from recovery and account support. A product built around DeFi transactions may gain more from direct wallet interaction.
The USDT-to-XMR Example
Consider a user holding USDT on Ethereum who wants XMR in a Monero wallet. The transaction has a clear endpoint: the user provides the source asset and receives XMR at an address they control.
A non-custodial exchange such as ChangeNOW can handle the conversion while sending the resulting asset to the user's wallet rather than maintaining a long-term trading balance. A user looking to convert USDT to XMR therefore keeps control of the receiving wallet throughout the transaction.
The model also differs from a DEX. DEXs generally rely on smart contracts and on-chain liquidity, while swap services can coordinate execution through their own infrastructure and liquidity partners. For founders, this means different engineering requirements: custodial exchanges need account infrastructure, DEXs require smart-contract and liquidity systems, while non-custodial swap services focus on routing, settlement and transaction monitoring.
Security Moves With Control
Custody concentrates security responsibility inside the company. Private-key management, withdrawal approvals, access permissions and reconciliation become part of the platform's internal control environment. Coinbase's filings provide a concrete example of the scale involved. The company says it holds full keys for crypto assets and stablecoins managed for customers, uses hot and cold wallet systems and requires multiple human approvals for private-key operations. It also describes reconciliation between its wallets and blockchain data.
Self-custody moves a larger share of security responsibility to the user. Phishing, malware, compromised devices, malicious transaction approvals and lost recovery phrases can all result in asset loss. Sumsub and Stripe both identify key loss and user-side security as central self-custody risks.
Neither architecture removes risk. The location of the risk changes. A custodial founder builds controls around a concentrated pool of customer assets. A non-custodial founder builds controls around software integrity, transaction safety and user education.
What FTX and Coinbase Show Founders
The FTX collapse shows how custody, software permissions and corporate governance can become connected. The U.S. Department of Justice said Sam Bankman-Fried misappropriated billions in customer funds and directed code changes that allowed Alameda to withdraw effectively unlimited amounts of cryptocurrency.
The case puts operational controls at the center of custody design. Once a company controls customer wallets, access policies, segregation, reconciliation and withdrawal approvals become part of its financial control system.
Coinbase shows what mature custody infrastructure requires. Its 2025 annual report describes segregated accounts, cold storage, distributed approval processes and internal reconciliation, alongside measures designed to keep custodied assets separate from claims against general creditors.
The wider market includes several custody models. A 2026 comparison of Coinbase alternatives covers centralized exchanges such as Kraken, Binance and OKX alongside non-custodial services. For founders, these models show how custody choices shape the infrastructure behind trading products.
A startup therefore needs to budget for security engineering, compliance, audits, monitoring and incident response when it takes on custody.
Which Model Fits the Product?
The choice becomes clearer when the founder maps the actual customer journey:
- Persistent balances: Does the product need users to keep assets inside an account between transactions?
- Transaction authorization: Should every blockchain movement require a signature from the user's wallet?
- Recovery: Can support restore access after a lost password or compromised device?
- Trading mechanics: Does the product need an order book, internal transfers and advanced trading functions?
- Settlement: Does the service convert assets directly between external wallets?
- Security responsibility: Who protects private keys and approves withdrawals?
- Regulatory perimeter: Which entity receives assets and which entity performs the regulated service?
A custodial architecture fits products built around persistent balances, account-based trading and institutional services. A non-custodial model can fit wallets, direct swap products and applications centered on on-chain activity.
There is also a hybrid route. A startup can keep everyday transactions self-custodial while using a regulated custodian for a separate institutional product. The same company can therefore operate different custody models when its products have different transaction requirements.
External Infrastructure Changes the Build Decision
A founder does not always have to build the entire exchange stack internally. Wallets and crypto applications can connect to external execution providers, liquidity networks or swap infrastructure while retaining control over their own customer-facing experience.
ChangeNOW's integrations provide useful examples. Its partner materials describe integrations with products including Guarda and Rubic, where exchange functionality can sit inside another crypto application's workflow. That model can reduce the amount of chain-specific exchange infrastructure a small team needs to maintain.
The trade-off moves toward dependency management. The founder now needs to assess provider reliability, supported assets, settlement procedures, pricing, compliance arrangements and failure handling. A non-custodial architecture can reduce direct custody exposure while creating reliance on external infrastructure.
Regulation Is Part of the Architecture
Custody also changes the regulatory perimeter. Under MiCA, regulated crypto-asset service providers face requirements around custody and other crypto-asset services, while ESMA has continued to emphasize authorization requirements for firms serving EU users.
The useful legal questions follow the transaction itself: who receives the asset, who controls the key, who executes the conversion and which entity provides the regulated service?
Outsourcing can change the answer to the first three questions without removing the fourth. A founder therefore needs legal review alongside technical architecture before choosing a custody provider or exchange infrastructure partner.
AI can support transaction analysis, documentation and internal monitoring. Human teams still need to review security controls, legal structures and decisions involving customer assets.
Three Possible Market Paths
In a base scenario, custodial exchanges continue to serve trading and institutional products while non-custodial services grow around wallets, payments and direct asset conversion.
An optimistic scenario brings clearer regulatory treatment and more standardized infrastructure. Smaller teams gain easier access to compliant custody, liquidity and execution services.
A stress scenario follows another major custody failure or security event. Exchanges face stronger segregation and control requirements, while founders place greater emphasis on limiting direct control over customer assets.
A sound architecture should work under all three conditions. The key test is whether responsibility for assets, transactions and failures stays clear as the business grows.
What the Custody Choice Means for a Founder
Custody affects far more than wallet security. It shapes the user experience, regulatory obligations, engineering workload and consequences of a system failure. FTX shows the cost of weak centralized controls, Coinbase shows the infrastructure required for mature custody and ChangeNOW demonstrates how direct asset conversion can operate through a non-custodial model.
The transaction flow provides a practical starting point: identify who controls the asset at each stage, then build the product around those responsibilities.
FAQ
What is a custodial exchange?
A custodial exchange controls the private keys associated with customer assets and manages balances through its own infrastructure.
What is a non-custodial exchange?
A non-custodial exchange facilitates conversion or trading while users retain control of their wallets and private keys.
Is self-custody safer?
Self-custody reduces reliance on a third-party custodian while placing greater responsibility on the user for keys, devices and transaction approvals.
Why do users choose custodial exchanges?
Account recovery, customer support, internal transfers and familiar trading interfaces can make custodial platforms easier to use.
Why do users choose non-custodial services?
Direct asset control, on-chain interaction and access to decentralized applications make self-custody attractive to many experienced crypto users.
What did FTX demonstrate?
The FTX case showed how privileged software permissions and misuse of customer deposits can create severe custody and governance failures.
Does a non-custodial exchange eliminate security risk?
No. Users can still lose assets through phishing, compromised devices, malicious approvals or lost recovery credentials.
Can a startup combine both models?
Yes. Different products within one business can use different custody architectures when their transaction flows and customer requirements differ.
Does MiCA regulate crypto custody?
MiCA establishes requirements for regulated crypto-asset services in the EU, including requirements relevant to custody and service authorization.
Can AI operate an exchange independently?
AI can assist with monitoring, analysis and documentation. Human oversight remains necessary for security, legal and custody decisions.
Disclaimer
This article is for informational purposes only and does not constitute financial, legal or investment advice. Crypto-asset services involve technical, operational and regulatory risks. Founders should obtain qualified professional advice before launching a product involving customer assets.
