Measure the system, respect the people.
Engineering metrics fail when developers stop trusting them. These are the rules DevGlimpse is built on, written down so you can hold us to them.
- 01
Teams are the unit of improvement
Delivery is a team sport. DevGlimpse leads with team and group numbers, which everyone in the workspace can see. Transparency runs up the org chart as well as down.
- 02
Your numbers belong to you first
By default a developer sees their own individual metrics and nobody else’s. Managers see the people in their own teams and groups. An admin can tighten or widen each role’s scope, and the server enforces it on every query.
- 03
Outcomes, never activity
We measure what ships: pull requests, reviews, merges and deploys. We never collect keystrokes, screen time, IDE activity, calendars or source code.
- 04
No individual rankings
DevGlimpse does not rank people against each other. Where work is uneven, like review load, we show the distribution across the team so it can be shared out, not blamed.
- 05
Every number has a definition
Each metric has a published formula, a single implementation and tests with hand-computed answers. If you can’t explain a number to the person it describes, it doesn’t belong on a dashboard.
- 06
Numbers start conversations
A slow cycle time is a question about the system: review capacity, PR size, a flaky pipeline. DevGlimpse is designed to prompt that conversation, not to settle a performance review.
- 07
AI is measured per team and tool
As AI and agent impact arrives, it rolls up by team and by assistant, never as a score on a person. Each developer gets a private view of their own AI usage.
- 08
Leaving is easy
Export your data at any time, delete it immediately, or uninstall and get a visible 30-day read-only window. Trust means never being locked in.
“If a developer wouldn’t be comfortable seeing it about themselves, DevGlimpse shouldn’t show it about anyone.”
DevGlimpse is free for up to 10 contributors, with no time limit.