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

# Technical Overview

#### System Architecture

Brava is a non-custodial DeFi automation platform built on Safe smart accounts. The architecture consists of two main layers:

#### Smart Contracts (On-Chain)

The on-chain layer provides secure, deterministic execution of DeFi strategies:

* **Safe Accounts:** User-controlled smart contract wallets maintaining full custody
* **Action Contracts:** Modular protocol adapters (Aave, Yearn, Morpho, etc.)
* **SequenceExecutor:** Orchestrates atomic multi-action transactions
* **AdminVault:** Governance and configuration registry with time-delayed proposals
* **EIP712 Module:** Cross-chain bundle execution with single-signature authorization
* **BravaGuard:** Transaction validation ensuring funds stay within approved protocols

#### Data Intelligence Layer (Off-Chain)

The off-chain layer handles computation, orchestration, and user experience:

* **Pool Discovery & Onboarding:** Automated protocol integration and vetting
* **Risk Intelligence:** Real-time monitoring and assessment of protocol health
* **APY Analytics:** Continuous yield calculation and performance tracking
* **Transaction Orchestration:** Cross-chain execution coordination and monitoring
* **Data Indexing:** On-chain event tracking and historical data aggregation
* **User Interface:** Portfolio management and strategy execution dashboard

***

#### Core Principles

<details>

<summary><strong>User Custody</strong></summary>

All funds remain in user-controlled Safe accounts at all times

</details>

<details>

<summary><strong>Modularity</strong></summary>

Protocol integrations as composable, upgradeable action contracts

</details>

<details>

<summary><strong>Security</strong></summary>

Multi-layer protection with BravaGuard, time-delays, and role-based access

</details>

<details>

<summary><strong>Cross-Chain</strong></summary>

Unified interface across Ethereum, Base, Arbitrum, and other EVM chains

</details>

<details>

<summary><strong>Deterministic Deployment</strong></summary>

CREATE2 for consistent addresses across networks

</details>


---

# 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/technical-architecture/technical-overview.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.