GitHub Analytics Platform

Engineering performance, made visible

Transform your GitHub activity into actionable insights. Track PR cycle time, review health, contributor engagement, and delivery metrics in real-time.

Coming Soon
2.3d
Avg Cycle Time
12% faster
94%
Review Coverage
+3%
156
PRs Merged
+24 this week
8.2h
Time to Review
Under SLA
12
Contributors
All active
8.4
Engagement Score
+0.6
0
At Risk
Healthy team
42
Reviews Given
+8 this week
2.3d
Avg Cycle Time
12% faster
94%
Review Coverage
+3%
156
PRs Merged
+24 this week
8.2h
Time to Review
Under SLA
12
Contributors
All active
8.4
Engagement Score
+0.6
0
At Risk
Healthy team
42
Reviews Given
+8 this week
5
Champions
+1 new
98%
SLA Compliance
On target
3.2x
Throughput
vs last month
24h
Avg Pickup Time
-6h improved
2
Stale PRs
Needs attention
847
Commits
+127 this week
15%
After Hours
Healthy balance
8
Repositories
All synced
5
Champions
+1 new
98%
SLA Compliance
On target
3.2x
Throughput
vs last month
24h
Avg Pickup Time
-6h improved
2
Stale PRs
Needs attention
847
Commits
+127 this week
15%
After Hours
Healthy balance
8
Repositories
All synced
Features

Everything you need to improve delivery

Built for modern engineering teams. Focus on outcomes, not vanity metrics.

Delivery Flow Analytics

Track PR cycle time, throughput trends, and bottleneck analysis. Identify where time is spent and optimise your delivery pipeline.

  • Cycle time breakdown
  • Cumulative flow diagrams
  • Review SLA compliance

Team Engagement

Monitor contributor health, identify at-risk team members, and recognise champions. Balance workload based on role expectations.

  • Engagement scoring
  • Burnout detection
  • Role-based expectations

Code Quality Insights

Track review coverage, code ownership, and identify bus factor risks. Ensure quality gates aren't being bypassed.

  • Review reciprocity matrix
  • Code ownership tracking
  • Self-merge detection

Productivity Metrics

Understand output patterns, commit frequency, and working hours distribution. Identify productivity trends without surveillance.

  • Working hours heatmap
  • Expected vs actual output
  • Contribution consistency

Repository Health

Monitor repository activity, stale PR accumulation, and maintenance patterns across your entire organisation.

  • Multi-repo dashboards
  • Stale PR tracking
  • Activity trends

Group Comparison

Compare teams, squads, or custom groups side-by-side. Understand relative performance and share best practices.

  • Cross-team benchmarks
  • Custom group definitions
  • Trend comparison
Dashboards

Six powerful dashboards

Each dashboard answers a specific question about your engineering organisation.

Delivery Flow

"How fast do changes ship?" Track cycle time, throughput, and review SLA compliance.

Productivity

"Who is contributing and when?" Understand output patterns and working hours.

Code Quality

"Is the review process healthy?" Track coverage, ownership, and quality risks.

Repository Health

"Which repos need attention?" Monitor activity and maintenance patterns.

Group Comparison

"How do teams compare?" Benchmark squads and share best practices.

Engagement

"How engaged is the team?" Identify at-risk contributors and champions.

Real Results

Teams see improvements within weeks

When teams have visibility into their delivery process, they naturally optimize it.

40%
Faster Cycle Time
Average improvement in 90 days
95%
Review Coverage
Teams achieve with visibility
60%
Fewer Stale PRs
Reduced backlog within 30 days
2x
Review Throughput
When bottlenecks are visible

Cycle Time Trend

38% faster
Week 1
5.2 days
Week 4
3.9 days
Week 8
2.8 days
Week 12
2.2 days

Teams identify bottlenecks and streamline their process

Review Coverage

+27%
95%
Before 68%
After 95%
Self-merges 12% → 2%

Visibility drives accountability and better practices

Reduced Bottlenecks

"We discovered one senior dev was doing 70% of reviews. Redistributing the load cut our review time in half."

Team Balance

"After-hours metrics helped us identify burnout early. We caught it before losing a key team member."

Faster Delivery

"Seeing cycle time trends motivated the team to ship smaller PRs. We went from weekly to daily deploys."

Ready to see your team's potential?

