- Get Started

The big picture

OpenFlows Manager is the trusted product control plane. Coder provides workspace execution. Nexus is the controller inside one tenant's runtime, and workers execute ticket-scoped tasks in separate workspaces.

flowchart TB
    user["Signed-in user"] --> manager["OpenFlows Manager"]
    manager --> postgres[(PostgreSQL)]
    manager --> coder["Coder"]
    manager --> github["GitHub App"]
    coder --> nexus["Nexus controller"]
    coder --> workers["Worker workspaces"]
    nexus <--> redis[("Tenant Redis")]
    workers <--> redis
The product control plane provisions and supports a tenant runtime
View diagram source
flowchart TB
    user["Signed-in user"] --> manager["OpenFlows Manager"]
    manager --> postgres[(PostgreSQL)]
    manager --> coder["Coder"]
    manager --> github["GitHub App"]
    coder --> nexus["Nexus controller"]
    coder --> workers["Worker workspaces"]
    nexus <--> redis[("Tenant Redis")]
    workers <--> redis
ComponentBoundaryResponsibility
ManagerProduct control planeUsers, organizations, GitHub connections, runtime identity, broker, operations, hook ingress
CoderExecution control planeTemplates, builds, workspace agents, and workspace lifecycle
NexusTenant controllerIssue sync, scheduling, reconciliation, agent hooks, and A2A relay
Forge, Sentinel, Vessel, LoreTenant workersScoped work in separate disposable Coder workspaces
PostgreSQLManager system of recordOwnership, operation leases, workspace credentials, and broker leases
RedisTenant coordination storeTickets, worker slots, agent heartbeats, A2A evidence, and hook audit

From organization to agent work

  1. A user signs into Manager, creates an organization, and connects a GitHub App installation.
  2. Manager provisions a tenant and Nexus using durable operations and pinned Coder templates.
  3. Nexus registers a runtime session, synchronizes repository work using a brokered installation token, and asks Manager for workers.
  4. Manager authorizes and creates workers in Coder. The workers register their own scoped runtime sessions.
  5. Forge and Sentinel exchange verification requests through the Nexus A2A relay, with evidence stored in tenant Redis.

See Manager Runtime for the lifecycle and Credentials and Trust for the exact authority boundaries.