Allure Reports Dashboard.
Deploy with Docker Compose or Helm.
// Quick Start
Get up and running with Docker Compose or Helm.
# Download and start the full stack
$ curl -sL https://raw.githubusercontent.com/mkutlak/alluredeck/main/docker/docker-compose.yml \
-o docker-compose.yml
$ docker compose up -d
$ helm pull oci://ghcr.io/mkutlak/charts/alluredeck
$ helm install alluredeck oci://ghcr.io/mkutlak/charts/alluredeck
$ helm install alluredeck oci://ghcr.io/mkutlak/charts/alluredeck \
--set api.ingress.enabled=true \
--set api.ingress.host=allure.example.com \
--set ui.ingress.enabled=true \
--set ui.ingress.host=allure.example.com
// Capabilities
Everything you need to manage Allure test reports at scale.
Health summary cards, sparkline charts, pass rate badges, and project tags. See all your projects at a glance.
Embedded report viewer with breadcrumb navigation. Supports both Allure 2 and Allure 3 formats automatically.
Server-side computed analytics: status trends, pass rate, duration, failure categories. Branch filtering and KPI sparklines.
Interactive D3.js Gantt chart with minimap, zoom, and brush controls. Identify bottlenecks in parallel test suites.
Select two builds to see regressions, fixes, added, and removed tests. Filter by category with duration deltas.
Tag flaky tests and known bugs with regex patterns. Adjusted pass rate excludes matched tests for cleaner metrics.
Authorization Code + PKCE flow. 3-level roles (admin, editor, viewer). Azure AD, Keycloak, Okta, Google support.
Programmatic access with ald_ prefix keys. SHA-256 hashed storage, role-based, optional expiry dates.
Local persistent volumes or S3-compatible storage (AWS, MinIO). IRSA support for EKS deployments.
Cmd+K command palette with PostgreSQL full-text search. Find projects and tests instantly.
Count-based and age-based retention strategies. Daily background scheduler with safe-latest-build protection.
Catppuccin Latte and Mocha themes. Persistent preference with keyboard shortcuts for power users.
// System Design
Two-component deployment: API handles report processing, UI serves the dashboard.
Each component runs as a separate Deployment with dedicated Service, ServiceAccount, and optional NetworkPolicy. The UI proxies API requests, and CORS is auto-configured when ingress is enabled.
// Resources
Documentation, source code, and support.