Platform architecture

One control plane. Many providers.

Separate intent, capability arbitration, account orchestration and execution so the same desired state can move across vendors and engines.

BlueprintsProvider AdaptersPolicy-as-CodeAuditDrift Reconciliation
BP

Blueprint compiler

Typed, versioned desired state from natural-language or structured intent.

AR

Arbitration engine

Score offerings for abstract capabilities using policy, cost, latency and quota.

AC

Account orchestration

Detect, link or create supported vendor account resources.

EX

Execution adapters

Materialize plans through OpenTofu, Pulumi, Crossplane or APIs.

VR

Verification agents

Validate actual resources against the blueprint after execution.

DR

Continuous reconciliation

Observe desired versus actual state and surface or remediate drift.

Capability registry

Speak in capabilities, not vendor syntax.

Provider adapters implement normalized capability contracts.

CapabilityNormalized intentImplementationsArbitration
database/postgresversion, storage, HA, regionManaged / VM / Kubernetesprice, SLA, residency, quota
storage/objectcapacity, durability, regionObject storageprice, egress, policy
dns/zonezone, records, routingDNS providerslatency, features, cost
cdnorigins, cache, TLSCDN providersperformance, geography