Skip to main content
DevPerform connects to your code host — GitHub, GitLab, or Bitbucket — and turns your delivery data into the metrics engineering leaders actually need: how work flows, where it stalls, how healthy the team is, and — increasingly — how AI is changing the way code gets written. Everything works the same whichever of the three your team uses.

​
What DevPerform gives you

Delivery & flow

DORA’s four keys, phased cycle time, review health, and weekly trends.

Code quality

Line-level rework/churn and the files that change the most.

AI-native metrics

Human vs. AI-assisted vs. agent-authored work, acceptance, and rework on AI code.

Team health

DX and engagement surveys, driver analysis, goals, and an executive summary.

​
A team-health tool, not a ranking tool

DevPerform measures teams and systems. Individual data is shown only as a person’s own self-view or as a protective health signal (like a burnout flag) — never as a ranked “who’s fastest” scoreboard. We don’t treat lines of code or PR counts as productivity scores, and we don’t track keystrokes or individual activity. This is a deliberate stance: gamifying individual output metrics backfires, and in the AI era raw line counts mean even less.

​
How it works, briefly

  1. Sign in with GitHub, GitLab, or Bitbucket, then connect the org / group / workspace and add the repos to track.
  2. Engineers are added to a roster (manually or imported from your org / group / workspace in one click).
  3. DevPerform syncs your PR/MR, review, and commit metadata into its own database — hourly and on demand — so dashboards are fast and history builds up over time.
  4. Metrics are computed from that store and shown per team, per engineer, and org-wide.
Use a different code host (e.g. Azure DevOps)? Contact sales — we add providers based on demand. DevPerform stores delivery metadata (PR titles, authors, timestamps, review events, file paths, line counts) and computed aggregates — not your source code. See How DevPerform works for the full picture.
Some metrics (rework/churn, AI-native metrics) are part of the Pro plan. Each metric page notes its plan. See Plans.