Ripple Expands Custody Offering With Securosys HSMs and Figment Staking Integration

SAN FRANCISCO — Feb. 9, 2026 — Ripple announced a set of collaborations aimed at making its Ripple Custody offering more “institution-ready,” adding new security hardware options and staking functionality designed for banks, custodians, and other regulated enterprises.

The company positioned the update as part of a broader custody push that follows its previously announced Chainalysis integration and its acquisition of Palisade, saying the combined moves are meant to simplify procurement, reduce complexity, and shorten the time it takes for institutions to launch custody services at scale.

What’s changing: hardware security modules, faster procurement, more flexibility

Ripple said it now offers CyberVault HSM and CloudHSM capabilities from Securosys, a provider of high-security hardware security modules.

The key pitch is practical: institutions can deploy HSM-based custody without the traditional cost, complexity, or procurement delays, with options available on-premises and in the cloud depending on internal requirements.

Ripple also emphasized that the setup gives banks and custodians direct control over cryptographic keys, while remaining scalable and cost-effective. It added that Ripple Custody supports a wide range of HSM providers, positioning this as a way to support compliance needs across different regulatory jurisdictions.

Securosys CEO Robert Rogenmoser said the integration is designed to give institutions an out-of-the-box enterprise-grade custody configuration that can be deployed quickly while retaining full control over cryptographic keys.

Staking inside custody: Ripple partners with Figment

To expand product offerings beyond storage and transfers, Ripple said it partnered with Figment to bring staking capabilities to Ripple Custody clients.

Through the collaboration, Ripple and Figment aim to help banks and custodians offer staking on leading proof-of-stake networks, including Ethereum and Solana, without requiring those institutions to build and operate their own validator infrastructure or compromise operational controls.

Ripple’s SVP of Product, Aaron Slettehaugh, framed the change as reducing friction from managing complex institutional tech stacks, helping customers go live faster and scale with more confidence.

Why this matters now

This move is part of a larger pattern: institutional crypto adoption is shifting from “can we custody an asset?” to “can we offer a full suite of services safely?” That means security architecture, compliance tooling, and yield-bearing features like staking increasingly need to ship as one coherent system, not a patchwork of vendors.

Industry takeaway: why this is useful for crypto (especially institutional custody and staking)

This announcement matters because it targets the real bottleneck in institutional crypto: operational readiness.

• HSM choice and deployment flexibility (cloud or on-prem) makes custody easier to fit into existing bank-grade security policies and procurement realities.
• Key control is the institutional deal-breaker. The focus on customer control over cryptographic keys addresses the governance question regulators and risk teams care about first.
• Staking becomes a “product feature,” not a research project. If custody platforms can offer staking via established infrastructure partners, more institutions can provide yield products without building validator operations from scratch.

Bottom line: Ripple is trying to make custody feel less like a bespoke crypto build and more like a standardized financial infrastructure rollout—secure keys, embedded compliance, and staking as a turnkey extension.

Source: Ripple’s official press release