Welcome to PanDev Metrics
TL;DR. PanDev Metrics is the glue between Git, Jira, and your engineering environment. Git shows only the artefacts of finished work, and task trackers reflect reality ~30% of the time — together they give no more than 40% of the picture. PanDev Metrics closes the remaining 60% with developer-tool telemetry — IDE plugins, browser extensions, and terminal plugins for Claude Code and Codex CLI: real coding hours, debugging time, AI sessions, context switches, deep work. It is the only platform that calculates the true cost of every feature your team ships.
Who PanDev Metrics is for
PanDev Metrics is built for engineering organisations with 10 or more developers who value a data-driven approach.
It will not help organisations that are not built around code, or teams whose primary work is not writing software (pure DevOps / security / IT-ops setups, for example). The product earns its keep when coding is the core activity.
What you get
PanDev Metrics turns IDE, Git, and task-tracker signals into the picture you need to lead an engineering team. Here's what every tenant gets out of the box.
- Real engineering hours, not "status: in progress" — actual time in the IDE, broken down by deep work, debugging, AI prompting, and switches.
- DORA metrics on top of real cost data — Deployment Frequency, Lead Time, Change Failure Rate, MTTR, plus the dollar value of every release.
- Honest cost per feature — direct task time multiplied by the developer's hourly cost, plus a fair share of unallocated time.
- One dashboard for the whole engineering org — IDE, Git, and task tracker in a single view.
Choose your deployment
PanDev Metrics ships in two flavours. Both expose the same product surface; the differences come down to identity and multi-tenancy.
| Cloud | On-prem | |
|---|---|---|
| Hosted by | PanDev | Your own infrastructure |
| Multi-tenant | Yes — multiple organisations per user | No — one organisation per install |
| Authentication | Email + password, Google sign-in, LDAP / AD | Email + password, LDAP / AD |
| Updates | Automatic | Manual (you bump the tag) |
| Time to first metric | 15–20 minutes | 1–2 hours |
| Hardware footprint | None on your side | 24+ CPU, 40+ GB RAM, 150+ GB SSD |
Cloud (SaaS)
The fastest way to start. PanDev hosts everything; you get automatic updates, scaling, and a Google sign-in option. Suitable when you have no compliance reason to keep data on-premises.
On-prem
You run PanDev Metrics on your own servers, behind your own firewall. Same product, minus Google sign-in and multi-tenancy. Suitable when data residency is non-negotiable.
On-prem Quick Start → · System requirements
Personal workspace
A separate single-user track for an individual developer. Personal metrics, gamification, and history that stays with you between jobs — independent of any company workspace.
How PanDev Metrics works
PanDev Metrics is a thin platform that sits across four data sources:
- IDE plugins (JetBrains, VS Code, Visual Studio, Cursor, Windsurf, Xcode, Eclipse), browser extensions (Chrome, Brave, Edge, Firefox, Opera, Arc, Vivaldi, Yandex, Whale, Sidekick), and terminal plugins for Claude Code and Codex CLI stream events — file edits, scrolls, opens/closes, AI sessions, and CLI commands. Source code and screenshots are never collected.
- Git integrations (GitHub, GitLab, Bitbucket, Azure DevOps) ingest commits, PRs/MRs, releases, and merge events into production branches.
- Task tracker integrations (Jira, Yandex Tracker, ClickUp, Azure Boards) bring in tickets, transitions, and worklogs.
Daily cron jobs rebuild materialised views — that is how new DORA numbers, finance totals, and dashboards stay fresh.
What's new
Latest product news, release breakdowns, and a running summary of what shipped and what's coming next — on a dedicated page.
Next steps
Continue with the deployment that fits your team — Cloud for fastest start, on-prem for full data control, personal for an individual track.
- Pick your deployment — Cloud, on-prem, or personal
- See the full feature list — what is in every PanDev Metrics tenant
- Read the IDE plugin overview — where telemetry comes from
Related
Sideways links if you want to understand the model first, or jump straight to integration specifics.
- Concept: How PanDev Metrics computes IDE hours — the 15-minute gap rule
- Reference: Integration matrix — every supported source