A tokenised asset account for every client. Operated by AI. Held by your custodian.

Brava gives banks, wealth managers, funds and treasuries a separate on-chain account for each client or policy - run by the AI they already use, with the rules written into the account, the custodian holding the keys and the team signing every transaction.

Scalable

One account per client, fund or treasury; thousands per institution; one integration.

Segregated

Each account holds its own assets under your custodian's key. No pooling; its own record.

Operated by AI, approved by people

Agents research, prepare and report inside each mandate. Nothing moves without your team's signature.

Built on Safe. Smart contracts audited by Sigma Prime. Verify deployed permissions in the Brava Security Screener. Forward-deployed with your team.

Institutional infrastructure for agentic DeFi and tokenised capital markets.

How a Brava account worksOne custodian, many accounts
Your custodian
Holds the key

Approves each mandate and decides what enters the account.

Brava account - one per client
  • MandateRules in code
  • Your AIResearches and prepares
  • Your teamSigns. Nothing moves otherwise
On-chain markets
Approved venues only

Stablecoin yield, tokenised funds, on-chain credit, real-world assets.

Thousands of accounts. One integration. Every action recorded.

Built for

  • Banks
  • Wealth managers
  • Funds
  • Treasuries
  • Neo banks

Works with your AI

  • Claude
  • ChatGPT
  • Codex
  • Cursor
  • and other MCP clients

Custody

  • Fireblocks
  • Utila
  • MPC Vault
  • Ledger
  • and more

Markets

  • Aave
  • Morpho
  • Uniswap
  • Ondo
  • Securitize
  • and more

Networks

  • Ethereum
  • Base
  • Arbitrum

Data for your agents

  • Arkham
  • Alchemy
  • Messari
  • CoinMarketCap
  • The Graph
  • and more

Your first project

Keep the traditional.
Add the tokenised.

Banks and wealth managers

Client investment products

Offer clients mandate-controlled tokenised asset accounts for approved stablecoin yield, tokenised funds and on-chain credit. Prepare strategy changes across eligible accounts with institution-controlled approvals and account-level reporting.

How it works for banksHow it works for wealth managers

Fund managers and administrators

Tokenised-asset allocations

Add an eligible tokenised-asset sleeve to an investment strategy. Research, subscriptions, monitoring and redemptions run in a mandate-controlled workflow, with records for your operations team and administrator. Investing in tokenised funds; issuing one is a separate scope.

Treasuries, including digital-native

Stablecoin treasury operations

Evaluate and allocate approved stablecoin balances against your liquidity policy. Agents prepare the weekly review and proposed changes; your team approves and signs, with a record of proposals, refusals and execution.

How it works for treasuries

Neo banks

Investment products for neo banks

Offer customers tokenised funds, securities and stablecoin yield in mandate-controlled accounts under your custodian, with per-customer reporting. Suitability and product governance remain with your institution; agents prepare and monitor within the rules you set.

How it works for banks

What each project depends on, and product status per capability, is set out in the supported deployment scope, confirmed with your team at assessment.

The product in operation

From research to a checked proposal, an authorised transaction and a record.

One account - illustrative

"Can this mandate hold a tokenised treasury fund, and which one?"

Research

Mandate permits tokenised treasuries; concentration limit 20%; exit route must be verified. Three candidates compared on backing, control and exit. One ruled out for thin secondary depth.

Refused

A first proposal to place part of the balance in a higher-yield vault is rejected before preparation: the venue is not in this account's mandate. Nothing prepared.

Plan

Move 15% of the account's stablecoin balance into the fund that passes. Post-trade concentration inside the limit.

Prepared

Subscription prepared and checked against the mandate. Nothing has moved.Venue allowlistedExit route verified for sizeConcentration within limitAwaiting approval

Approved

The manager approves. Signing happens through the permissions the custodian has set for the account.

Executed

Confirmed on chain, matched to the approved intent, in the account's statement the same day.

Illustrative walkthrough with demonstration data. Not customer deployment evidence.

412 accounts - illustrative

The model portfolio moves 5% from a stablecoin yield position into a tokenised treasury fund.

Eligibility

