Turn idle balances into yield that keeps users engaged.

A product that drives retention, increases deposits, and gives users more value from their money.

~1 minute guaranteed settlement, insured; the same rails live in Picnic's Savings Account

The challenge

• Native savings flows take two signatures and a two-step deposit/withdraw window, slow enough that users think their money is gone.
• Building an insured position from scratch means picking a vault, integrating an insurer, and building the tracking layer yourself.
• Users aren't looking for the highest APY on the board; they're deciding whether to trust a savings product with money they were about to spend.

How Pods solves it

Savings Account is a configuration of the Investments API, not a separate system. The flavor you offer comes from which capability you compose it with: Pods Zero for cross-chain execution, OpenCover for an insured vault, or RWA-backed for tokenized treasuries. OpenCover vaults take a 1% cut of yield to insure the position, the tradeoff we think is worth making for a savings product, since users are looking for a safe place to park funds, not the highest APY on the board.

How it works

• Client signs the strategy call: Calls GET /strategies/<insuredStrategy> and signs the returned transaction from the source wallet, specifying amount and destination address.
• Pods routes the deposit: The Investments API routes the deposit into the OpenCover vault, handling any crosschain hop or asset swap, slippageless for like-for-like assets.
• The vault deploys into the protocol: The vault deploys into the underlying yield protocol (e.g. Sky, Spark), while OpenCover's insurance covers the position for a 1% cut of yield.
• Vault token lands at the destination: The client receives the OpenCover vault token in the destination wallet within ~1 minute, not back at the signing wallet.
• Track the position: Poll GET /strategies/:slug?wallet=<wallet> for currentPosition, profit, APY, and in-flight amounts.