Screenshots¶
A visual tour of the dashboard. Every image below is the live demo stack (--profile demo) seeded with the curated demo dataset โ exactly what you get from the Quickstart. Toggle the site's light/dark switch and the matrix and swimlane shots follow.
Deployment matrix¶
The default view: one row per service, one column per environment. Each tile carries version, status (success / in-progress / failure), actor, commit, elapsed time, and a link to the CI/CD run. KPIs across the top summarise services, environments, in-flight, and failed counts.

Swimlanes¶
A per-service graph view: see how a version flows from dev through qa, staging, preprod, and prod, with branching topology and status-colored edges.

Deployment feed¶
The chronological event log, grouped by deployment_id into expandable roll-ups (or flat, one row per event) via a shared toggle. Search the full history server-side, or scroll to load older pages via cursor pagination. A toggleable bottom dock mirrors the same log โ last 8 events, live via SSE with a flash on arrival โ on every other view; it's suppressed while the Feed view itself is active.

History drawer¶
Click any slot to open its full deployment history โ every event ever recorded for that (service, environment), newest first, with status, version, actor, commit, and run reference.

Analytics¶
A DORA-anchored analytics view covering the last 7, 14, or 30 days (bounded by HISTORY_RETENTION_DAYS). The KPI band at the top surfaces the four DORA keys โ deployment frequency, lead time (approximated from promotion chains), change failure rate, and mean time to restore โ followed by eight charts: deployment frequency over time, change-failure-rate trend, deployment-duration distribution (p50/p95), promotion funnel, status distribution, deploy heatmap (day-of-week ร hour), top deployers, and time-to-restore incidents.

Services filter¶
Glob pattern filter for services: type a pattern (front-*, checkout, org-a/gateway, etc.), pick "Show only" or "Show all except", and the Matrix rows and Swimlanes lanes update instantly. Patterns persist across reloads.
Namespace-aware matching. Services fetched from different GitHub repositories (or posted with a non-null namespace field) can share the same workflow/service name. Each (namespace, service) pair is a distinct row. When a name collision exists, the row label shows the namespace/ prefix; otherwise the bare name is shown. A pattern containing / matches the full namespace/service identity; a slashless pattern matches the service name across all namespaces โ existing saved patterns keep working without change. Autocomplete offers both bare names and composite namespace/service identities derived from received data.
The same widget appears in the notification preferences popover for service and environment axes.


Browser notifications¶
Opt-in desktop notifications triggered by deployment status transitions. Enable the bell toggle in the topbar โ the browser permission is requested once, lazily. Filter notifications by status, service, and environment via the notification preferences popover.

UI settings presets¶
Save, apply, share, and import named snapshots of your UI settings โ filters, display preferences, and notification configuration โ via the preset panel.

Import from URL¶
The preset panel's Import from URL field lets you paste a public HTTPS link to a single preset or a multi-preset bundle. The SPA fetches client-side โ no backend involved.
Import from URL โ accepted formats and boundaries
Demo control panel¶
The demo profile ships a Demo Driver control panel (/demo/): ingest the curated or random dataset, seed the GitHub emulator, drive live emission, trigger a system reset, and watch the deployment feed and component event streams in real time.

Install as an app¶
The dashboard can be installed as a standalone Chromium app โ a dedicated window with no browser chrome, a taskbar or dock icon, and the same deployment URL behind your gateway.

Provided presets¶
Read-only, repo/CI-sourced UI-settings presets published by a owner/repo source โ either directly over the push-mode REST recipe or automatically discovered by the Fetcher in pull mode. They appear in a PROVIDED section of the topbar presets popover, alongside any presets saved locally, with Apply and Clone-to-edit actions. Nothing here is ever written back โ provided presets are never edited or deleted from the UI.

Footer¶
A fixed glass footer persists across all views. The left side shows the running version (sourced from GET /api/version, prefixed v) and a Documentation link. The right side carries the copyright and MIT License attribution.

Want to see it for yourself? It's one command: