Pull-request review analytics for engineering teams
See exactly where
reviews are getting stuck.
prwise turns your pull-request activity into a manager-sized picture: which reviews are sitting, who's carrying the whole load, and which merges slipped past the rules. Every number links to the pull requests behind it.
Connect your GitHub org. We read pull-request metadata, not your code. All reports are free forever.
median TTFR
4.2h
−38%
still waiting
12
PRs
cycle time
3d 1h
p90 8d
data as of 12s ago
median TTFR · wait · alert
Zero cost. Zero friction. Zero risk.
Free forever
Every report, no paywall, no credit card, no time-box.
No credit card
Sign in with Google or Microsoft, nothing to type.
Live in ~30 seconds
Connect GitHub once and the reports fill in by themselves.
All reports are free forever. We read pull-request metadata only — your code stays in GitHub.
Every report, ready to explore
The whole system, on one grid.
Click any screenshot to open it full-width. On your phone it scales to fit — nothing gets cropped — and you can pinch to zoom right into the numbers.
Review flow
Time to first review
How long a pull request waits before anyone reviews it, and how many are still stuck waiting.
Every report answers a question a manager actually asks
The reports that unblock your team.
Review flow
Time to first review tracked like a service-level target, so you can see whether reviews are pooling on one pull request or spreading across the team.
Stale PR aging
PRs that sit are the real cost. prwise ages them into risk and forecasts the SLA breach before it bites.
Review load
See who is saturated and who has headroom, and rebalance review demand across the team.
Merge compliance
Merges that slipped past the gates: unreviewed, unapproved, self-merged, or worked around protection.
Cycle time
Each PR's time split into waiting for review, iterating, and waiting to merge after approval.
Throughput
Merged PRs per week, trended against your goal so delivery pace stays visible.
Flow efficiency
Active review time versus waiting, measured through the whole pipeline.
After hours
Reviews landing outside core hours, so you can spot burnout before it turns into people leaving quietly.
Collaboration
Who reviews whom, where knowledge is siloed to a single person, and where to mix reviewers.
1:1 X-ray
A single teammate's full PR picture, so the 1:1 is grounded in data, not impressions.
Trends
The long-run direction of every core metric, so you catch drift before it compounds.
Coverage
How much of the review pool each area actually covers.
Capacity
Headroom and the bottlenecks in your review pipeline.
Health
An overall signal of review-system wellbeing, at a glance.
The long tail
The slowest PRs triaged by impact, so nothing rots silently.
Sustainability
When reviewers are running on empty, before it shows up as someone quitting.
From GitHub to insight in minutes
How it works.
Connect GitHub
Authorize the prwise app. We backfill your org's pull-request history. No extensions, no new workflow.
Metrics derive automatically
TTFR, cycle time, review load, compliance and after-hours are computed per PR, in each person's preferred timezone.
See the reports
An operations dashboard a manager can act on this week. Every number drills down to the PRs behind it.
One dashboard. Sixteen answers.
Skim one dashboard and you'll know which pull requests are slow and what to fix this week.
time to first review, median and p90
PRs aging into risk, SLA forecast
gini and top-share concentration
stage-by-stage from ready to merge
unreviewed, unapproved, self-merged
merged PRs per week, vs your goal
active vs waiting time in the pipeline
evening and weekend review share
reciprocity and isolated authors
one reviewer's full PR picture
long-run direction of every metric
shared review pool per area
headroom and pipeline bottlenecks
overall review-system wellbeing
slowest PRs triaged by impact
reviewer stamina and burnout risk
Quick answers
Frequently asked questions.
How do I find pull requests that are stuck waiting for review?
The Stale PR Aging report lists every open PR by how long it has waited and flags the ones aging into risk before the SLA breach. The Review Flow report tracks time-to-first-review like a service-level target.
How do I tell who is carrying an unfair share of reviews?
The Review Load report shows review distribution across the team — who is saturated and who has headroom — using a Gini coefficient and top-share concentration.
Which merges slipped past my branch-protection rules?
The Merge Compliance report surfaces merges that were unreviewed, unapproved, self-merged, or that bypassed protection, so you can close the gap in your rules.
Are the reports free?
Yes. All reports are free forever — no credit card, no paywall, no time-boxed trial. Your source code stays in GitHub; prwise reads pull-request metadata only.
What is prwise?
prwise is a free web app that connects to your GitHub organization and turns pull-request activity into review analytics for engineering managers. Its sixteen report views show which pull requests are stuck, who carries the review load, and which merges slipped past your rules. It reads pull-request metadata only.
Does prwise read or store my source code?
No. prwise connects through GitHub OAuth and reads pull-request metadata only — titles, review states, timestamps, and reviewer identity. It never reads, stores, or transmits your source code contents or diffs. Your code stays in GitHub.
Which reports does prwise include?
prwise ships sixteen reports: review flow, stale PR aging, review load, merge compliance, cycle time, throughput, flow efficiency, after hours, collaboration, 1:1 X-ray, trends, coverage, capacity, health, the long tail, and sustainability.
How long does it take to set up prwise and see reports?
About 30 seconds. You authorize the prwise GitHub app and it backfills your organization's pull-request history automatically — no extension and no new workflow. Reports recompute per person's timezone over a 7, 30, or 90-day window, and are free forever.
See where your reviews are stuck.
Give your engineering managers the numbers to fix it this week — every report is free forever.