A side-by-side comparison across custody models, regulatory standing, custodian optionality, key architecture, and asset coverage. Compare core elements to help banks, asset managers, fintechs, and trading firms decide who should hold their keys, who should hold the license, and whether those need to be the same party.
What to Look for in Digital Asset Custody
For banks, asset managers, and exchanges selecting a custodian, the shortlist used to build itself. A mandate requiring a federally supervised custodian narrowed the field to a single provider, and the evaluation was effectively finished before it began.
That filter no longer does the work. National trust bank charters are now held or conditionally approved across several providers, so a federal credential confirms that a custodian is supervised without saying much about how client assets are actually held. The questions that separate providers sit underneath the license:
- Who holds the keys, and who holds the license: These are separate questions the word custody hides. A regulated custodian model means the provider holds your assets and you are its client. A direct custody model means you hold and operate the assets on infrastructure you control, with a qualified custodian in the chain when a mandate requires one. They produce very different operating models.
- Whether you can change your mind later: Ask whether the technology can be used with a different custodian, and what a custodian change actually costs. If switching custodians means re-platforming, the custody decision is also a permanent decision.
- Switching providers: Ask what the end of the relationship looks like before you sign the start of it. Whether assets can move to another provider without the incumbent’s cooperation, whether key material or backups are yours to hold independently, and how long a migration actually takes.
The factors that decide most late-stage evaluations:
- Asset and chain coverage against your roadmap: Coverage varies widely here, and the process for adding a new asset varies more.
- Key architecture and whether it can be independently reviewed: Some providers publish their cryptography for external audit and some treat it as proprietary.
- Where policy is enforced: Approval rules that sit in application software behave differently under compromise than rules enforced in a hardware boundary.
- Compliance and deployment flexibility: Whether you can choose your own screening and Travel Rule providers, and whether the platform runs anywhere other than one vendor’s cloud.
- Insurance scope: Headline insurance figures differ by an order of magnitude across this group and often describe different things, so get the policy scope rather than the number.
Compare: Fireblocks vs. BitGo vs. Anchorage vs. Coinbase
| Category | Fireblocks | BitGo | Anchorage | Coinbase |
|---|---|---|---|---|
| Core Business Focus | Digital asset infrastructure where customers hold and operate their own assets, with qualified custody available through Fireblocks Trust or a partner | Regulated custody with prime trading, staking, and settlement bundled under BitGo’s own licenses | US national trust bank offering custody, staking and settlement, with prime brokerage delivered through affiliated Anchorage entities rather than the chartered bank | Vertically integrated crypto platform spanning retail exchange, Prime brokerage, custody, and derivatives via Deribit |
| ICP / Best For | Banks, fintechs, exchanges, and managers that want to own the operating model and keep custodian choice open | Institutions with a day-one qualified custodian mandate and a well-defined asset list | Funds, ETF issuers, and RIAs whose regulator or board specifically requires a federally chartered bank counterparty | Asset managers, ETF issuers, and institutions that want custody, execution, and financing from one supervised counterparty |
| Custody Model | Direct custody where the client holds key shares and operates assets under their own policy, with qualified custody as an option rather than a requirement | Provider-held qualified custody, where BitGo’s trust entities hold the assets and the client is their client, alongside a separate self-custody wallet line | Provider-held custody inside a national trust bank, with the client as a customer of the bank | Provider-held custody through Coinbase’s regulated custody entities |
| Custodian Optionality | Clients pair the platform with Fireblocks Trust Company or a licensed custodian from the Fireblocks Custody Network, available across eleven initial jurisdictions, and can switch without re-platforming | Within BitGo’s qualified custody, BitGo is the custodian, so a custodian change is a platform change | Custody sits with Anchorage Digital Bank, so a custodian change is a platform change | Coinbase’s separate developer platform offers both non-custodial wallets and custodial accounts, and its documentation for those accounts states that “Coinbase provides custody for assets in these accounts on behalf of your CDP entity” (docs.cdp.coinbase.com, custodial wallets overview, 17 September 2026), while the offering Coinbase documents as qualified custody is Prime, provided by Coinbase Custody Trust Company, a New York limited purpose trust company and Qualified Custodian (coinbase.com/prime, 17 September 2026) |
| Key Architecture | MPC-CMP published on GitHub with a universal composability proof and external audits, with policy enforced inside Intel SGX enclaves | Multi-signature and MPC key management, with documented policy rules that apply to transactions involving BitGo and a documented recovery path that bypasses them | HSM-based key management, with private keys generated and processed in air-gapped HSMs under Anchorage’s own signing logic, alongside an MPC option | MPC-based key management, with the optional Server-Signer for automated onchain co-signing documented for AWS deployment only |
| Chain and Asset Coverage | 200+ blockchains with thousands of supported assets across EVM and SVM networks, Bitcoin, Cosmos, Sui, and TON (fireblocks.com, 17 September 2026) | 97 protocols listed in BitGo’s own asset registry as of 9 September 2026, with more than 1,700 supported assets | 988 assets listed in Anchorage’s published asset registry, 978 of them available for custody on Anchorage Digital Bank and 623 on Anchorage Digital Singapore (docs.anchorage.com, 17 September 2026), with support added by request | 470 or more custodied assets in Prime Custody, with the self-custody wallet covering around 10 |
| New Asset Listing | Self-service token addition from the workspace, with new assets live in minutes and no vendor approval step | New assets and networks pass through an internal review before becoming available to customers | Every token is pre-approved and added by Anchorage’s team | New assets enter Prime Custody through Coinbase’s listing review process. Anyone can submit a token through the public “Request a review” form on Coinbase’s listings page, but Coinbase alone decides, and that page states Coinbase is “not able to respond to all submissions” (coinbase.com/listings, 17 September 2026) |
| Compliance and Deployment Optionality | Choose among Chainalysis, Elliptic, TRM Labs, and Notabene per workspace, deployed as SaaS, dedicated cloud, hybrid, on-premises, or multi-cloud TEE | Compliance integrations available with deployment delivered as a managed service under BitGo’s stack | Compliance operates inside the Anchorage perimeter with Anchorage’s own screening. Anchorage’s asset registry publishes availability by entity, Anchorage Digital Bank and Anchorage Digital Singapore, rather than by client jurisdiction, so confirm coverage for your entities directly (docs.anchorage.com, 17 September 2026). | Coinbase’s own screening, with Travel Rule handled through the TRUST network Coinbase operates; the one customer-deployed component Coinbase documents is the Prime Onchain Wallet server signer, which runs in the customer’s own AWS account, and as of 17 September 2026 its developer documentation sets out no on-premises or non-AWS deployment path |
| Enterprise Support | 24/7 global support with a 99.9% uptime SLA, named customer success, and self-service policy changes | Support tiers are set commercially and not published | Full-service model with account team involvement in operational requests | Institutional support scaled to the Prime and CaaS commercial tiers |
Fireblocks vs. BitGo
When Fireblocks is the better choice:
You need assets and chains added on your own schedule, you want to keep custodian choice open, and you want the operating model to belong to you rather than to your custodian.
Key Highlights of Fireblocks vs. BitGo:
- Coverage against a review process: Fireblocks operates 200+ blockchains with self-service token addition, so a new asset can go live in minutes. BitGo’s own asset registry lists 97 protocols as of 9 September 2026, and new assets enter a published submission-and-review process before they are enabled.
- Custodian portability: With Fireblocks, qualified custody comes from Fireblocks Trust Company or a licensed partner across eleven initial jurisdictions, and the custodian can change without re-platforming. On BitGo’s qualified custody, BitGo is the custodian, so there is no second-source option.
- Where policy is enforced: The Fireblocks Policy Engine runs inside Intel SGX enclaves with rules signed by admin quorum and encrypted in the enclave. BitGo’s own documentation states that recovery transactions using the user key and backup key “bypass any policies you may have in place with BitGo” (BitGo, Policies Overview, 17 September 2026).
- Cryptography your security team can read: Fireblocks publishes its MPC-CMP implementation on GitHub with a universal composability proof and external audits, so the protocol can be independently reviewed rather than accepted.
- Settlement without an intermediary: Fireblocks provides direct exchange and trading venue connectivity alongside the Fireblocks Network, reaching 2,500+ counterparties and 40+ providers across 100+ countries through one integration. BitGo’s own trading agreement states that clients face BitGo Trust as the contra-party to every transaction, and settlement runs through Go Network venues, so each expansion depends on BitGo adding it.
Summary:
BitGo’s position strengthened materially in the last year. IOn 12 December 2025 the Office of the Comptroller of the Currency (OCC) approved BitGo’s conversion from a South Dakota state trust company to a federally chartered national trust bank, BitGo Bank & Trust, National Association, one of five national trust bank charter approvals the OCC announced that day (OCC news release NR 2025-125, 12 December 2025). BitGo also operates BitGo New York Trust Company, LLC, a qualified custodian regulated by NYDFS. Cold storage holdings carry insurance up to a $250 million policy limit, which is a scored line in many RFPs. For a US institution with a hard-qualified custodian mandate, a defined asset list, and no appetite to run infrastructure, BitGo delivers a coherent answer.
Fireblocks leads when the mandate is to build rather than to outsource. The difference is not whether BitGo is a capable custodian, it is that choosing BitGo means BitGo holds the keys, sets the asset list, and intermediates the settlement, and none of those can be changed without changing platforms. Bakkt and Sygnum Bank both operate their own regulated custody offerings on Fireblocks infrastructure rather than becoming a custodian’s client.
Fireblocks vs. Anchorage
When Fireblocks is the better choice:
You want infrastructure you own and operate, cryptography that can be externally audited, chain coverage that moves with your roadmap, and no dependency on a provider that also runs a trading desk and settlement network.
Key Highlights of Fireblocks vs. Anchorage:
- Cryptography open to review against proprietary firmware: Fireblocks published MPC-CMP on GitHub with a universal composability proof and external audits, so a security team can inspect the protocol. Anchorage documents air-gapped HSMs running its own custom signing logic and does not publish that implementation for public review as of 17 September 2026, though its SOC 2 Type 2 examination is scoped to private key generation, signing and authentication, and it is OCC-examined. Anchorage added an MPC-based option through a cloud partnership, which matters given how the two models are usually contrasted.
- Treasury operations at volume: Fireblocks ships automated sweeping, threshold rebalancing, scheduled top-ups, and gas management as platform features. Anchorage’s gas station covers network fees transaction by transaction: once a withdrawal or transfer is approved, an address controlled by Anchorage deposits the estimated network fee into the wallet for that transaction, and as of 17 September 2026 it is documented for ETH, ERC-20 and SOL withdrawals and transfers plus ETH staking (Anchorage Digital, Sending assets, 17 September 2026).
- What sits downstream of your flow: Fireblocks operates no trading desk, exchange, or settlement network, and integrates the custodians, liquidity providers, and compliance vendors a customer selects. Anchorage runs Anchorage Digital Prime and Atlas settlement alongside its custody business, with agency trading provided by Anchorage Hold LLC and principal trading by A1 Ltd.
- Platform breadth: Fireblocks covers custody, payments, tokenization with permissioned contract templates across 35+ chains, embedded wallets, and reconciliation on one platform. Anchorage’s token management product came through its Hedgey acquisition and covers cap tables, vesting and distributions rather than contract deployment, and its issuance work runs through Anchorage’s own bank as the stablecoin issuer rather than as an engine a customer operates.
Summary:
Anchorage has held an OCC national trust bank charter since January 2021. For a mandate where the regulator, the LP, or the board specifically requires a federally chartered bank counterparty, Anchorage clears that on day one. Anchorage also carries ETF and asset manager references that land in committee, including additional custodian status on BlackRock’s spot Bitcoin ETF, and consolidates custody, prime trading, settlement, staking and stablecoin issuance across the Anchorage group.
Fireblocks leads when the institution intends to operate rather than delegate. Buying Anchorage means becoming a customer of Anchorage’s bank, its asset list, its trading desk, and its settlement network, which is a reasonable trade for the buyer who wants exactly that and a constraint for everyone else. Where a federal charter is genuinely mandated, the two coexist, with the charter satisfying the mandate and Fireblocks running the platform. ABN AMRO used Fireblocks for the digital wallet on the first digital green bond registered on public blockchain by a Dutch bank (ABN AMRO, 12 September 2023), and WisdomTree secures private keys in WisdomTree Prime with Fireblocks MPC wallet technology (WisdomTree, 23 May 2022).
Fireblocks vs. Coinbase
When Fireblocks is the better choice:
You want one platform that spans self-custody and qualified custody without changing product lines, and you want to change custodian without re-platforming, you need chain coverage and listing velocity beyond a formal process, and you want infrastructure from a provider that does not run a competing exchange, hold retail customer relationships, or take proprietary positions.
Key Highlights of Fireblocks vs. Coinbase:
- Technology separate from custody: Fireblocks separates orchestration from custody, so a customer can run the platform with Fireblocks Trust Company or a licensed partner and change custodian without re-platforming. Coinbase splits the two across product lines instead: the custody it documents as qualified sits inside a Coinbase custody entity you contract with, while its developer platform offers separate custodial accounts and non-custodial wallets outside that entity (docs.cdp.coinbase.com, 17 September 2026). Coinbase’s own documentation states that non-custodial wallets “do not require a custodial account” (Coinbase Developer Platform, payments overview, accessed 8 September 2026).
- Chain coverage and listing velocity: Fireblocks operates 200+ chains with customer-controlled token addition. Coinbase Prime Custody supports 52 chains with 470 or more custodied assets, its institutional self-custody wallet covers roughly 10 networks, and new assets enter Prime Custody through a formal listing process with no customer-initiated path, with long-tail assets reachable only outside custody through the non-custodial Onchain Wallet.
- Compliance and deployment choice: Fireblocks lets each workspace select Chainalysis, Elliptic, TRM Labs, or Notabene, and deploys as SaaS, dedicated cloud, hybrid, on-premises, or multi-cloud TEE. Coinbase pairs its own screening with the TRUST Travel Rule network it operates, and publishes one customer-cloud option, the Prime Onchain Wallet server signer, which the customer deploys into their own AWS account through an AWS CloudFormation template; as of 17 September 2026 its developer documentation sets out no on-premises or non-AWS path (docs.cdp.coinbase.com, Prime server signer setup).
- Counterparty reach: Fireblocks connects 2,500+ counterparties for authenticated settlement plus 35+ exchanges and trading venues. Coinbase Prime routes through a connected-venue list that client ETF filings state is subject to change and currently includes Bitstamp, LMAX, Kraken, the exchange Coinbase operates, and four additional unnamed non-bank market makers (Bitwise NEAR ETF Form S-1/A, filed 16 September 2026), with instant transfers between Prime accounts rather than across an open counterparty network.
- Whether the platform is neutral about assets and chains: As of 17 September 2026 Coinbase describes its payments stack as “Multichain by design. Led by Base, Coinbase’s purpose-built Ethereum L2” (coinbase.com/payments), so the default onchain path is a network Coinbase owns.
Summary:
Coinbase Custody Trust Company has been NYDFS-chartered as a qualified custodian since October 2018, a separate new entity, Coinbase National Trust Company, received preliminary conditional approval from the OCC on 2 April 2026 with Coinbase’s custody business set to migrate to it over a three-year de novo period, it holds MiCA authorization through Luxembourg with an EU-wide passport, and Coinbase Custody Trust Company maintains SOC 1 Type II and SOC 2 Type II audits by Deloitte & Touche (coinbase.com/prime, 17 September 2026). It is custodian to most US spot Bitcoin ETF issuers. For a buyer whose primary criterion is board-level familiarity and single-vendor breadth, that is a strong case.
Fireblocks leads on ownership and neutrality. The structural difference is that qualified custody on Coinbase means becoming a client of a Coinbase custody entity, and the provider making that offer also competes in exchange, brokerage, and consumer finance. Revolut and GSR made comparable calls on neutrality and network reach.
Why Teams Choose Fireblocks for Digital Asset Custody
- You hold the keys and set the rules: MPC-CMP distributes key shares so no complete private key exists in one place, with every transaction governed by the Policy Engine inside Intel SGX before signing.
- Qualified custody as an option, not a condition: Pair the platform with the NYDFS-chartered Fireblocks Trust Company or a licensed custodian from the Fireblocks Custody Network, available across eleven initial jurisdictions, and change custodian without re-platforming.
- Cryptography your security team can audit: MPC-CMP is published on GitHub with a universal composability proof and external audits, so the protocol is open to review rather than taken on trust.
- Coverage that moves at your pace: 200+ blockchains with self-service token addition, so a new asset ships in minutes without a listing committee.
- No competing business downstream of your flow: Fireblocks runs no exchange, no trading desk, and issues no stablecoin of its own, and integrates the venues, issuers, and compliance vendors you choose.
- Deployment and compliance on your terms: SaaS, dedicated cloud, hybrid, on-premises, or multi-cloud TEE, with Chainalysis, Elliptic, TRM Labs, and Notabene selectable per workspace.
Custody used to be a question about who was allowed to hold your assets. With federal charters now held by several providers, it is increasingly a question about who operates the platform underneath, and $16T in lifetime digital asset transactions across 2,500 organizations runs on this answer.
Ready to Compare Hands-On?
→ Explore Fireblocks Trust Company
→ Check out our customer stories
FAQs
-
Is Fireblocks a qualified custodian?
Fireblocks Trust Company, LLC is chartered as a limited-purpose trust company by the New York State Department of Financial Services to engage in Virtual Currency Business Activity, and provides qualified custody with client assets held fully segregated and on an insolvency-remote basis. -
Do we have to use Fireblocks custody to use the platform?
No. Custody and orchestration are separate, so a customer can run the platform in direct custody, with Fireblocks Trust Company, or with a partner custodian, and change that arrangement without re-platforming. That separation is the main structural difference between Fireblocks and the provider-held custody models in this comparison. -
Our mandate requires a federally chartered bank custodian. What then?
Fireblocks Trust Company, LLC is chartered as a limited-purpose trust company by the New York State Department of Financial Services to engage in Virtual Currency Business Activity, and provides qualified custody with client assets held fully segregated and on an insolvency-remote basis. -
Where are the keys and who can move assets?
MPC-CMP splits key shares so a complete private key never exists in one place, with the customer holding a share. Every outbound transaction is evaluated by the Policy Engine inside Intel SGX before signing, and policy changes require admin quorum approval, so no single party can move assets unilaterally. -
How long does it take to support a new asset?
Customers add tokens themselves from their workspace and see them live in minutes on supported chains, with no support ticket or listing approval. This is the most frequently cited operational difference against provider-held custody models, where new assets pass through an internal review process. -
Can we choose our own compliance providers?
Yes. Chainalysis, Elliptic, TRM Labs, and Notabene are selectable per workspace, so screening and Travel Rule providers can be chosen and changed to match your obligations rather than inherited from the platform. -
What deployment options exist?
SaaS, dedicated cloud, hybrid, on-premises, and multi-cloud trusted execution environments including Intel SGX, AWS Nitro Enclaves, and GCP Confidential Space. Deployment flexibility matters most for banks and regulated institutions with data residency requirements or an existing HSM estate to integrate.
Last Updated: September 2026. Competitive comparisons are based on publicly available information. Features and capabilities are subject to change.