Why DeFindex

You want a savings feature in your app. The choice is between integrating a yield protocol yourself and integrating DeFindex, which sits on top of those protocols.

​

What you get

• One integration, in one day. The API builds the transactions and your user signs them. No smart contract code on your side.
• A margin you control. You set a fee on the yield, and the spread between what the strategies earn and what you show is yours. See Fees and revenue.
• A fixed rate if you want one. Stable APY manages the fee inside bounds you set so the APY your users see tracks a target.
• A way out for everyone at once. If a protocol underneath turns risky, one call pulls every user’s funds back to the vault. Read on.

​

Against integrating directly

A lending market or an AMM is a protocol, not a product. It lends and it pays a rate. Everything a savings feature needs around that, you build. The fee row is the one partners are surprised by. A protocol pays its rate to whoever holds the position, and it has no notion of an integrator taking a cut. To earn on the yield you have to sit between your users and the protocol, keep the accounting, and charge on the gain. That is a vault, and building one is the work DeFindex already did and got audited. The row that matters most is the emergency exit. If the protocol underneath gets risky and each of your users holds their own position, there is nothing you can do for them. You can warn each one and hope each one signs a withdrawal, and most do not. In DeFindex it is one call, rescue, and it stays non custodial: the role pulls the funds out of the risky place and into the vault, where only the users can withdraw them.

​

When not to use DeFindex

If you only want to point each user at a single protocol, hold nothing in between, and earn nothing on it, you do not need a vault and you do not need us.