Crypto Custody Platforms for Banks Compared
Part of our guide to digital asset security for banks

Quick answer. Banks that hold crypto themselves can license a custody platform such as Taurus-PROTECT, Ripple Custody, Fireblocks, BitGo or GK8. Compare them on key model (HSM, MPC or offline vault), deployment, certifications and which bank users are named.
Video transcript
Banks holding crypto themselves can license a custody platform. The real choice is who runs signing, because a license alone does not prove the bank controls the keys.
There are four routes: build, license and self-host, hybrid or SaaS, or sub-custody. None of them moves accountability off the bank.
Three key models recur. HSM-first keeps master keys in certified hardware. MPC-first splits keys into shares. The third is an offline vault, as with GK8.
Here are five platforms, listed alphabetically, not ranked. Every claim is the vendor's own, taken from its public pages.
Treat named bank users with care. State Street reported Taurus PROTECT live in production, but did not publish who holds which keys or how recovery works.
Every certification has a scope. FIPS one forty two validates a cryptographic module, such as an HSM, not the platform, and NIST moved all those certificates to its Historical list in September 2026.
Keep approvals separate from the key store. An HSM or MPC cluster signs what it is asked to sign. The policy engine decides what gets asked.
Ask who can sign without the bank, whether you can recover without the vendor, which report covers your deployment, and how you exit.
Read the full comparison. Guardian's Digital Asset Assurance Pilot reviews custody and key ceremony design, and pentests the consoles, APIs and signing services that can reach your keys.
Build, Buy or Sub-Custody
A crypto custody platform for banks is software a bank licenses to hold client crypto under its own keys and controls. Choosing one is an operating-model decision first.
For national banks and federal savings associations, the OCC's Interpretive Letter 1184 of May 7, 2025 confirmed they may provide crypto custody and may use sub-custodians, subject to third-party risk management.[1]
On July 14, 2025, the Federal Reserve, FDIC and OCC said existing risk-management principles apply to crypto safekeeping. Their statement creates no new supervisory expectations, but safekeeping must still be safe and sound.[2]
In the EU, DORA has applied since January 17, 2025. The EBA says in-scope entities need a register of contractual arrangements with ICT third-party providers.[3]
So the real choice is who runs signing. There are four routes.
| Route | Who runs signing | What the bank still owns |
|---|---|---|
| Build | The bank, on code it writes | Every layer, including the cryptography |
| License and self-host | The bank, on vendor software and its own HSMs | Operations, upgrades, recovery and vendor oversight |
| License, hybrid or SaaS | Bank and vendor, split by component | Oversight of each vendor-hosted part |
| Sub-custody | A custodian holding the keys | Third-party risk management of the custodian |
Platforms Compared
A license alone does not prove the bank controls the keys, and no route moves accountability off the bank.[1, 2]
If a provider will run custody for you, read our crypto-as-a-service for banks guide. To pick a sub-custodian, see best crypto custodians.
We compare five that publish bank-facing self-custody material: BitGo, Fireblocks, GK8, Ripple and Taurus. Other MPC platforms, and who holds their key shares, are in our MPC wallet providers comparison.[4, 5, 6, 7, 8]
The table is alphabetical, not a ranking. Every claim is the vendor's own, from its public pages.
| Platform | Key model, as stated | Deployment, as stated | Bank users named |
|---|---|---|---|
| BitGo | HSMs, air-gapped cold vaults; MPC or multisig | Fully on-premises, BitGo managed or hybrid | None on its bank page |
| Fireblocks | MPC-CMP; existing HSMs via Key Link | Cloud, hybrid or on-premises | BNY Mellon, BNP Paribas, ANZ, NAB, ABN AMRO, BTG Pactual (2023 list) |
| GK8 (Galaxy) | Offline vault; optional iHSM or SSM | Self-managed; optional bring-your-own server | None on its TradFi page |
| Ripple Custody | Client HSM or MPC cluster; hot, warm and cold | On-premises, SaaS or hybrid | DZ BANK, VP Bank |
| Taurus-PROTECT | FIPS 140-2 Level 3 or 4 HSMs, plus MPC | SaaS, hybrid or fully on-premises | State Street, Deutsche Bank, CACEIS, Swissquote |
Each Platform in Brief
Taurus-PROTECT is HSM-first. Taurus says its HSMs store master keys, derive signing keys and run the policy engine, with offchain approval quorums backed by hardware tokens.[9]
State Street selected Taurus in August 2024 for custody and tokenization, subject to regulatory approval. In July 2025 it reported Taurus PROTECT live in production inside its own infrastructure.[10, 11]
On January 15, 2026, State Street launched a Digital Asset Platform with wallet management and custody capabilities; that release does not name a technology provider.[12]
State Street did not publish who holds which keys or how recovery works. A named bank user is not proof the bank runs the keys itself.
Ripple Custody keeps private keys in the client's own HSM or MPC cluster. Ripple describes its Vault as a secure gateway to that client-managed key management system.[13]
In February 2026, Ripple added Securosys CyberVault HSM and CloudHSM support, on premises and in the cloud.[14]
Ripple's custody page features DZ BANK, which chose Metaco Harmonize in February 2023.[6, 15]
VP Bank, the other named Harmonize bank, runs it as a managed service integrated with its core banking system.[16]
Fireblocks is MPC-first, using MPC-CMP with hardware-backed isolation. Its bank list comes from a June 2023 announcement.[4, 17]
BitGo offers self-custody with bring-your-own licensing, beside its own licensed crypto-as-a-service. Its bank page lists role-based approvals, velocity limits and whitelisting.[8]
In its 2-of-3 self-custody model, the customer holds the user and backup keys. BitGo keeps a platform key, protected by HSMs.[18]
GK8, owned by Galaxy, builds around an offline vault with no digital input and one-way communication. Its TradFi page names no bank in production.[7]
Self-Custody Key Models and Deployment
Three key models recur. HSM-first platforms keep master keys inside certified hardware the bank can own and operate.[5, 9]
MPC-first platforms split keys into shares. Fireblocks says a customer can keep a critical share inside its own hardware, or run HSMs as sole signing authority.[19]
Offline-vault platforms such as GK8 are the third model. Some vendors combine models: Ripple and Taurus each support both HSM and MPC.[6, 7]
Our HSM vs KMS guide covers hardware choices.
Taurus describes on-premises custody as infrastructure the bank controls, with no vendor-hosted signing component.[20]
Ripple documents mirroring its signed container images into a bank's private registry before installation.[21]
Keep the approval layer separate from the key store. An HSM or MPC cluster signs what it is asked to sign; the policy engine decides what gets asked.
Map where each component runs and who can reach it:
- Key material: HSMs, MPC nodes or offline vault, and who has physical and logical access.
- Policy engine: which server enforces approval rules, and whether any path signs around it.
- Approver devices and hardware tokens, and how a lost one is revoked.
- Console and APIs: the identity provider, network exposure and admin roles.
- Software supply: who builds, signs and installs each release.
- Backups and recovery material: sites, custodians and the quorum to use them.
- Vendor support access: who approves it and where it is logged.
Certifications
Every certification has a scope: the vendor's company, its hosted service or the software you run.
FIPS 140-2 validates a cryptographic module, such as an HSM, not the custody platform built around it.[22]
NIST moved all FIPS 140-2 certificates to its Historical list on September 22, 2026, for use in existing systems only.[23]
Ask for each module's certificate number and whether a FIPS 140-3 validation exists.
A vendor's SOC 2 on its hosted service says little about a copy on your hardware. Self-host, and your own controls become the audited ones.
How SOC 2, ISO 27001 and CCSS differ is set out in our security standards comparison.
| Platform | Published claim | Ask for |
|---|---|---|
| BitGo | SOC 1 Type 2, SOC 2 Type 2 and CCSS listed in its trust center | Whether any report covers self-custody, on-premises or hybrid deployments |
| Fireblocks | SOC 2 Type II, ISO 27001, 27017, 27018, 22301; CCSS QSP Level 3 | Report period, scope, exceptions and user-entity controls |
| GK8 | SOC 2 Type II renewal claimed 2022; iHSM FIPS 140-2 Level 3 cyber | SOC 2 boundary, period; FIPS 140-3 certificate, or 140-2 number and status |
| Ripple Custody | SOC 2 Type II and ISO 27001 compliant; FIPS via partners | Audited reports and scope; FIPS 140-3 certificate, or 140-2 number and status |
| Taurus-PROTECT | ISO 27001; ISAE 3402 audit of key generation and backup | Whether the audit covers your deployment model |
Questions to Ask
For EU banks, DORA Articles 28 to 30 cover ICT third-party principles, concentration risk and key contract terms; ask counsel which apply to the platform contract.[24]
Our guide to crypto custody controls examiners expect covers key lifecycle, sub-custodian and DORA contract evidence in depth.
Then test the build: try a signature that skips policy, and witness the first key ceremony.
| Question | Evidence to ask for | Red flag |
|---|---|---|
| Who can sign without the bank? | Quorum map across bank, vendor and cloud | Vendor-held keys or shares can reach quorum, or vendor holds a recovery key |
| Is the reference true self-custody? | Reference call naming the model: self-hosted, managed or white label | Live in production, model unnamed |
| Can we recover without the vendor? | Dated recovery drill on bank hardware | Recovery needs vendor staff or systems |
| Where does policy run? | Architecture diagram and policy change log | Admin or recovery path skips policy |
| How do releases reach us? | Signed images, private registry, support calendar | Vendor pushes updates directly |
| Which report covers our deployment? | Report scope naming our model | Certificates cover only the vendor's offices |
| How do we exit? | Key export path and a tested migration | Keys locked in a proprietary format |
Test the platform before it holds client assets
Guardian's Digital Asset Assurance Pilot reviews custody and key ceremony design, reads DORA and other standards as demands on it, and pentests the consoles, APIs and signing services that can reach your keys.
Frequently Asked Questions
How often does an on-premises custody platform need upgrading?
Ripple's schedule is one example. Its long-term support releases for on-premises customers come about every six months. The current one, v1.43, shipped October 5, 2026 and is supported to October 5, 2027. SaaS releases come about every four weeks.[25]
Is an on-premises software license an ICT service under DORA?
The Commission's answer published January 22, 2025 calls the ICT-services definition intentionally broad and says each entity must assess its services. Implementing Regulation 2024/2956 lists licensing software run on premises as an ICT service type.[26, 27, 28]
Can a bank keep its existing HSMs with an MPC platform?
Fireblocks says it can. Its HSM Key Link connects existing HSM systems through zero-knowledge proof verification, giving access to its wallet features without replacing current infrastructure. Ask which HSM models and firmware versions it supports.[4]
Related reading
- what is a key ceremony
- third party risk management digital assets
- bank crypto trading security architecture
- crypto custody
Sources
- Office of the Comptroller of the Currency: Interpretive Letter 1184, Clarification of Bank Authority Regarding Crypto-Asset Custody Services
- Federal Reserve: Agencies issue joint statement on risk-management considerations for crypto-asset safekeeping
- European Banking Authority: Preparations for reporting of DORA registers of information
- Fireblocks: Fireblocks Buyer’s Guide for Banks and Financial Institutions
- Taurus Developer Hub: Taurus Technology and Products
- Ripple: Digital Asset Custody Products for Institutions
- GK8 by Galaxy: TradFi
- BitGo: Crypto Solutions for Banks
- Taurus: Security and Privacy
- State Street: State Street Announces Agreement with Taurus to Deliver Full Service Digital Platform for Institutional Investors
- State Street: State Street and Taurus: A partnership in action
- State Street: State Street Launches Digital Asset Platform to Power Tokenized Finance
- Ripple Developer Documentation: Ripple Custody security model
- Ripple: Ripple Accelerates Institutional Custody Adoption with Security, Compliance, and Staking Capabilities
- Ripple: DZ BANK selects Metaco Harmonize
- Ripple: VP Bank consolidates digital asset custody and tokenization operations
- Fireblocks: Fireblocks Expands Support for Banking and Financial Institutions
- BitGo: Self-Custody Asset Infrastructure
- Fireblocks: Jurisdiction, Data Sovereignty, and Operational Control: A Fireblocks Reference for European Financial Institutions
- Taurus: What Is On-premises custody?
- Ripple Developer Documentation: Ripple Custody installation environment setup
- National Institute of Standards and Technology: Cryptographic Module Validation Program
- National Institute of Standards and Technology: FIPS 140-3 Transition Effort
- European Banking Authority: Digital operational resilience Regulation (DORA), interactive Single Rulebook
- Ripple Developer Documentation: Ripple Custody change history
- Financial Market Authority Austria: DORA – Managing of ICT third-party risk
- Dillon Eustace: The European Commission clarifies the definition of ICT services under DORA
- CMS: EU’s final ITS version extends the scope of ICT services subject to DORA
- Fireblocks: Securing Digital Assets in an Evolving Threat Landscape: The Fireblocks Defense-in-Depth Approach to Security
- Taurus Developer Hub: Taurus PROTECT documentation introduction
- State Street: Digital Asset Solutions
- European Banking Authority: Request for Clarification on Article 28(3) of Regulation (EU) 2022/2554
- Guardian: Crypto Custody for Banks: Controls Examiners Expect
- Guardian: Bitcoin Custody: How It Works and How Institutions Hold BTC
- Guardian: Best Crypto Custodians in 2026: Custody Services Compared
- Guardian: Crypto Custody: How Institutional Custody Works, Its Risks and How to Choose a Custodian
- Guardian: Banks Offering Crypto Trading: The Security Architecture
- Guardian: Neobank Crypto Integration: A Security Plan for Fintechs
- Guardian: Digital Asset Assurance Pilot
- Fireblocks: How Banking Circle Launched their MiCA Regulated EURI Stablecoin with Fireblocks
- Alberta Securities Commission: Continuous Information Relating to Assets Held
- Crypto Reporter: GK8 Reaffirms Its Commitment to Trust, a Secure Operating Environment, and Data Privacy with Renewed SOC 2 Type II Certificate
- U.S. Securities and Exchange Commission: Galaxy Digital Inc. Form S-4/A
- Ripple: Digital Asset Infrastructure Solution Security
- BitGo: BitGo Trust Center
- BitGo: BitGo's Commitment to Security and Trust: The SOC 2 Advantage
- BitGo: BitGo Secures CCSS Level 3 Certification, the Highest Standard in Crypto Security