| AnchorWatch Scored8.2/10 Insurance-backed collaborative custody | Trident Vault is a miniscript "multisig of multisigs" — your own keyset (a single hardware key, or a client-side 2-of-3) paired with AnchorWatch's independent institutional keyset, and both sides must complete their own signatures before coins move. AnchorWatch is a required co-signer while the vault is insured. | A lost key is recoverable via AnchorWatch co-signing, with Lloyd's-syndicated insurance covering named theft and key-loss scenarios on top. | Best for users who want collaborative custody plus explicit policy language, not just wallet architecture. | Insurance should widen your questions, not end them. Coverage scope and claims assumptions still matter. |
| Unchained Scored8.1/10 Collaborative multisig | Standard client-controlled vault is 2-of-3: you hold 2 keys and Unchained holds 1. Unchained cannot move the bitcoin without one of your keys. | If Unchained's site is unavailable, the wallet config file plus your two keys recovers the vault in Caravan or Sparrow. If you still hold one key, Unchained can co-sign a recovery. | Best for users who want guided self-custody rather than a fully outsourced custody relationship. | Read the exact service boundary and recovery assumptions carefully before treating it as “set and forget.” |
| Anchorage Digital Scored8.0/10 Federally chartered qualified custody | Single-custodian model under a federal national trust bank charter rather than a state trust. | Recovery and continuity are institutional process questions under federal supervision. | Best as a benchmark for federally regulated qualified custody, not as a Bitcoin-native self-custody alternative. | A federal charter does not by itself resolve concentration or product-fit questions for individual holders. |
| BitGo Scored8.0/10 Qualified institutional custody | Pure institutional-custody benchmark with less user-participation than collaborative models. | Recovery and continuity are likely service-process questions, not self-custody questions. | Best used as an institutional reference point, not as a default recommendation for every Pledge reader. | A large brand and broad platform are not the same thing as segment fit or legal clarity for your specific use case. |
| Fidelity Digital Assets Scored7.8/10 Institutional custody | Institutional-custody benchmark with traditional-finance trust signals rather than user participation. | Recovery and continuity are likely enterprise-service questions, not wallet-design questions. | Best for institutional benchmarking, not as a blanket default for self-custody-minded users. | Brand trust and category fit are different things. Users should not confuse the two. |
| Coinbase Custody Scored7.8/10 Qualified custody (NY trust) | Single-custodian qualified custody — Coinbase Custody Trust Company holds and signs. | Recovery and continuity are enterprise-process questions, not user-held key design. | Best for institutional and ETF-adjacent contexts, less obviously the right answer for individual holders who want structural redundancy. | Coinbase Custody Trust and the Coinbase consumer platform are separate legal entities — do not conflate the protections. |
| Onramp Scored7.7/10 Multi-institution custody (2-of-3) | Individual and IRA vaults are 2-of-3 across Onramp, BitGo Trust, and CoinCover. CoinCover holds a backup key for recovery if an institution fails, is compromised, or a client loses access. The client holds no keys. Business accounts use Onramp, Tetra Trust, and CoinCover. | If Onramp is unavailable, the other two institutions still have the 2-of-3 quorum and coordinate recovery into a replacement vault. Inheritance planning is included. | Best for users who want the structural benefits of multisig without operating the keys themselves. | Independence of the three signers is the load-bearing claim — confirm it before treating the model as airtight. |
| NYDIG Scored7.6/10 Qualified custody (NY trust) | Single-custodian NY-trust custody, Bitcoin-only by design. | Recovery and continuity are institutional processes, not user-held key designs. | Best for Bitcoin-focused institutional and wealth-advisory contexts, less obviously a direct answer for individual self-custody-minded holders. | Bitcoin-only framing is meaningful but does not substitute for a clear current read on disclosures and concentration risk. |
| Casa Scored7.5/10 Self-custody coordination | Standard is a 2-of-3 vault. You hold your own keys, and Casa holds one Casa Key that co-signs for recovery. Higher plans add a 5-key or 6-key vault. | Recovery and inheritance are central. If Casa shuts down, you recover with your own keys in Sparrow or Electrum. | Best for users who want durable self-custody with guidance, not passive institutional storage. | Users still inherit personal operational responsibility, so complexity tolerance matters a lot. |
| Gemini Custody Scored7.3/10 Qualified custody (NY trust) | Single-custodian NY-trust custody operated by an exchange-linked entity. | Recovery is enterprise-process, not user-held key design. | Best for institutional and benchmarking contexts; readers should keep custody and exchange products clearly separated. | Compliance reputation is real, but does not erase concentration risk or the importance of separating the custody product from adjacent Gemini services. |
| Swan Scored6.8/10 Collaborative multisig (Swan Vault, 2-of-3) + segregated trust custody (Swan Safe) | Swan Vault is 2-of-3: you hold 2 keys in cold storage and manage the third, a Cloud Key, through Swan. Swan has access to only that one key. Swan Safe is separate: a regulated custodian holds the keys. | If Swan is unavailable, download the Swan Vault Recovery Kit and import it into Specter Desktop or Bitcoin Core, then spend with your two Jade devices. | Best for users who want Bitcoin-native relationship management more than pure software autonomy. | Do not flatten “concierge” into “safer” until the control model and contingency plan are directly reviewed. |