Google Cloud Previews Institutional Bitcoin Custody Service Ahead of Commercial Launch
Key Facts
Google Cloud has placed its Google Multi-Party Compute service in preview, offering a Bitcoin custody infrastructure that lets institutions sign transactions collaboratively without creating the full private key or storing it in one place. The move comes as institutions’ need to manage digital assets grows while distributing the authority to transfer them among multiple parties. Google describes the service as a key management system that uses a threshold signature scheme, allowing parties that do not trust one another to approve a transaction through collaboration. The service remains pre-launch, and Google’s terms say products and features available in this capacity may be provided “as is” and may have limited support. The company plans to make it commercially available in early 2027, according to CoinDesk.
The system distributes key shares mathematically across independent computing nodes, rather than keeping a complete private key in text form in one location. Google says the parties combine what they need from these shares to produce the transaction signature, without reconstituting or storing the full key. In examples of signature thresholds, approving a transaction may require two of three parties to participate, or five of seven. This arrangement allows signing authority to be distributed among participants instead of resting with one party, while contributors’ actions can be documented in an auditable log, according to an earlier company explanation. Google says its Confidential Space architecture uses remote attestation and AMD SEV technology to run workloads in a trusted execution environment and isolate the signing process.
Before signing begins, asset transfer requests pass through Confidential Space, where the policy engine checks the transaction. Institutions can set a cap on the amount transferred, restrict destination addresses and require approvals from multiple departments, according to CoinDesk. These controls give compliance and operations teams a role in setting transfer conditions before a request moves to collaborative signing. Google’s release notes show that Bitcoin policy engine rules were added on October 1, 2026. The additions included evaluating normalized amounts, detecting change outputs and classifying destination addresses, all of which factor into checking a transaction before it is executed.
Google told CoinDesk that design partners and major financial institutions are testing the technology, but did not name the participating institutions. Alphabet, Google’s parent company, has begun using the service to protect digital assets on the Ethereum and Solana networks, without specifying those assets. That puts the company’s own use alongside ongoing tests by partners and financial institutions, while the service remains in preview. Google has not announced pricing, leaving details of its commercial model unspecified ahead of the planned early 2027 launch. The next commercial phase is expected to show whether testing turns into institutional use and which organizations join the service.
The approach traces back to explanations Google Cloud published in 2023 on using multi-party computation to protect digital assets and reduce the risk of single points of compromise. In a later technical explanation, the company presented a reference architecture for signing blockchain transactions and said participating parties could operate outside Google Cloud, including on mobile devices, on-premises systems and other clouds. A Wells Fargo official said at the time that the bank was exploring solutions to enable secure access to a new generation of digital products, in collaboration with Google Cloud’s digital assets team. The current preview service adds key management and a Bitcoin-specific policy engine to this technical path. Its commercial launch in early 2027 will be the next milestone Google has set, with no price or names of the institutions testing it announced.