Of 412 client accounts following the model, 380 have the fund in their eligible universe. 32 do not; they are listed separately with the reason.

Proposals

Each eligible account gets its own proposal sized to its balance and checked against its own limits. 7 are held for a limit breach and routed as exceptions.

Approval

Advisers approve per account, or per client group where the institution's approval policy permits. Each approval is recorded individually.

Execution

Instructions execute under the custodian's permissions. Fills and positions reconcile to each account's statement the same day.

Record

Proposals, exceptions, approvals and executions per account, on one ledger, with the model and mandate versions that applied.

Illustrative. Grouped approval only where the institution's policy permits it.

How deployment works

Forward-deployed with your team.

We begin with a defined use case, map the controls and integrations it requires, and demonstrate the workflow against agreed criteria. Our team then configures and integrates the licensed platform alongside yours - hosted by Brava with regional residency by default, or installed in your cloud when your diligence requires it.

  1. Define the use caseWhich product or workflow, for whom, on which custodian.
  2. AssessmentA deployment decision document, with your policy encoded as a mandate.
  3. Proof sprintA mandate, a refused proposal, a permitted one, an approval, a record.
  4. Deployment and expansionConfiguration, integration, evaluation, go-live. Further accounts reuse it.

Three ways to run Brava

Connect. Deploy. Own.

AI orchestrators for financial institutions have arrived. Claude for Financial Advisors connects to custodians, portfolio systems and planning tools; a bank's own AI platform does the same. Brava is the system those orchestrators connect to for tokenised assets: the account, the mandate, the execution and the record. Enter where it fits; skills, mandates and the record travel with you.

Your AI, today

Connect your AI to DeFi

Connect the orchestrator you already use - Claude for Financial Advisors, Claude, ChatGPT, Cursor or any MCP client - to Brava. Research, assess risk and execute across DeFi and tokenised markets from that tool; your team signs. On the record from the first prompt.

Connect your AI

With our team

Deploy

Unattended schedules with approval gates, memory your institution owns, integration with your systems, a segregated environment your risk committee can sign off, evaluations against your mandates. On your keys, inside your AI governance; hosted or in your cloud.

How we work

On your stack

Own

Your own platform runs the agents and proposes through Brava; the account, the mandate and the record govern every action as before. Skills, mandates and memory move with you as files.

How your platform plugs in

Platform and controls

Why a smart contract, and why now.

Money is becoming programmable and the systems that will manage it are agents. A wallet with a policy engine was built for neither: it decides what a key may sign, at treasury level, and knows nothing about a client's mandate, an asset's backing or whether a position can be exited. Put an agent in front of it and you have a chatbot with a key.

A smart contract account puts the rules in the account, not the prompt: venues, assets, limits, exit conditions, who approves. One client's assets, no one else's. Proposals outside the mandate are refused before anything is prepared; everything accepted is recorded; nothing executes without a signature Brava cannot produce. Created a thousand times, one per mandate, each under your custodian's key.

Your custodian holds the keys and decides what enters each account. The account is where an agent is allowed to act; the mandate says how far. The full comparison.

Accounts

Every account is a Safe smart account. Contracts audited by Sigma Prime. Deployed permissions checkable by anyone in the Security Screener.

Keys and AI governance

The custodian holds every key. Claude, ChatGPT or any MCP client runs on your keys, inside your AI governance.

Mandate and control

On-chain restrictions, pre-trade checks, human approval, monitoring - each condition enforced where it belongs.

Intelligence

Brava's own block-by-block index across supported networks, joined with partner datasets - Glassnode, Arkham, Nansen, Alchemy, Messari, Cambrian, CoinMarketCap, The Graph - with provenance on every record.

Reporting and record

Daily valuation and reconciliation per account, and the record of every proposal, refusal, approval and execution. Your administrator's books stay the books.

Operations

Brava's operations runner or your own platform runs the schedules, agent roles and approvals. Skills are portable files your compliance function can read.

Your mandate, on-chain.

Discuss the first use case for your institution. Treasury and research teams can also connect the AI they already use and start today.

Already talking to us? Continue with your Brava contact, or meet the team.