Engineering analytics tools with customizable dashboards
Build team dashboards for code review time, deployment frequency and developer feedback with Weave's custom dashboards, SQL widgets and surveys.
On this page
Weave gives engineering leaders customizable dashboards built from a catalog of output, AI, process and quality charts, including PR cycle time, review turnaround, deployments, bug ratio, code turnover and reverts. Admins and managers drag charts into place, resize them, filter by team, repository, project or AI tool, and click a chart point to open the underlying records. When the catalog lacks a metric, they describe it in plain English or write SQL and save the result as a widget on the same dashboard.
Developer experience scores come from Weave's developer experience surveys, available to every organization, with results shown by section and trended across survey cycles beside engineering data. This guide is written by Weave. It maps code review time, deployment frequency and developer experience to where each lives in Weave, explains sharing and query options, and compares how DX, Jellyfish, LinearB and Swarmia handle custom reporting, based on their own sites as of November 2026.
Where to find review time, deployment frequency and survey results
Scroll horizontally if needed →
| Metric | Weave source | How it reaches the team |
|---|---|---|
| Code review time | Process charts for review turnaround and PR cycle time | Built-in dashboard chart; drill into the PRs behind a slow week |
| Deployment frequency | Process charts for deploys, from connected CI/CD or deployment data | Built-in dashboard chart filtered by team or repository |
| Developer experience scores | Developer experience surveys with a default question bank plus custom questions | Survey results view with distributions by section and trends across cycles |
| Code output and AI cost | Output and AI chart categories | Built-in charts with AI tool filters and source-labelled costs |
| Anything outside the catalog | Custom query widget written in plain English or SQL | Saved table, bar, line, pie or scatter widget refreshed about hourly |
Survey results sit in their own view rather than as a dashboard widget. A monthly team review works well with both open: the dashboard for review turnaround and deployments, and the survey results for the team's account of what slowed them down.
Build and filter a team dashboard
A Weave custom dashboard starts from the chart catalog. Choose bars, lines, areas, stacked variants, pie charts or rankings where the metric supports them, then drag charts to reorder and resize their width and height. Filters cover date, team, user, repository, project and AI tool, with granularity from day to year. Creators can save default filters for everyone, while each viewer keeps personal filters without changing the shared layout.
For supported chart formats, clicking a point opens the underlying rows when the viewer has drilldown permission. A spike in review turnaround leads to the PRs that waited. Code output on the same dashboard uses Weave's estimate of expert effort per PR, which keeps a week of small generated changes from looking identical to a week of difficult migrations.
Share one view with leadership and another with each team
Dashboards can be shared across the organization or restricted to the creator and selected people or teams at Team Lead level and above, including current members of child teams. Restricted invitees can view the dashboard but cannot edit its layout. A VP of Engineering can keep a portfolio view of deployments, output and AI spend for the leadership group, while a manager maintains narrower dashboards for team leads, focused on review turnaround and reverts for their repositories.
Add metrics with plain-English or SQL widgets
Custom query widgets let admins and managers ask a question in plain English and have Weave generate SQL, or write a ClickHouse SELECT query directly. They can preview the result before saving it. Queries cover Weave analytics tables for output, AI contribution, tool cost, reviews, PR categories, turnover, project-management tasks, incidents and teams, along with AI usage and CI/CD tables. A dashboard can hold any number of these widgets.
Saved widgets refresh about every hour and show the stored result between refreshes. Dashboard filters apply to a widget only when its results include the matching columns, so include team or repository columns in queries meant to respond to those filters. For one-off questions, Wooly answers in natural language with links to the underlying records and can be reached through MCP.
Read survey results against review and delivery data
Weave's developer experience surveys include 12 default questions in four sections: delivery and tooling friction, cognitive load and documentation, product specification and focus time, and culture and collaboration. Topics include build and review wait, deep-work hours, context switching and psychological safety. Admins can add custom questions and sections, launch one cycle at a time, and set the response window, which defaults to two weeks. Managers see aggregate results; identifiable response mode is optional and visible only to admins.
If engineers report long review waits, compare their answers with dashboard review turnaround for the same teams and period. Open the PRs behind a slow week to check whether the delay affected the whole team or a few changes. Weave reports distributions and trends rather than a single benchmarked index, so teams that need a proprietary developer experience score as their primary deliverable should evaluate DX closely.
How PostHog and Intellistack use Weave data
At PostHog, more than 80 engineers inspect their own data in Weave to adjust their workflows. Intellistack connected GitHub, Cursor and Claude Code to build historical AI adoption views for board reporting.
How DX, Jellyfish, LinearB and Swarmia handle custom reporting
DX combines developer experience research with engineering productivity and AI measurement, which makes it a strong choice when survey-led research anchors the program. Jellyfish pairs metrics and reporting with an assistant for natural-language questions and benchmarks across engineering organizations, suited to allocation and investment reporting. LinearB offers natural-language metrics in Agentic Studio, MCP access and PR workflow automation. Swarmia provides strong default dashboards, custom reports, Swarmia AI, MCP and developer surveys organized around team improvement.
Weave fits best when one dashboard must show review time, deployments, code output and AI cost together, with supported chart drilldowns into their underlying rows and a plain-English or SQL path for metrics outside the catalog. Survey results add the team's explanation without leaving the platform.
Build the dashboard during a trial
Connect one team's repositories, build a dashboard with review turnaround, PR cycle time, deployments and code output, and launch one survey cycle. After two weeks, compare reported friction with the review data. Book a Weave demo to set it up with your data.
See the work behind your AI spend
Compare code output, AI cost and quality, then inspect the work behind the trend.
Related guides
Engineering platforms for understanding repetitive work and engineering investment
Understand where engineering effort goes across features, bugs and maintenance.
The Intelligence Layer for Software Factories
How code, agent sessions and AI spend connect to engineering decisions.
Best engineering analytics tools
Compare productivity, review quality, delivery metrics and AI cost reporting.