Manager overview

July 30, 2026 · View on GitHub

The Manager is the connected-Hub control plane in Transform Hub. It maintains the registry of connected Hubs, routes lifecycle and API operations to the owning Hub, aggregates status, and exposes live topic/service discovery across the connected Hub set. It does not replace the Hub runtime: Sequences still execute in Runners owned by individual Hubs.

Key responsibilities

  • Command routing — receives deployment, stop, inspect, and monitoring commands and forwards them to the correct Hub via the verser2 transport protocol.
  • Hub registry — maintains a registry of connected Hubs and their current connection, health, and inventory status.
  • Instance tracking — tracks all running Sequence Instances across the fleet, providing a global view.
  • Aggregation readiness — exposes deterministic v2 health details that show whether connected Hubs have reported sequence and instance inventory.
  • API surface — exposes the primary REST API that the CLI and API client target.

Manager vs Hub

AspectHubManager
RoleExecutes SequencesOrchestrates Hubs
ScopeSingle hostMulti-host fleet
APIDirect Hub controlUnified control plane
StateInstance state per hostConnected-Hub and instance registry view

For single-Hub development scenarios, you can interact with the Hub directly. When multiple Hubs are connected, the Manager provides the shared control-plane API and routes each operation to its owning Hub.

Control-plane and live topic paths

The Manager brokers control/API traffic and live topic/service-discovery streams through connected Hubs:

flowchart LR
    S1[Sequence] --> H1[owning Hub]
    H1 -->|control/API| C1[TLS/verser2]
    C1 -->|control/API| R[Manager API/router]
    R -->|control/API| C2[TLS/verser2]
    C2 --> H2[remote Hub]
    H2 --> S2[Sequence]
    H1 -->|live topic-stream| T1[TLS/verser2]
    T1 -->|live topic-stream| M[Manager topic multiplexer]
    M -->|live topic-stream| T2[TLS/verser2]
    T2 --> H2

The Manager API/router control path and the Manager topic multiplexer live-stream path are separate concerns. Topic streams are transient: they are not persisted and cannot be replayed. This model does not provide direct Sequence-to-Sequence networking; Sequences communicate through Hub topics and the Manager-brokered connection when the Hubs are connected. It also makes no HA, failover, or automatic Hub-redirection guarantee.

Health and readiness

The Manager exposes canonical health data at GET /api/v2/health. The health details include an aggregation readiness summary with connected Hub counts, active Hub counts, aggregate sequence and instance counts, and per-Hub inventory readiness. Operators can poll this signal to wait until Manager aggregation has consumed Hub inventory updates.

Legacy GET /api/v1/health remains available for backwards-compatible callers.

MultiManager

MultiManager coordinates multiple Manager processes and their API/control-plane lifecycle. Its presence does not by itself imply HA, failover, persistence, or automatic redirection; those behaviors require separate verified deployment behavior and configuration.

Next steps