01 · Control plane

Dimension

01 · Control plane

Platform

Exo + Hark + Hermes

Hark

The primary agent operators drive Exo work through: plans, changes, reviews, and approvals. The accountable record stays in Exo. Ecosystem standard · authority: Exo

Hermes

Open-source agent runtime (Nous Research); the open-source option for driving the control plane. Ecosystem standard · authority: Exo

Open-source option

Hermes

Status

Exo is live on Convex (staging and production deployments); Payload removed (October 2026). Hark is the primary way work is driven; Hermes is the open-source option. Integration contract for both: TBD.

What it isCopy Anchor Link

Exo is the application platform and control plane. It owns projects, organizations and access, environments, provider provisioning, deploy/release/rollback state, runtime-dependency metadata, policy and security controls, audit evidence, orchestration, health, and bounded usage and cost aggregates (ADR 0003).

Priorities, dependencies, release gates, and verified delivery share one accountable operating record. The public Exo shell explains the platform without exposing App data. The authenticated workspace is the internal operator surface.

On exo.now the dimension reads: "Plans, releases, and approvals for every app live in one record. Work runs through Hark, with Hermes as the open-source option. Recommended, not required."

The control plane is recommended but optional, like source control: an app may opt out of it (overview).

PlatformCopy Anchor Link

• Exo is first-party. Its state lives in Convex, its web app runs on Railway, and its source lives in Entire.
• Hark is the primary: the agent operators drive Exo work through, from plans and changes to reviews and approvals (integration catalog: ecosystem standard, authority Exo).
• Hermes (agents) is the open-source option: the open-source agent runtime from Nous Research (integration catalog: ecosystem standard, authority Exo). Every layer names an open-source option; this is the control plane's.
• FluidVoice is an optional, open-source, on-device dictation tool an operator can use to drive work by voice. It is not part of the control plane's primary stack (integration catalog: optional adapter).

Source: convex/README.md and src/platform/integrations/catalog.ts.

Boundary and replaceabilityCopy Anchor Link

• Authority rules. Every record has exactly one authority during every cutover phase. External providers stay authoritative for live deployment, billing, source, and health facts. Exo owns portfolio and release coordination, Entire owns source and execution provenance, Construct owns Pages, and independent Apps own their domain data (ADR 0003).
• Agents and voice are inputs, not authorities. Hark (or Hermes, the open-source option) is how operators drive work; the accountable record stays in Exo. How Hark and Hermes sessions connect to Exo records is not documented in the repository yet: TBD.
• No Payload. Payload and its PostgreSQL adapter are gone from the code. The old Postgres database is kept, untouched, only until its records are exported to their new owners.
• Exit. Every tenant can obtain independently usable content, media, design, source, and deployment artifacts (portability).

Cost notesCopy Anchor Link

• Convex and Railway plan costs for the control plane: TBD.
• Hark operating cost: TBD. Hermes and FluidVoice are open source (per the catalog); their operating cost: TBD.
• Exo stores bounded usage and cost aggregates for Apps, not their ledgers. See cost and unit economics.

StatusCopy Anchor Link

• Done: Convex backend for the platform, deployed to staging and production (roadmap: exo-convex-backend).
• In progress: roadmap as repo files with a public board (roadmap-as-repo).
• Data export: where each legacy Postgres record family goes is described in ADR 0003 and the legacy authority map.
• Hark and Hermes: named in the catalog and on exo.now (Hark as the primary, Hermes as the open-source option). No ADR or roadmap item records their rollout: TBD.