Skip to main content
The hosted dashboard is the workspace view for audit history and team workflows. The CLI still creates audit data; the dashboard stores pushed summaries so a workspace can review trends, compare audits, manage Optimizations, and configure integrations over time.
Local CLI audits and --compare do not require an account. The hosted dashboard works with a free workspace: up to 2 members, the last 30 days of pushed audit history, and up to 100 stored audit snapshots per month. Pro and Enterprise workspaces get full history, unlimited members, Ask Xerg, hosted MCP, Slack, and policies.

​
Requirements

You need:
  • a signed-in Xerg account (a Free workspace is created automatically on first sign-in)
  • at least one pushed audit for real dashboard data
  • a workspace API key when pushing from the CLI or connecting hosted MCP
The primary new-workspace flow starts at xerg.ai/signup. After Clerk creates the first workspace, /dashboard/get-started asks for an audit source, creates or reveals the workspace key, verifies xerg login --replace, shows the exact push command, and waits for the first distinct audit. The waiting page is resumable after a refresh or later sign-in. If you are starting from the CLI, run a local audit first:
connect authenticates and offers to push the latest audit. You can also push explicitly with npx @xerg/cli@latest audit --push.

​
Dashboard sections

The dashboard is organized around the current workspace:
  • Overview: onboarding, workspace API key setup, latest spend, waste, and optimization summary
  • Audits: pushed audit runs and audit detail pages
  • Sources: source-level history, rename/archive controls, and source detail trends
  • Compare: side-by-side comparison for two pushed audits
  • Optimizations: modeled and provisional opportunities from the latest active audits
  • Policies (Alpha, Pro and Enterprise): recommendation-backed hosted policy drafts and Cedar previews
  • Settings: workspace profile, members and billing, API keys, and hosted MCP integration snippets (hosted MCP and Slack require Pro or Enterprise)
Free workspaces see every listed section; pages backed by paid capabilities show an in-place upgrade prompt instead of the feature. Legacy dashboard links such as /dashboard/actions, /dashboard/ask, and /dashboard/mcp redirect into the current Optimizations or Settings views.

​
Workspace API keys

Workspace API keys are used by:
  • xerg audit --push
  • xerg push
  • hosted MCP clients
  • non-interactive hosted automation
Create or rotate a key from onboarding or Settings. If an older active key cannot be recovered, rotate it once to reveal a fresh secret. The wizard uses npx @xerg/cli@latest login --replace, whose terminal prompt masks pasted characters and which verifies the new key before replacing any stored credential.
The onboarding wizard offers an expandable inline-key command for speed, with a warning that the key may be written to shell history or visible to other same-user processes. Rotate it in Workspace Settings if it is exposed.

​
Pushed audit data

Pushed audits use the versioned AuditPushPayload wire contract from @xerg/schemas. The payload includes totals, daily rollups, findings, recommendations, optional compare deltas, and source metadata. The payload excludes raw prompt and response content, local source file paths, local snapshot store paths, and internal local finding details.

​
Access and billing

Dashboard routes require a signed-in browser session. Free workspaces see the last 30 days of pushed audits; older snapshots are hidden, not deleted, and become visible again when the same workspace upgrades to Pro. Paid-only pages (Ask Xerg, hosted MCP, Slack, Policies) show an upgrade path instead of the feature. Members and billing are managed from Settings. Free workspaces support up to 2 members; Pro supports unlimited members billed per seat. Local CLI usage stays free and local-first regardless of workspace plan. At 90 through 99 stored snapshots, the dashboard shows remaining pushes and the UTC reset date. At 100, it shows a deliberate blocked state and Pro path instead of a generic API error. An already saved first-audit success view remains available.