Platform Dashboard

Dashboard landing (/dashboard)

Fleet view. Surfaces:

• Fleet status strip — Total exocorps; counts of running, draft, stopped, failed. Provider-credential coverage (configured / total).
• Exocorp cards — One card per exocorp: name, status badge, creation date, provider-readiness indicator. Click to open the detail page.
• Launch onboarding — Button to start the onboarding flow for a new exocorp (same flow as the browser signup).

Exocorp detail (/company/:id)

Per-exocorp management at the runtime level.

• Status hero — Current status (Draft, Starting, Provisioning, Running, Stopped, Failed) with a contextual message.
• Runtime readiness — Selected execution providers and the saved company configuration required for launch.
• Configuration status — Saved draft, previous runtime, active model price book.
• Release section — Current installed version, available version, status (up_to_date, install_required, update_available, blocked). Release channel selector: stable / beta / canary.
• Runtime status — Health and lifecycle state for the hosted runtime. Package-owned interfaces, when installed, are documented by their packages.

Lifecycle action surface

From the exocorp detail page (and via the admin API), you can run these actions: update, restart, reprovision, rollback, stop, destroy. Destructive actions require you to type the exocorp’s slug to confirm.

See Restart, stop, rollback for when to use each.

Admin pages (platform-owner only)

• Admin landing (/admin) — Fleet-wide metrics, recent audit events. The /admin/runtime-stats endpoint backs the runtime numbers.
• Admin companies (/admin/companies) — Sortable fleet table with owner, membership, latest job, channel, version, last update.
• Admin billing (/admin/billing) — Account states (current / grace / restricted / suspended), internal model-cost ledger, collections queue, provider event log. Per-account grace policy and ledger adjustments.

Health & monitoring

Runtime health surfaces in two states:

• Healthy — Runtime is running, control plane responding.
• Unreachable — Runtime metadata indicates running, but the control plane isn’t responding. Warning banner on the detail page.

Status (pending, provisioning, running, stopped, failed) is separate from health. During provisioning, the dashboard polls live and shows phase progress.

Domains

Hosted ingress metadata is keyed by the exocorp slug and issued with TLS. The runtime’s ingress binding reaches its authenticated control plane; installed packages may add separately routed app surfaces.

Audit trail

Every platform-level action attempt creates an audit event with actor, action, target (type and ID), outcome (succeeded / failed), human-readable summary, and structured details JSON. Admin landing shows the latest; the full set is queryable via the registry.