> 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/technical/fees.md).

# Platform Fees

Brava operates on a simple and transparent fee structure—a 0.50% annual fee that accrues linearly on your total deposited funds across all strategies. This fee is automatically calculated and accrued in real-time, eliminating complex calculations or opaque charges. **There are no performance fees, deposit fees, or withdrawal fees associated with the Brava platform.**

#### Fee Calculation

The 0.50% annual fee accrues linearly, meaning:

* Daily accrual rate: approximately 0.00137% (0.50% ÷ 365)
* Monthly accrual rate: approximately 0.0417% (0.50% ÷ 12)

For example, with a $10,000 deposit:

* Annual fee: $50 ($10,000 × 0.50%)
* Monthly fee: \~$4.17
* Daily fee: \~$0.137

#### Network Fees

> **Note:** Gas fees for blockchain transactions (deposits, withdrawals, rebalancing) are separate from Brava's management fee and depend on Ethereum network conditions at the time of transaction.

Brava incorporates several gas optimization techniques to minimize transaction costs, including:

* Batch processing for rebalancing operations
* Strategic timing of non-urgent transactions
* Efficient smart contract design


---

# 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/technical/fees.md?ask=<question>&goal=<user_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.
