How we work
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 as the same open artefact when your diligence requires it. Additional accounts and workflows build on that deployment.
Four steps
From a defined use case to an authorised go-live.
- Define the use caseWhich product or workflow, for whom, on which custodian. No commitment; the output is a shared page describing your process and where the account, the mandate and the record would sit.
- AssessmentA deployment decision document: first product or workflow, intended users, success criteria, relevant systems, control responsibilities, integration gaps, proposed scope, the resources you provide, and the basis for the commercial proposal. Includes your policy encoded as a mandate object.
- Proof sprintAgainst agreed scenarios in a defined environment: a mandate, a refused proposal, a permitted one, an approval, a record. Environment, data, assets and custody prerequisites are stated in scope. A passed sprint informs the deployment decision; it is not automatic authorisation.
- Deployment and expansionAccount and mandate configuration, custody and approval integration, reporting connections, evaluation against agreed controls, operational responsibilities, authorised go-live. Additional accounts and supported workflows reuse the platform and established integrations; new venues, assets and requirements are scoped with your team.
Three ways to run Brava
Connect, deploy, own: what changes at each step.
Enter where it fits. The account, the mandate, the intelligence and the record are the same at every step; what changes is who runs the harness and how deeply Brava is integrated with your systems.
| Connect | Deploy | Own | |
|---|---|---|---|
| Accounts, mandate and control, intelligence, record | The same at every step. The guarantees never depend on how far you go. | ||
| Connectors | The same at every step. They attach to the account, not to the harness. | ||
| Harness | Your AI tool's own scheduler and memory | Brava's operations runner, hosted or in your cloud | Your platform |
| Skills | Brava packs, as shipped | Packs plus skills written for your firm, with evaluations | Licensed, versioned, carried with you |
| Memory | In your AI tool | Owned by your institution, compounding | Yours, as files |
| Integration | None | Your custody, approval and reporting systems, built by Brava | Yours |
| Services | None | Assessment, proof sprint, deployment, expansion | Advisory only |
If two of the Deploy items describe a limit you have hit on Connect, you are a Deploy client. If your AI platform already runs governed agents, you may start at Own.
Commercially: research is free to start. Deploy and Own are a platform licence per institution plus implementation, priced against the accounts and capital operated through Brava with minimums per account. Terms are set out in the assessment.
FAQs
Can an agent ever move capital on its own?
No. Agents produce proposals. A proposal executes only after the mandate check passes, required pre-trade checks pass, and an authorised person approves. Signing follows the permissions your custodian configured. Brava holds no keys. Controls in detail.
Who can change a mandate, upgrade an account or exercise administrative powers?
Mandate changes follow the same approval tiers as transactions and are recorded with version history. Account upgrades and administrative powers are set out under authority and control.
What data do the models see, and where do they run?
Per task: the account's mandate and version, positions, custodian envelope, eligible markets and relevant skills. Models run on your keys; supported deployment modes, including in your cloud, are listed with their scope under data and AI governance.
What happens if Brava, a model, a data source or an integration is unavailable?
Assets stay under your custodian's key in Safe smart accounts you can operate directly without Brava. Brava's research, automation and reporting services would need replacement or manual operation, and source code escrow and documented handover are part of every deployment. Behaviour for each failure, and handling of reconciliation breaks, is described under continuity.
Which custodians, networks, venues and assets are supported today?
Published with onboarding dependencies per item in the supported deployment scope, and confirmed with your team at assessment.
Is there an audit trail if we only connect our own AI?
Yes. The account is the only way to act, so every proposal, refusal, approval and execution is recorded whichever tool proposed it, from the first prompt. Deploy adds evaluations, client-owned memory and system integration; it does not add the record, which is always there.
What do we own at the end?
Brava licenses its platform and retains its proprietary and reusable technology. Rights to your configurations, skills and deliverables follow the agreed contract. Your mandates, your accounts and your record are yours to export.
Discuss the first use case for your institution.
A short call to define the use case. No commitment; the output is a shared page describing your process and where the account, the mandate and the record would sit.