Aave makes the vault infrastructure behind its savings app available to businesses

A savings backend other businesses can use

Aave Labs introduced Stable Vaults on 9 July 2026, making the smart-contract system behind Aave App available to other businesses. A smart contract is software that executes transactions on a blockchain. Businesses can select accepted stablecoins, underlying earning strategies and customer rates, with returns above their commitments becoming operator revenue. The system supports Aave markets and other compatible ERC-4626 vault strategies. ERC-4626 is a common technical format for tokenized vaults. Aave also said its app’s production deployment would use Chainlink pricing and cross-chain infrastructure.

How different customers can receive different rates

The technical documentation explains that each user belongs to a SubVault, a grouping with its own per-second accrual rate. Operators can assign groups according to subscriptions, promotions or other product rules and can change assignments after deposit. Assets can be allocated across multiple approved strategies and networks. An accounting chain maintains the authoritative balance, while additional earning chains hold other strategies. In ordinary language, the screen can show one customer balance even though the system behind it has more than one place working to generate returns.

The same documentation distinguishes original principal from accrued interest. Converting interest into redeemable claims depends on a surplus check. It also describes asset-specific withdrawal fees and an aggregate redemption speed limit. These are configurable infrastructure capabilities, not a statement that every customer product uses identical settings.

What the app’s disclosures add

Aave App’s disclosures identify governance-approved settings, including allocations, supported assets, rate parameters and permissioned roles. Deposits follow signed instructions from the user’s embedded account; withdrawals go to pre-authorized destinations or a linked bank route. The disclosures say displayed rates are indicative, may fall to zero and are not guaranteed. Certain roles can restrict flows within their permissions, and lending-market liquidity can delay withdrawals. This later explanatory document describes the app’s configuration and risks; it should not be treated as a promise governing every other business that adopts Stable Vaults.

A worked example of the gap between two rates

Imagine a fictional merchant app that places $10,000 into an earning arrangement. For this example only, assume the underlying assets generate a constant 6% over one year while the app credits the merchant a constant 4%. Ignore compounding, fees and losses. The assets would generate $600, the merchant would receive $400, and $200 would remain before the operator’s other costs. These numbers are invented to illustrate the difference between an underlying return and the rate shown to a customer.

Now change the underlying result to 3% while leaving the customer figure at 4%. The assets would generate $300 against the assumed $400 credit, creating a $100 gap in this simplified example. Calling the customer rate predictable does not make that arithmetic disappear. An evaluation of such a product needs an explanation of how the gap is managed and which terms can change. The calculation is not a model of Aave’s reserves, contractual obligations or live rates.

The same backend can produce different products

Consider two hypothetical businesses using similar software. One builds a merchant settlement tool whose users need cash every Friday. Another builds a long-term savings interface for people adding a small amount each month. A feature that helps the second group may be irrelevant to the first. Their withdrawal expectations, accounting displays and support questions differ even before any rate is shown. Sharing a software foundation cannot settle those product choices.

For the merchant, the decisive test is whether an expected payout reaches the spending account when payroll is due. For the monthly saver, it may be whether the displayed growth separates new contributions from earnings. Those are specific jobs an interface must perform. A familiar infrastructure name is useful background, but the customer ultimately experiences the business’s settings, communication and payment journey. That is why the adoption of reusable vault contracts matters as a building block rather than a complete description of the finished service.