Connect your first repository in under 5 minutes. No credit card required.

Security

Your code stays yours

We process metadata only. No source code is ever stored or accessed.

Read-Only Access

We can never modify your code, PRs, or repository settings.

Metadata Only

We process PR titles, timestamps, and commit hashes—never file contents.

Your Data, Your Control

Disconnect anytime. Export your data. Delete everything on request.

FAQ

Frequently asked questions

Everything you need to know about Perfo.Team

Metrics & Analytics

How do you calculate PR cycle time?
Cycle time is measured from PR creation to merge. We also track key milestones like time to first review, time to approval, and time waiting for CI—helping you identify exactly where bottlenecks occur in your workflow.

What individual contributor metrics do you track?
For each contributor we track: commits and PRs merged, lines changed (additions/deletions), reviews authored, average cycle time, time to review, engagement score, after-hours activity ratio, and workload balance compared to role expectations. We also identify champions and at-risk contributors based on engagement patterns.

What is the engagement score?
The engagement score is a composite metric reflecting contributor participation and sustainability. Positive factors: regular commits, active review participation, timely PR merges. Negative factors: extended inactivity, stale PRs, high after-hours work. Scores range from 0-10, with 8+ being excellent and below 3 indicating risk.

How do you detect burnout risk?
We track after-hours activity ratio—the percentage of commits and reviews outside normal work hours (8am-8pm in each contributor's timezone). Sustained rates above 20% warrant attention, and above 40% indicates immediate intervention is needed. Combined with workload ratio data, you can identify overloaded team members before burnout occurs.

Technical Setup

Why do you need force pushes blocked?
Force pushing rewrites Git history, changing commit SHAs. When a commit SHA changes, the commit we've already imported becomes orphaned—leading to duplicate data or gaps in your metrics. Blocking force pushes ensures consistent, accurate tracking over time.

What if we use squash merges?
Squash merges work great! All PR-level metrics (cycle time, review coverage, throughput) remain fully accurate. The only caveat: individual commit counts reflect the squashed commit rather than original branch commits, which may slightly affect commit-level productivity metrics.

How long does initial setup take?
Most teams are up and running in under 10 minutes. Connect your GitHub account, select repositories, and we'll start importing. Initial data import may take a few hours for large repositories with extensive history, but you'll see data appearing within minutes.

How do you handle bot activity?
You can configure repository filters to exclude bot activity (Dependabot, Renovate, etc.) from your metrics. Filter by author patterns, file paths, or branch names. This ensures your team's metrics reflect actual human contribution, not automated updates.

Security & Privacy

Do you store my source code?
No, never. We process GitHub metadata only—PR titles, timestamps, commit hashes, and file paths. We never read, access, or store the actual contents of your code. Your intellectual property stays yours.

What GitHub permissions do you need?
Read-only access. We request permission to read repository metadata, pull requests, commits, and reviews. We can never modify your code, PRs, branches, or any repository settings. You can revoke access anytime from your GitHub settings.

Do you support private repositories?
Yes! Private repositories work exactly the same as public ones. You control which repositories to connect, and we only access the ones you explicitly authorize. Organisation repositories require appropriate GitHub permissions.

Do you support SSO/SAML?
SSO/SAML authentication is available on our Enterprise plan. We support integration with major identity providers including Okta, Azure AD, Google Workspace, and others. Contact our sales team to discuss your specific requirements.

Billing & Plans

Can I try before I buy?
Absolutely! Our Starter plan is free forever with 1 repository and 5 contributors. For larger teams, all paid plans come with a 14-day free trial—no credit card required. Test everything before committing.

What's the difference between Plus and Pro?
Plus is designed for small teams (up to 5 repos, 15 contributors) with 30-day retention. Pro removes all limits—unlimited repositories and contributors, 90-day retention, plus team management features and group comparison dashboards for scaling teams.

Can I cancel anytime?
Yes, absolutely. Cancel from your billing settings anytime, no questions asked. Your data remains accessible until the end of your billing period. We also offer full data export if you need to take your metrics history elsewhere.

How does per-user pricing work?
You're billed based on the number of active contributors—people who have committed code or reviewed PRs in your connected repositories during the billing period. Inactive GitHub accounts don't count toward your limit. You can add or remove contributors anytime, with billing adjusted pro-rata.