Short answers to the questions we hear most. For anything else, see Support.
Source code and data
Does DevGlimpse read our source code?
No, it never stores or shows it. DevGlimpse reads pull-request, review, commit, deployment and membership metadata. On GitHub it needs the Contents (read) permission only to list commits, and never fetches file contents or diffs. GitLab reports no line counts, so there a merge request's diff is read once to count added and removed lines, and only those two numbers are kept. See GitHub App permissions.What data do you store?
Repositories, pull requests (titles, states, timestamps, sizes), reviews and review comments, commit metadata (author, date, message and line counts), teams and membership, and what you connect from other sources such as deployments, CI runs, tickets and incidents. It also stores daily metric rollups, workspace settings and an audit log. The full list is on the Security page.Where is our data stored?
DevGlimpse is fully hosted, so there is nothing for you to run. Each workspace is isolated from every other, and credentials and export files are encrypted under a key that belongs to your workspace. EU data residency is on the roadmap. See Security and Sub-processors for who processes data and where data location details are published.Measurement and privacy
Can a manager rank developers against each other?
DevGlimpse has no individual leaderboards. Team and group numbers are visible to everyone. Individual numbers follow a scope your admin sets per role (everyone, reporting line, my groups, or only myself), and the server enforces it. See Visibility and Measurement principles.Is this surveillance?
No. DevGlimpse measures outcomes such as cycle time and review latency, not keystrokes or screen time. AI impact is measured from commit and pull-request signatures and from usage that assistants report through a privacy allowlist. Small teams are protected by a minimum group size, and pseudonymous mode (by plan) can hide names.Who can see my numbers?
It depends on your admin's settings. By default, developers see only themselves, managers see their own groups and teams, and admins see everyone. You always see your own numbers.Deletion and leaving
What happens if we leave?
Export everything at any time. Uninstalling the App puts the workspace in read-only mode with a visible deletion date 30 days out, and the data is deleted after that. An admin can also delete everything immediately. See Data and deletion.Can we remove one person's data?
Yes. An org admin can exclude a person from every report, or erase them permanently. See Data and deletion.Pricing and setup
What does it cost?
DevGlimpse is free for up to 10 tracked contributors, with no time limit. A workspace with more than 10 active contributors can ask for a 14-day full-organization Team trial, then falls back to Free; nothing is deleted. Paid plans are priced per active contributor, meaning a non-bot person with a commit, pull request or review in the last 30 days. Team has no minimum; Founding has a minimum of 20 paid contributors. See License.How long does setup take?
Minutes. An org admin installs the app, and DevGlimpse backfills 90 days of history inside the host's rate limits. Dashboards fill in as the backfill lands. Very large organizations take longer for the full history. See the Quickstart.Supported providers
We use GitLab, Bitbucket or Jira. Is DevGlimpse for us?
Yes. GitHub, GitLab and Bitbucket Cloud are live as code sources. Linear, Jira Cloud and Asana are live for tickets, and PagerDuty, incident.io and Opsgenie for incidents. See Integrations.