> For the complete documentation index, see [llms.txt](https://docs.brava.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brava.finance/docs/platform-overview.md). # Platform Overview Connect your AI to DeFi while keeping custody and approval with your team. ## Platform Overview Brava connects your AI to DeFi. Your agent researches opportunities, assesses risk, and prepares transactions across DeFi and tokenised capital markets. Your mandate sets the limits. You and your custodian decide what moves. The agent proposes. The mandate defines what is possible. You decide what moves. ### The problem this solves Institutional capital has been largely absent from on-chain yield, and not for lack of return. The obstacles are operational. **Custody.** Most ways of accessing DeFi require handing an application the ability to move your funds. For a regulated treasury that is not a trade-off to be negotiated; it is a full stop. **Diligence.** A stablecoin pool's advertised rate says almost nothing about whether the position is sound. What backs it, where the yield actually comes from, how deep the liquidity is if you need to leave — these are the questions, and answering them means reading contracts and indexers across a dozen protocols. **Execution.** Deploying across several venues and chains is many transactions, each with its own approval, gas, bridging and failure mode. Doing that by hand at size is operationally unattractive. Brava addresses all three: your custodian keeps the keys, the diligence data is gathered for you, and a deployment across venues and chains is planned as one instruction. ### Custody Brava holds no keys. Your capital sits in a **workspace** — a Safe smart account connected to your custodian, Utila or Fireblocks. Brava plans transactions and prepares them for signature. Your custodian signs them. Two things follow from this, and they are the reason the architecture is worth understanding: **Brava cannot move your capital unilaterally.** Not through a bug, not through a compromised account, not through an agent behaving unexpectedly. Every movement requires a signature Brava cannot produce. **A plan is not an action.** Everything Brava or an agent produces is a proposal until a person approves it and a custodian signs it. ### How capital moves Three tiers, and capital crosses between them deliberately: ``` Custody wallet ──deposit──▶ Workspace ──allocate──▶ Strategy ◀─withdraw── (cash holdings) ◀──redeem─── (holdings) ``` **Your custody wallet** is your custodian's vault. It funds the workspace and receives withdrawals. **Your workspace** holds capital that is not yet deployed, as *cash holdings*. This is the account that transacts. **A strategy** is a named set of holdings that capital is deployed into. The two hops are different in kind. Deposits and withdrawals cross the boundary between your custodian and Brava. Allocations and redemptions move capital that is already inside the workspace, and never touch the custody boundary at all. This is worth internalising early, because it explains where capital is when it appears to be nowhere. Funds that have left your custody wallet but are not in a strategy have not gone missing — they are cash holdings, waiting. ### What you can do **Research.** Markets lists every pool Brava can deploy into, with the data to judge it: what backs the position, where the yield originates, and how you would exit. Trace the collateral, understand the yield, assess the exit. **Build.** A strategy holds one or more pools in proportions you set. It can span chains; Brava plans the bridging as part of one instruction rather than leaving you to sequence it. **Move.** Allocate into a strategy, redeem out of it, rebalance between its holdings, or transfer between strategies. Each states what moves, where it goes and what it costs before you commit. **Watch.** Every transaction reports its steps as they execute — deploying on a chain, bridging between chains, syncing afterwards — and leaves the transaction hashes behind for your records. **Ask.** Ask Brava answers questions about your positions and activity from inside the app. **Delegate, within limits.** An agent can research and prepare transactions on your behalf. What it may propose is bounded by a mandate; whether anything happens is your decision. ### Who this is for Institutional allocators, treasury teams, and the wealth managers who run capital on their behalf. The assumption throughout is that the person instructing and the person signing may not be the same person, and that both answer to someone. Workspaces carry permissions accordingly: who may propose, who may approve, and who may sign are separate questions with separate answers. ### Where to start * **Getting started** — connect a custodian and open your first workspace. * **Workspaces** — how custody, permissions and capital fit together. * **Strategies** — building one, and moving capital through it. * **Transaction types** — what each instruction does, and what Brava records. * **Glossary** — the words, and what they mean here. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.brava.finance/docs/platform-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.