Brahma

• Name: Brahma
• URL: https://brahma.fi/
• Category: Onchain orchestration / delegated execution / agent-workflow infrastructure
• Summary: Brahma is delegated-execution and workflow middleware for onchain finance. The wallet framing is secondary. What matters is the policy and routing layer it inserts between user custody and automated action across strategies, chains, and payment flows.
• What it does:
  • Provides a non-custodial multi-chain account model for users, teams, and institutions to secure, navigate, and automate onchain activity
  • Offers Console Kit, a developer platform for building automated and agentic onchain workflows without custom smart-contract development or direct custody of user funds
  • Supports delegated execution with policy controls so users keep custody while workflows or agents execute with defined restrictions
  • Exposes modular infrastructure for account management, policy enforcement, execution, and cross-chain DeFi integrations such as routing, MEV protection, and liquidity movement
  • Publishes example agent implementations and workflow scaffolds, including LLM-powered flows, automation agents, and MCP/server-style integrations in public repositories
• Key claims:
  • The homepage describes Brahma as “The Orchestration Layer for Internet Finance” and says it abstracts execution, security, and real-world rails so apps can coordinate onchain and offchain capital flows
  • Official product docs describe Brahma Console as a “universal multi-chain account” for securing, navigating, and automating onchain interactions for power users, teams, and institutions
  • The public Console Kit repository says developers can build automated and agentic workflows onchain while retaining user custody and relying on delegated execution, policy enforcement, and cross-chain primitives supplied by Brahma
  • The public scaffold-agent repository shows Brahma explicitly packaging example autonomous DeFi agents, including LLM-powered execution patterns, around Console Kit infrastructure
  • A notable cataloging nuance is that Brahma’s public materials appear to span multiple product eras: the marketing site emphasizes orchestration infrastructure, while parts of the docs still center on legacy account migration and Safe-based recovery flows
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were Brahma’s homepage, product/docs overview pages, Console Kit and scaffold-agent repositories, and the public GitHub organization; see ../whitepapers/brahma-primary-sources-2026-04-25.md.
• Sources:
  • https://brahma.fi/
  • https://docs.brahma.fi/brahma-overview/overview-of-brahma-products.md
  • https://docs.brahma.fi/brahma-agents-or-built-with-console-kit.md
  • https://docs.brahma.fi/developer/deployed-contracts-console.md?ask=What%20is%20Brahma%20Console%20and%20who%20is%20it%20for%3F
  • https://github.com/Brahma-fi
  • https://github.com/Brahma-fi/console-kit
  • https://github.com/Brahma-fi/scaffold-agent

Internal linkages

• Keep this one curated.
• Strongest comparisons: safe for the account substrate, coinbase-developer-platform for the broader wallet-and-payments control plane, and halliday for higher-level workflow packaging.

Control surface

• The leverage is in delegated-execution policy, routing defaults, workflow templates, cross-chain pathing, and whatever service logic decides how far an agent or automation layer can act before a human re-enters the loop.

• So do not overread the wallet surface. Brahma matters when custody remains nominally user-side but practical authority starts migrating into middleware.

• Last reviewed: 2026-05-27 UTC