Deckgauge documentation
Open-source engineering intelligence — one board over Jira, GitHub, GitLab, and Azure DevOps, plus org trees, roadmaps, and DORA-aligned analytics.
Open source
Deckgauge is a set of containers: a web app (
:3000), an API (:3001), a background sync worker, plus Postgres, Redis, ClickHouse, and Keycloak. It's open source (FSL) and reads only from the tools you connect.
Start here
- Quickstart — clone it, stand up the containers, and get your first board synced.
- Concepts & data model — how boards, groups, rows, sources, org trees, and roadmaps fit together.
- Navigating the app — the sidebar, search, favorites, and the New menu.
- Connecting sources — credentials and sync behavior for Jira, GitHub, GitLab, Azure DevOps, and Microsoft Graph.
Platform initiatives
⋮⋮ProjectOwnerStatusUpdated
⋮⋮Checkout v2A. RiveraIn progress2d ago
⋮⋮Payments SDKS. ChenAt risk5h ago
Jira · ACME
⋮⋮ACME-142 · Guest checkoutA. RiveraIn progress3h ago
⋮⋮ACME-158 · Fraud rulesM. DeviBlocked1d ago
A board with a manual group and a synced group.
What you can do with it
- Boards — a Monday-style view of projects and synced work items, grouped and status-tracked. Read more →
- Connect sources — pull issues, PRs/MRs, commits, and work items from Jira, GitHub, GitLab, and Azure DevOps (all read-only). Read more →
- Org trees — a people hierarchy (from Microsoft Entra/Graph or CSV) with contribution ranking and per-team boards. Read more →
- Roadmaps — Gantt timelines across boards, with progress and a today line. Read more →
- Engineering intelligence — ClickHouse-backed dashboards: DORA, velocity, flow, planning accuracy, quality, and AI-adoption. Read more →
- Timesheet & workload — CapEx/OpEx time allocation and who's overloaded or idle. Read more →
Read-only, always
Read-only, always
Every code-host connector only reads. Deckgauge never writes back to Jira, GitHub, GitLab, or Azure DevOps. Stored tokens are never returned in full — masked as
*** for Jira, GitHub, and ADO, and omitted entirely for GitLab.
Last updated