Maestro architecture

How Maestro BPMN, Maestro Case, and Maestro Flow share one runtime, one deployment model, and one set of operating, monitoring, and optimization services.

One platform, three canvases

Maestro BPMN, Maestro Case, and Maestro Flow are three ways to build on the same orchestration platform, not three separate products. Whichever canvas you build with, your process shares the same deployment target, the same instance management surface, and the same monitoring and optimization tools.

The stack

レイヤー	機能	Where each canvas fits
Authoring	Where you build the process definition.	Maestro BPMN, Maestro Case, and Maestro Flow each provide a visual canvas in Studio Web. Maestro Flow also builds in VS Code.
Execution engine	Runs process instances and evaluates transition logic.	Maestro BPMN and Maestro Flow run on the same Maestro engine. Maestro Case runs on the Case Manager, which evaluates CMMN-style rules and falls back to agent reasoning when no rule matches.
デプロイ	Publishes a process definition so it can run.	All three publish to Orchestrator and are versioned the same way.
Runtime services	Cross-cutting services every running instance uses regardless of canvas.	Instance management, monitoring dashboards, alerts, and process optimization apply the same way to a BPMN process, a case, or a flow.
Business-user surface	Where non-technical users interact with running work.	BPMN and Flow surface through Action Center and Orchestrator; Case surfaces through the Case App.

使用するメリット

A process built with one canvas can call a process built with another: a case can invoke a BPMN process as a task, and a Flow can call a BPMN subprocess. Because they share the same runtime and deployment model, this composition doesn't require any translation layer.

関連ページ

• Choosing a Maestro canvas — which canvas fits your use case
• The Maestro Case lifecycle — a deeper look at how the Case Manager layer works
• Ways to build with Maestro — Studio Web, VS Code, and coding-agent support per canvas