Dashboard

The Fuze dashboard at app.fuze-ai.tech gives you live run monitoring, tool analytics, workflow patterns, and compliance reporting. Set FUZE_API_KEY and the SDK streams telemetry automatically.

Views

Live Runs

Real-time view of all active and recent agent runs. Shows:

  • Activity-based status, runs are shown as active (last event < 5 min), idle (< 1 hr), or stale (> 1 hr) without requiring an explicit run.end() call
  • Cost accumulation per run with step count
  • Filter by status, search by agent ID
  • One-click kill switch for any active run

This model matches conversational agents where "completion" is not a well-defined event, a ChatGPT-style session stays active for as long as the user keeps messaging.

Trace Replay

Step-by-step replay of any run:

  • Timeline of all steps with tool names, latency, and cost
  • Side-effect and compensation indicators
  • Guard event details (loops detected, budget blocks, kill-switch activations)
  • Full args hash and token counts per step

Tools

Per-tool analytics and remote configuration:

  • Stats table, call count, total cost, avg cost, avg latency, P95 latency, failure rate for every registered tool
  • Hero cards, most expensive tool, most-called tool, highest failure rate
  • Expand a row to see the configured budget, retries, and timeout
  • Configure button, edit maxRetries, maxBudget, timeout, and enabled state directly. Changes take effect within 30 seconds, no redeployment required

See Tools for the SDK side of this feature.

Workflows

Server-side analysis of tool call patterns:

  • Tool Chains, single-interaction sequences detected via n-gram analysis. If your agent calls search → retrieve → summarize in 60% of runs, that chain appears here
  • Recurring Patterns, cross-run recurring sequences. Fuze infers interaction boundaries from timing gaps and identifies tool sequences that recur across ≥ 40% of runs
  • Friction Points, tools flagged for high failure rate (> 20%) or unusually high cost (> 3× average). These are candidates for budget or timeout tuning

Trigger a fresh analysis with the Run analysis button, or wait for the automatic 6-hour background job.

Budget

Org-wide and per-agent spend tracking:

  • Daily spend with trend visualization
  • Per-agent breakdown
  • Budget ceiling indicators

Agent Health

Per-agent reliability metrics:

  • Success rate, total runs, average cost per run
  • Failure hotspot detection (which tool fails most for each agent)

Compliance Panel

EU AI Act compliance checklist:

  • Hash chain integrity status
  • Audit log coverage and retention period
  • Human oversight controls (kill switches)
  • Risk classification status

Systems

Per-AI-system inventory. Each registered system carries a provider-vs-deployer classification, risk tier (minimal / limited / high), intended purpose, and the data categories it processes. Evidence from runs, guard events, and questionnaires is attached to the system, which is what the Art. 12/14/15 conformity-assessment export packages up.

Vendor VRA

Vendor risk-assessment auto-responder. Paste a questionnaire (one question per line), click Auto-respond, and each question is matched against a built-in seed corpus plus any custom entries under Settings → VRA corpus. Every draft carries a confidence score and one of approved / drafted / needs_review / unanswered; low-confidence answers never auto-submit. Approved answers are editable inline and tracked per questionnaire (draft / in_review / sent / archived).

Team and roles (RBAC)

Members hold one of five roles, checked server-side on every mutating call:

RoleScope
ownereverything, plus organisation deletion
adminteam, settings, billing, compliance writes, run writes, audit read
membercompliance writes, run writes, audit read
vieweraudit read only
billingbilling and audit read only

Role changes go through Settings → Team and are written to the admin audit log along with actor, target, outcome, IP, and user-agent. The client never carries authority: viewers can load the UI, but the API rejects any write they attempt.

Admin audit log

Every privileged action, role change, invite, retention update, OTEL configuration, account export, account erasure, is recorded to admin_audit_log with actor UID, org, target type/id, outcome, and request metadata. The log is append-only and surfaced to owners and admins; it is also included in the GET /account/export payload.

OTEL export

Forward completed runs as OTLP/HTTP JSON traces to your own observability backend (Datadog, Honeycomb, Grafana Cloud, any OTLP receiver). Configure under Settings → OTEL export:

  • Endpoint URL (plain-http endpoints are rejected in production)
  • Per-header auth (exporter headers are encrypted at rest with AES-256-GCM; the master key is held outside the database)
  • Test connection sends a synthetic span so you see failures before enabling export
  • last_export_at and last_error are surfaced on the same page

Export is opt-in per organisation and only mutates with the settings:manage permission.

Account export and erasure

Under Settings → Retention (owners only):

  • Export, downloads a JSON bundle of the organisation, members, projects, runs, steps, guard events, retention policies, billing invoices, and the admin audit log
  • Erase, requires typing ERASE to confirm. Deletes guard events, steps, runs, alert deliveries, retention policies, API keys, projects, and members, then anonymises the organisation row and timestamps erased_at. The erasure itself is recorded in the admin audit log with per-table status.

Both actions satisfy GDPR Articles 15 and 17 for platform-stored data. Managed-backup purge follows the sub-processor's schedule (documented in the trust pack).

Deployment modes

The cloud dashboard is only available in Cloud mode. The Daemon mode exposes a REST API at :7821 for direct queries but has no web UI.

ModeConfigWeb UIAudit storage
CloudFUZE_API_KEY env varapp.fuze-ai.techSupabase (cloud)
Daemondaemon.enabled = trueREST API at :7821, no web UISQLite on-prem
Standaloneno configNonefuze-traces.jsonl

All three modes preserve the same guard() / createRun() API. See Deployment Modes for a full comparison and setup guide.

Generating compliance reports

Navigate to any run's trace replay and click Generate Report to produce an EU AI Act Art. 12 compliant incident report. The report includes:

  • Full step trace with timestamps and costs
  • Side-effect inventory
  • Compensation actions and outcomes
  • Guard events with severity classification
  • Human oversight status
  • Audit chain integrity verification