System architecture

Structure for agents that have to operate in the real world.

Agentstration separates governance, delegated work, orchestration and execution—then reconnects them through explicit, provider-neutral contracts.

01 / Four boundaries, one platform

Four boundaries, one platform

Management plane

Govern the desired system

Own declarative agents, model profiles, tool catalogs, deployments and access boundaries.

Work plane

Track delegated work

Own durable Work Items, interactions, tasks, results and artifacts exposed through the Workplace.

Flow plane

Orchestrate visibly

Turn editable graph drafts into immutable published versions and observable Flow Runs.

Runtime plane

Execute through an agent runtime

Materialize and run agents through today’s Microsoft Agent Framework adapter, behind stable contracts.

02 / The path of work

The path of work

A request moves down through increasingly focused platform concepts. Results and operational signals return through the same clear boundaries.

03 / Architectural boundaries

Architectural boundaries

Declarative by design

Management owns durable definitions; Runtime materializes them only when work is executed.

Explicit boundaries

Planes exchange stable contracts so each can evolve without depending on another’s internals.

Local-first, cloud when useful

Run the control plane close to your data and add remote services selectively.

Replaceable components

Runtimes, model providers and AEP extensions can evolve without redesigning orchestration.

Build the system around your agents

From promising prototype to dependable platform.

Explore the architecture today. Connect to the project as public resources become available.