PanDev Metrics — transparent metrics on how your team works
TL;DR. Not screen surveillance. Automatic capture of work signals that replaces guesswork with facts and gives developers back the context of their work. This page is the deck we hand to engineering teams before a rollout — read it here, or download it as a PDF to send round.
What developers get
AI contribution = your contribution
Work with AI counts the same as hand-written code. Use AI tools to automate routine work — every minute of their activity goes to your credit.
Overtime is now visible
You can see when you actually worked: evenings and weekends are recorded. Use that data in your own interest — at a performance review, or when reshaping team processes.
No more manual reports
The system collects data automatically and links it to tasks. You no longer spend time writing reports.
See what eats your time
Endless meetings and operational work that drain the team's time are now visible on charts.
Security
Collection stays inside the work perimeter: corporate repositories, domain allowlists, and metadata only wherever metadata is enough.
Company projects only
Only company projects are collected — personal and pet projects are not. Detection is based on the git project: only repositories from the corporate GitLab count. The status is shown in the indicators, so at any moment you can see whether the current project is collected or not collected.
Allowlists only
Plugins collect data strictly by allowlist: corporate domains only, and only what relates to work. The list is open — you can see it in the extension settings.
We don't collect source code
All source code stays on your side. Plugins don't read it, don't store it, and never transmit it.
No screenshots or screen recording
Only work in work tools and on work branches is recorded, and in the browser — activity on allowlisted domains. Nothing else is collected.
What data we collect
| Source | What is collected | Data type |
|---|---|---|
| IDE plugins — activity JetBrains, VS Code, Eclipse, etc. | Working time, project, module, language, file name and path, git branch, IDE name, line number and cursor position | Metadata — work metadata only; code contents are not transmitted |
| IDE plugins — app runs | Time, status (success or error), run configuration, class, module, branch | Metadata |
| IDE plugins — commits | Hash, branch, author, time, commit message text | Work data — metadata and message text; diffs and code are not transmitted |
| CLI — terminal | Time, directory, project type, shell, full text of the entered command | Work data — metadata and the text of work commands |
| CLI — AI tools Claude Code, etc. | Tool, model, time, token count, which files the AI edited and how many lines, prompt text | Work data — usage metadata; prompt text is configurable, a text-free mode is available |
| Chrome extension — browser | Time, tab title, full URL | Work data — page title and address; page contents are not read. Optional module |
| Chrome extension — Google Meet | Time and meeting code, participants, full conversation transcript | Work data — transcripts of work meetings. Optional module, enabled for work calls only |
| DB plugin (DBeaver) | Connection, database, host, account, SQL query text, old and new value on a manual cell edit | Work data — work SQL queries and edits. Optional module |
The same deck as a PDF
Handy when you need to send it to the team or show it on a screen:
PanDev Metrics — presentation (English, PDF, 3 slides)
PanDev Metrics — презентация (Russian, PDF, 3 slides)
Where to go next
- Product overview — what the platform does end to end.
- What we collect — the same data seen from the metrics side.
- Privacy policy — the legally binding version of the same boundaries.