BM Studio

Design it visually

BM Studio is the canvas. Build and orchestrate AI agents by dragging nodes into place; a Leader Agent decomposes each task and directs the specialist agents under it. Built so the person who understands the work can assemble it.

INTAKE
Task intake
LEADER
Leader Agent
AGENTS
Specialist Agents
OUTPUT
Delivery

Maya at work

The real Maya interface creating a Google search tool from a single request (2x speed).

Workflow Journey

From a prompt to a delivered result

A workflow in BM Studio follows one path, from a task arriving to a result being delivered, and at each stage a named agent is responsible for the work.

Intelligent Task Intake

A task arrives by prompt, upload or trigger, and the Leader Agent reads the objective and plans the work.

Drag-and-Drop Workflow

The plan becomes a visual workflow on the canvas, where you can see, change or approve each step before it runs.

Agent-Based Execution

Specialist agents each take a defined role and carry their part of the plan, in sequence or in parallel, reporting back.

Central Task Control

A central Leader Agent takes command, delegating tasks, managing progress, and resolving dependencies in real time.

Approval Checkpoints

Consequential steps pause for a person at thresholds you set. Approvals sit at every level, including inside nested workflows, so a refund above your limit waits.

Output Delivery

Results go to the system of record, the next workflow, or the person who asked, with every decision logged.

System Roles

Four roles in every workflow

One prompt becomes an executed task, coordinated across your systems, with a person in the loop where you place one.

Maya

Blue Mesh's workflow generator: describe the outcome in plain language and Maya assembles the agents, tools and logic on the canvas.

Leader Agent

Decomposes each task, directs the specialist agents under it, and carries the work end to end with no manual handoffs.

Specialist Agents

Each carries one defined role in the plan, running on its own or as part of a coordinated team.

BM Tools

Connect agents to your APIs, databases and external systems, 300+ pre-built plus your own, under credentials your team governs.

See it run one of your workflows

Bring a real workflow. In one session we will build an agent for it, live, and show you exactly where your team stays in control.

Workflow generator

Meet Maya

Maya is Blue Mesh's agentic workflow generator: describe the outcome you want in plain language, and Maya assembles the agents, tools, and logic to make it happen, right on the Studio canvas. BM Architect takes the same description further: through test, deployment, a demo page and test keys.

How It Works

Build multi-agent AI by talking, not coding

Maya turns a description into a working workflow, so the person who understands the work can build the first version and your engineers spend their time refining it rather than wiring it. Where BM Studio is the wrong tool is a single call into a model: if that is the whole requirement, a canvas for multi-agent workflows is more machinery than the job needs.

Describe

Tell Maya the goal in everyday language: “summarize support calls, flag the unhappy ones, and escalate anything about a refund to a person.”

Generate

Maya assembles the right agents, tools, and connections into a complete, working workflow.

Refine & deploy

Adjust anything on the canvas, set the approval checkpoints, then publish to production.

Workflow built
4 / 4
  • Transcribe and summarize each support call
  • Flag the unhappy customers
  • Escalate refund requests to a person
  • Log every decision on the audit trail
Studio Features

What is on the canvas: the agents you assemble, the generator that assembles them for you, and the tools and protocols they act through.

  • 01Predefined Agents
  • 02Leader Agent
  • 03Maya - Agentic workflow generator
  • 04Custom Agents
  • 05Voice Agents
  • 06Skills
  • 07300+ Systems and tools
  • 08Custom Tools
  • 09Model Context Protocol (MCP)
  • 10Data Ingestion
  • 11Nested workflows
Deployment Features

What you get once a workflow is published: connectivity to your systems, live logs and metrics on every run, guardrails and access controls, and the environment variables that keep credentials out of the workflow.

  • 01Connectivity
  • 02Metrics
  • 03Management
  • 04Statistics
  • 05Live logs
  • 06Security Guardrails
  • 07Templates
  • 08Knowledge Base Management
  • 09Environment Variables
Where to go next
  • BM Architect The other way onto this canvas: describe the workflow in plain language and have it designed, tested and deployed.
  • Telecom Three operational lanes running as workflows, network, assurance and customer ops, with an engineer gate before the network is touched.
  • IT operations and MSPs The same canvas pointed at IT requests, checks and routine changes, with its own workflows and audit trail per engagement.