> 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/platform/getting-started.md). # Getting Started Connect custody, fund a workspace, then build and allocate a strategy. ## Getting Started Four steps between here and capital at work. Each is deliberate, and none of them happen without your custodian. ### Before you begin You will need a custodian account — **Utila** or **Fireblocks** — with authority to approve transactions. If your organisation separates the people who instruct from the people who sign, have both available; the last step needs a signature. You will also need capital in the custodian's vault, in a supported stablecoin, on a supported chain. ### 1. Connect a custodian Brava holds no keys. Before anything else, connect the custodian that does. Each custodian has its own setup guide, and the mechanics differ. What is the same either way: you grant Brava the ability to *prepare* transactions from an account the custodian controls, and nothing more. Signing authority does not move. If this step feels like it is granting less access than you expected, it is working as intended. ### 2. Open a workspace A workspace is a Safe smart account, and it is where your capital lives. Name it for what it holds — *Operating capital*, *Reserves*, a client name — because permissions, strategies, history and capital all belong to the workspace rather than to you. Most organisations end up with more than one, and the names are how you tell them apart at a glance. The workspace is created on-chain. This takes a moment and requires a signature. ### 3. Deposit **Portfolio → Actions → Deposit** moves capital from your custody wallet into the workspace. Choose the token, choose the amount, review the fee, and approve. Your custodian signs. The capital arrives as **cash holdings**: in the workspace, deployed nowhere, earning nothing. This is the staging state, and it is where every allocation spends from. A deposit deploys nothing. That is a separate decision. ### 4. Build a strategy and allocate **Strategies → create**, then add holdings from **Markets**. Markets lists every pool Brava can deploy into. Read each one before adding it: what backs the position, where its yield comes from, and how you would exit. A rate on its own is not a reason. Set the proportions — a holding at 40% receives 40% of what you allocate. Adding holdings moves nothing and commits nothing. Then **Actions → Allocate**. Choose the token and amount, read what it will cost, and approve. Your custodian signs, and capital moves. ### What happens after you approve A progress panel opens and follows the transaction. If your strategy sits on one chain, it will usually settle in under a minute. If it spans chains, Brava bridges between them, and the bridge is normally the longest part — several minutes is routine. While it runs, the capital in flight shows on Portfolio as **capital in transit**. Each step names what it is doing and leaves its transaction hash behind. When it finishes, Portfolio and the strategy update. ### What to expect on day one **Balances are immediate.** Read live from the chain. **Earnings and charts are not.** They are built from indexed history that accumulates daily, so they will be empty at first and fill over the following days. This is expected, and it is not a sign that anything failed. ### Where to go from here * **Workspaces** — custody, permissions, and what belongs to whom. * **Strategies** — allocating, redeeming, rebalancing and transferring. * **Transaction types** — what each instruction does, and what Brava records. * **Workspace permissions** — inviting your team, and who can do what. * **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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.brava.finance/platform/getting-started.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.