> ## Documentation Index
> Fetch the complete documentation index at: https://docs.defindex.io/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Short answers, with the page that has the long one.

### What is DeFindex?

Yield infrastructure for neobanks, fintechs and wallets. See [What is DeFindex](/intro/what-is-defindex).

### How does it work?

Your users deposit into a vault. The vault spreads that money across strategies, and each strategy connects to one external yield source. Your app reads back one balance and one APY. See [Vaults](/products/vaults).

### How does a partner make money?

By setting a fee on the yield the vault generates. See [Fees and revenue](/intro/fees).

### Is it secure?

The contracts are open source and audited, and the guarantees are enforced in the contract: a vault can only invest in the strategies fixed at its creation, funds cannot be sent to an outside address, and no role can freeze a withdrawal. See [Risks and Audits](/advanced-documentation/risks-and-audits).

### Is there a lock-up?

No. A user withdraws when they want to, with no minimum holding period, no cooldown and no notice. The only requirement is their own signature. See [Vaults](/products/vaults).

### Can a vault's strategies be changed after it is created?

No vault function adds or swaps one. Whether the list can change at all is decided when the vault is created: a vault deployed as permanent keeps that list forever, and a vault deployed as upgradable lets its Manager replace the vault's code, which is the only path that can change it. See [Vaults](/products/vaults).

### What do my users actually hold?

Shares in the vault, as a token called a dfToken, in their own address. See [Vault Operations](/integration-guide/vault-operations/index).

### Which chains does it run on?

Stellar today. The architecture does not depend on it, so ask us where the roadmap is if that matters to you.