Skip to content
Architecture

Three planes. Twenty-six layers. Nine already load-bearing.

Lower layers provide identity and isolation. Middle layers provide policy and orchestration. Higher layers provide the capabilities agents actually use. Start with the governance core and grow into the rest as your agent estate matures.

The planes

Three planes, one governance core.

Control Plane — decides and governs

A single north-south public contract: identity, tenancy, policy, roles, the skills catalog, workflow lifecycle, observability reads and the one governed orchestration entry point. It is the Policy Decision Point and the audit authority.

  • 01 — Identity & Delegation
  • 02 — Tenancy & Entitlement
  • 03 — Policy & Governance
  • 04 — Skills Governance
  • 05 — Workflow Control Plane
  • 09 — Platform Governance API
Precedent

The pattern that repeats

Every platform era externalized the concern its predecessor left to application code.

EraExternalized concernPlatform that named it
Cloud Identity, cost, config governance AWS IAM · HashiCorp
Microservices Service identity, policy, tracing Istio · OPA · SPIFFE
Data Governed access to data Snowflake · Unity Catalog
Durable workflows Reliable state, retries, replay Temporal
Agents Autonomy under delegated authority AgentOS
The substrate

Every heavy dependency sits behind a contract

The stack is pluggable, not welded.

Keycloak

Identity.

Temporal

Durable execution.

SpiceDB

ReBAC.

OPA

Policy-as-code.

Vault

Secrets.

pgvector

Per-tenant vectors.

LangGraph

Orchestration graph.

A2A

Agent transport.

Kubernetes

EKS · AKS · GKE.