TuiQiao/CBoard

An easy to use, self-service open BI reporting and BI dashboard platform.

View on GitHub ↗Jump to charts ↓

TuiQiao/CBoard has 3k+ stars and 1k+ forks on GitHub, is written in JavaScript, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 3 minutes ago
Added to GitGenius on September 22nd, 2026
Created on September 21st, 2016
Open Issues & Pull Requests: 100 (+0)
GitHub issues: Enabled
Number of forks: 1,149
Total Stargazers: 3,097 (+0)
Total Subscribers: 269 (+0)

Repository Insights (GitGenius)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 87 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

CBoard is a self-service open business intelligence platform for creating dashboards and reports without requiring technical expertise.

The platform addresses the need for non-technical users to build and explore data visualizations independently. It provides a web-based interface where users can connect to data sources, design dashboards through drag-and-drop interactions, and share insights across their organization. The tool handles the complexity of querying and visualization configuration, allowing business users to focus on analysis rather than technical implementation.

Organizations with business users who need to create ad-hoc reports and dashboards should consider CBoard if they want to reduce dependency on data engineers for routine visualization work. The platform suits teams that value self-service analytics and want to democratize data access. The README positions CBoard alongside other open business intelligence tools in the same category, indicating it competes in a space with established alternatives, though specific comparisons are not detailed.

Development activity shows consistent engagement with the codebase through regular commits and pull request reviews. The project maintains responsiveness to issues raised by users, addressing problems and incorporating feedback. Contributors demonstrate attention to code quality through review processes before merging changes. The maintainers actively update documentation to reflect platform capabilities and improvements.