A customizable team dashboard built with Next.js and React, featuring widgets for Jenkins, JIRA, GitHub, and other development tools.
Dashboard is an open-source team dashboard builder that allows development teams to create custom dashboards with widgets for monitoring Jenkins jobs, JIRA issues, GitHub metrics, SonarQube scores, and other tools. It solves the problem of fragmented tool visibility by aggregating key data into a single, customizable interface. Built with Next.js and React, it provides a modern, component-based approach to dashboard creation.
Development teams, DevOps engineers, and engineering managers who need a centralized view of CI/CD pipelines, issue trackers, and code quality metrics. It's particularly useful for teams using Jenkins, JIRA, Bitbucket, GitHub, SonarQube, or Elasticsearch.
Developers choose Dashboard because it's a lightweight, self-hosted alternative to commercial dashboard solutions that offers pre-built widgets for popular dev tools. Its modular design and open-source nature allow for easy customization and extension without vendor lock-in.
📺 Create your own team dashboard with custom widgets. Built with Next.js, React, styled-components and polished.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Includes ready-to-use components for Jenkins job status, JIRA issue counts, GitHub issues, and more, as detailed in the README, saving development time.
Allows creating separate dashboards for different teams or projects, like 'team-unicorn.js', enabling tailored views without code duplication.
Supports deployment via Docker, npm scripts, or platforms like Vercel, giving teams full control over hosting and data privacy.
Offers light and dark themes for visual preference, with easy integration into dashboard components, as shown in preview images.
Only supports a specific set of tools; integrating new services requires building custom React components, which may be complex without React expertise.
Requires setting up a proxy server for cross-origin requests, adding deployment complexity and potential performance bottlenecks, as noted in the CORS section.
Relies solely on HTTP basic authentication, lacking support for modern OAuth or token-based security, which could be insufficient for enterprise environments.