The stack
01 · Control plane
Exo itself — the portfolio control plane for App registration, environments, releases, and evidence — with work run through Hermes agents and FluidVoice built in for voice input.
- Dimension
- 01 · Control plane
- Platform
- Exo + Hermes + FluidVoice
- Hermes
- Open-source agent runtime (Nous Research) that operators and Exo agents work through. Ecosystem standard · authority: Exo
- FluidVoice
- Open-source, on-device dictation used to drive work by voice. Ecosystem standard · authority: Exo
- Status
- Exo is live on Convex (staging and production deployments); Payload removed (October 2026). Hermes and FluidVoice integration contract: TBD.
What it is
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 Hermes agents, with FluidVoice built in for voice."
Platform
- Exo is first-party. Its state lives in Convex, its web app runs on Railway, and its source lives in Entire.
- Hermes (agents) is the open-source agent runtime from Nous Research that operators and Exo agents work through (integration catalog: ecosystem standard, authority Exo).
- FluidVoice (voice input, built in) is open-source, on-device dictation used to drive work by voice (integration catalog: ecosystem standard, authority Exo).
| Environment | Convex deployment | Web |
|---|---|---|
| Staging | frugal-eel-930 | https://staging.exo.now |
| Production | befitting-bullfrog-619 | https://exo.now |
Source: convex/README.md and
src/platform/integrations/catalog.ts.
Boundary and replaceability
- 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. Hermes and FluidVoice are how operators drive work; the accountable record stays in Exo. How Hermes sessions and FluidVoice dictation 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 notes
- Convex and Railway plan costs for the control plane: 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.
Status
- 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.
- Hermes and FluidVoice: named in the catalog and on exo.now. No ADR or roadmap item records their rollout: TBD.