Engineering metrics for GitHub teams

Let your team ship faster.

See what is slowing your team down, fix the bottleneck, and track the improvement week by week. Clear team insight, without micromanagement.

Read-only GitHub App No source code access 7-day trial, no card
Features

Delivery metrics from GitHub, in one dashboard.

Connect your organization once and DXLens keeps every metric current, with history, trends and a daily digest included.

Core delivery metrics

Cycle time, time to first review, throughput and review coverage, reported as p50 and p90.

Trends over time

Week-over-week and month-over-month change for every metric, so you can confirm whether a process change had an effect.

Daily digest in Slack or email

A morning list of pending PRs plus weekly recaps, based on rules and channels you configure.

By repository and team

Filter any metric by repository or team to locate where work slows down.

Unlimited viewers

You pay only for the developers being measured. Managers, product and anyone else can view for free.

Read-only installation

A GitHub App with read-only scopes. Select your repositories and historical data is imported automatically.

Methodology

A focused set of metrics.

DXLens reports the measures that help teams improve how work flows, and leaves out the ones that encourage gaming or comparison between individuals.

What we measure

Cycle time. Time from pull request opened to merged, shown as p50 (the typical case) and p90 (the slowest cases).

Time to first review. The earliest and most reliable signal of a review bottleneck.

Review load. How review work is distributed, including who is waiting on whom.

Pull request size. Larger changes take longer to review and merge, so size is tracked alongside speed.

Every metric can be broken down by repository, team and person, and is reported as percentiles rather than averages so outliers do not distort the picture.

What we leave out

Most DORA metrics. They were designed for large enterprises with dedicated release and incident teams. For most teams, time is lost in review, so that is where DXLens focuses.

Commits per developer. It measures activity rather than impact, and individual rankings erode trust in the data.

Lines of code. Code volume is not a meaningful measure of productivity.

Source code analysis. DXLens reads pull request metadata only and never accesses your code.

Teams accept the numbers and act on them when no one is being ranked.

Team activity

When your team does its work.

A weekday-by-hour heatmap of when pull requests are opened, reviewed and merged, adjusted for each team's timezone. Use it to spot:

Late Friday merges, which carry more deployment risk
Sustained late-night activity, an early sign of burnout
Working-hour overlap between distributed teams
Focus days and whether they hold in practice
PR activity by weekday and hourPlatform · CET
0006121824
LessMore
AI-assisted pull requestsLast 90 days
AI co-authored
34%▲ 9 pts
AI reviewed
18%▲ 5 pts
Share of PRs with AI involvement, by week
AI adoption

Track how AI is used in your pull requests.

See the share of pull requests with AI co-authored commits or AI reviews from tools such as Copilot, Claude, Cursor and CodeRabbit, by team and repository.

How it is measured. DXLens detects Co-authored-by commit trailers and known AI review bots. IDE autocomplete is not recorded in commits, so treat these figures as a lower bound and use them to follow the trend.

Daily digest

Your team's PRs, summed up every morning.

Large PRs worth splitting. Pull requests above the size you set, so they can be broken up before review.

PRs waiting for review. Anything open longer than your review target, oldest first.

Delivered to Slack or email. You choose the rules, channels and schedule.

Getting started

One installation. No code changes.

Step 1

Install the GitHub App

Grant read-only access to the repositories you choose. No write permissions, CI changes or agents are required.

Step 2

Choose repositories and developers

Select what is in scope for your plan. You can change the selection at any time in settings.

Step 3

Open your dashboard

Historical data is imported on connection. Send the daily digest to any Slack channel or email address.

Pricing

Pay only for the developers you track.

Viewers are always free. Adjust the slider to estimate your monthly cost.

10
5200
Team Most popular

For organizations that use one shared setup.

$3.50per developer / month
  • 90 days of history
  • Up to 50 repositories
  • Unlimited viewers
  • One Slack channel, plus email digests and recaps
Start free trial

7 days free, no credit card required

Business

For organizations where each team configures its own setup.

$5per developer / month
  • Everything in Team
  • Per-team Slack channels, schedules and thresholds
  • Team comparison
  • 12 months of history
  • Up to 200 repositories
  • Priority support
Start free trial

7 days free, no credit card required

Included in every plan
  • Cycle time, review and throughput (p50 and p90)
  • Review coverage and PR size distribution
  • AI adoption tracking
  • Team activity heatmap
  • Quarterly and year-to-date reports
  • Filters by repository, team or person

Subject to our fair use policy.

Contact

Get in touch.

Questions about the metrics, a larger organization or a custom plan? Send us a message and we will get back to you.

support@dxlens.io
Thanks, we will get back to you.