Skip to content
Join the waitlist

The architecture behind governed AI software delivery.

Seven layers. Open contracts at every layer. Locked gates at every approval. Run it in our cloud, your VPC, or fully air-gapped.

Control plane Security architecture
Overview · 7 layers
  1. Surface: User experience layer · Console, dashboards, CLI, SDK, API gateway.
  2. Control: Mission control layer · Goals, missions, approvals, policy enforcement.
  3. Agents: Agent orchestration layer · Runtime, model routing, tool allow-lists, sandboxes.
  4. Context: Context & memory layer · Vector store, knowledge graph, decision memory. Integration layer · MCP, OpenAPI, gRPC adapters into the estate.
  5. Governance: Governance & audit layer · Policy engine, audit ledger, attestations, breakglass.
  6. Reporting: Reporting layer · KPI computation, rollups, exec reports. Seven layers from intent to evidence.
  • 7 layers · open at every contract
  • mcp · openapi · gRPC · graphql
  • cloud · vpc · air-gap · same control plane
  • cmk / hsm · zero retention by default
  • anthropic · openai · oss · provider-neutral
Uptime
99.98%
Latency
14.2ms
Nodes
128/128

Seven layers from intent to evidence.

Read it top to bottom: people work in layer 01, agents work in the middle, and every result ends up as evidence and a report.

Layers

  1. 01 · User experience layer

    Console, dashboards, CLI, SDK, API gateway.

  2. 02 · Mission control layer

    Goals, missions, approvals, policy enforcement.

    Control Plane

  3. 03 · Agent orchestration layer

    Runtime, model routing, tool allow-lists, sandboxes.

    Agent Runtime

  4. 04 · Context & memory layer

    Vector store, knowledge graph, decision memory.

    Memory & Context Graph

  5. 05 · Integration layer

    MCP, OpenAPI, gRPC adapters into the estate.

    Integrations & MCP

  6. 06 · Governance & audit layer

    Policy engine, audit ledger, attestations, breakglass.

    Security Architecture

  7. 07 · Reporting layer

    KPI computation, rollups, exec reports.

Where the boundary lives.

Switch the deployment mode. The control plane inside the boundary does not change.

  • Cloud, VPC, air-gap

    Same control plane across all three deployment modes.

  • Tenant isolation

    Cryptographic boundary with CMK / HSM key custody.

  • Regional residency

    Enforced at the platform layer per tenant policy.

  • Provider neutrality

    Anthropic, OpenAI, OSS — swap without code change.

Deployment boundary
Our cloud
Regional residency
Tenant · CMK / HSM
Control plane Same in every mode
Models
Nested boundaries: the environment, the region, the tenant, and the control plane inside them.

How a mission flows top to bottom.

Six hand-offs carry one mission from the console to the report. Press a step to replay it, or let it play.

  1. 01 // CONSOLE → MISSION CONTROL

    Operator opens mission; policy evaluated.

  2. 02 // CONTROL → ORCHESTRATION

    Mission scope handed to agent runtime.

  3. 03 // ORCHESTRATION → MEMORY

    Working set hydrated from the Grid.

  4. 04 // ORCHESTRATION → INTEGRATIONS

    Adapters invoked under allow-list + audit.

  5. 05 // OUTPUTS → GOVERNANCE

    Evidence captured, attested, ledger-pinned.

  6. 06 // LEDGER → REPORTING

    Metrics computed; rollups generated.

End-to-end request flow
6 / 6 Ledger → reporting · Metrics computed; rollups generated.

Start a Software Factory pilot.

Connect one repository, one ticketing tool, and one mission. See evidence in days, not quarters.

Book a pilot Join waitlist