Skip to Content

isA Maestro

The workflow orchestration runtime for the isA platform — a single orchestration spine across n8n, agent A2A, MCP tools, Maestro-native DAGs, and edition-specific UiPath integrations.

Overview

Apps, agents, developers, and end users all need to run workflows that cross APIs, tools, human actions, and agent execution. Built ad-hoc inside each app, this logic gets duplicated and ungoverned. isA Maestro centralizes it: one credential boundary, one webhook hub, one event stream, one observability surface, routed across whichever engine fits the workflow.

Status: v0.3 — multi-engine orchestration (UiPath + n8n + agent A2A) is code-complete. The GCP SaaS Maestro pod, n8n runtime, and MCP connectivity are deployed and live-verified. An operator console (governance UI), eval framework, and chargeback tooling are planned but not yet built.

Edition positioning

isA Maestro specializes its default routing per edition:

EditionDefault languageDefault runtime path
GCP SaaSDeveloper and end-user workflowsn8n + agent A2A + MCP tools + Maestro-native DAGs
Enterprise editionsGoverned business processesAPQC/process catalogs + UiPath where justified + n8n + agent A2A

Architecture

Apps · agents  →  isA Maestro (FastAPI)  →  engine adapters  →  n8n / agent A2A / maestro DAG / UiPath
                                ↓
                           Postgres + Redis + OTel

Capability surface (v1)

CapabilityEndpoint prefixDefault path
Workflows/processes/v1/processes/*Engine-routed n8n, agent, Maestro-native, or edition-specific UiPath
Process catalog/v1/processes/*Tenant-safe registration, lifecycle, and deployment reconciliation
Maestro instances (DAG/BPMN)/v1/maestro/*Maestro-native DAG tier
Agents/v1/agents/*Agent platform over A2A
RPA queues/v1/queues/*Enterprise UiPath integration
Document intelligence/v1/ixp/*Platform-native pipeline or enterprise UiPath IXP
MCP servers/v1/mcp/*isA MCP aggregator
Action Center (HITL)/v1/actions/*Platform collab/HITL adapter or enterprise Action Center
Assets/v1/assets/*Runtime asset abstraction
Webhooks/v1/webhooks/*Engine callbacks and workflow events

All endpoints are also exposed as MCP tools for AI agents.

Tech stack

ToolPurpose
Python 3.13 + FastAPIService runtime
uipath-python SDKUiPath engine adapter (the only module allowed to import it)
n8nDefault developer/end-user workflow engine
PostgresProcess state, audit rows
RedisQueueing, caching
OpenTelemetryTracing across every engine call

Conventions

  • Every UiPath call is wrapped in an OpenTelemetry span and a Postgres audit row.
  • All endpoints require an IAM JWT bearer token; scopes are per-endpoint.
  • Tenant → UiPath folder mapping is a dedicated routing layer, kept separate from workflow logic.
  • isA_MCP — the MCP aggregator Maestro’s MCP server self-registers with.
  • isA_Agent_SDK — agent DAG primitives and A2A utilities. Maestro shares DAG semantics but does not import the agent runtime directly.
  • isA_Mate — the A2A target for the agent engine tier.
  • isA_Cloud — the Helm-based deployment substrate for isA editions, including Maestro.

Local development

# Install
uv pip install -e ".[dev]"        # or: pip install -e ".[dev]"
 
# Configure
cp .env.example .env
# Edit .env: set UiPath credentials, IAM JWT public key, Postgres/Redis URLs
 
# Run
uvicorn isa_maestro.main:app --reload --host 0.0.0.0 --port 6792
 
# Verify
curl http://localhost:6792/healthz
Home