Skip to content
Request early access
ProductPrinciplesSecurityRoadmap Request early access
Early access Now inviting design partners

Know how your team ships.
Without watching anyone.

DevGlimpse turns GitHub activity into calm, team-first delivery insight: cycle time, review wait, PR size and throughput, live minutes after you install. Next, what AI and agents actually ship, across every vendor.

Become a design partner → See how it works
  • Read-only GitHub App
  • Never reads your code or diffs
  • Nothing to host or run

Sample data. Hover the chart.

How it works

Minutes from install to insight.

No agents to deploy, no Jira hygiene to fix first, no six-week onboarding. Connect GitHub and read your first dashboard the same day.

  1. 01

    Install the GitHub App

    An org admin installs DevGlimpse. We verify it on GitHub and create your workspace.

    Metadata read
    Pull requests read
    Contents read · commit list only
    Members read
  2. 02

    90 days, backfilled

    DevGlimpse walks your history within GitHub's rate limits and checkpoints every page.

    acme/payments-api 0 PRs
    acme/webqueued
    acme/mobilequeued
  3. 03

    A dashboard for every team

    GitHub teams arrive on their own. Custom groups cover everything else.

    PlatformPaymentsMobileDataGrowthSRE + New group

Self-healing Webhooks keep it live. A nightly reconcile repairs anything GitHub failed to deliver.

Metrics

Four metrics. Defined in plain sight.

Black-box scores breed distrust. Every DevGlimpse number has a published definition, one implementation, and tests with hand-computed answers.

  • Bots are excluded everywhere.
  • Sums travel with their counts, so any window averages correctly.
  • Teams and groups roll up from the same contributor rows.

Cycle time

Live

How long a pull request takes from opened to merged.

merged_at − created_at Counted on the merge day, for the author.

Review wait

Live

How long the author waited for the first human review.

min(review.submitted_at) − created_at Bot reviews never start the clock.

PR size

Live

How big the change was when it merged.

additions + deletions Smaller PRs are reviewed faster and break less.

Throughput

Live

The volume of shipped work, each counted on the day it happened.

commits · PRs opened · PRs merged · reviews Always the day of the event itself.
Privacy by design

Team numbers for everyone.
Your numbers for you.

Each role's view of individual metrics is a workspace setting, enforced on the server on every query. Rows outside your scope never reach your browser. Try it.

View as
Contributor Cycle time Review wait Merged
A Asha K. you 1d 1h 2h 40m 14 Outside your scope · filtered on the server
M Mateo R. 22h 3h 05m 11 Outside your scope · filtered on the server
L Lin W. 1d 6h 1h 50m 9 Outside your scope · filtered on the server
P Priya S. 1d 9h 4h 10m 12 Outside your scope · filtered on the server
S Sam O. 2d 2h 3h 30m 7 Outside your scope · filtered on the server
N Noor A. 1d 4h 2h 55m 10 Outside your scope · filtered on the server
Team aggregates · always visible
P Platform 1d 2h 2h 32m 34
P Payments 1d 16h 3h 32m 29
What DevGlimpse measures
  • Pull request timestamps, sizes and states
  • Reviews and review comments, and when they happened
  • Commit counts and dates
  • GitHub teams and org membership
What DevGlimpse never touches
  • Your source code, file contents or diffs
  • Keystrokes, screen time, IDE activity or calendars
  • Individual leaderboards or stack ranking
  • Your personal GitHub token. It is used once at sign-in and dropped
  • Your data sold, or used to train AI models

Read our measurement principles

Building now

Humans and agents,
side by side.

Your teams run two to four AI tools at once. Each vendor's dashboard only sees itself. DevGlimpse sees what actually merged: human, AI-assisted or agent-authored, across every vendor.

Vendor-neutral Claude CodeCodex CLIGitHub CopilotCursorGemini CLIAny OpenTelemetry source
Building now

Adoption and spend

Who uses which assistant, how often, and what it costs, by team and by tool.

Building now

Output vs. merged code

What AI suggests against what survives review, so acceptance isn't just a vendor's number.

On the roadmap

Quality, compared

Reverts, follow-up fixes and incidents for AI-assisted work next to human work.

On the roadmap

The review bottleneck

More PRs means more review. See where AI shifts the load, before reviewers burn out.

AI numbers are shown per team and per tool, never as a score on a person. Each developer gets a private view of their own AI usage.

Where we are

What's live, and what's next.

We'd rather be honest than impressive. Here is exactly what works today and what's coming. Design partners help decide the order.

Live In production today.
Building now Specified and in active development.
On the roadmap Designed, and next in line.

See the full roadmap →

Security

Trust you can verify, not a badge wall.

DevGlimpse is serverless on Cloudflare, Neon Postgres and Hasura, so there is nothing for you to run or patch. These guarantees are built in and tested today.

Two walls between tenants

Every query is scoped to your workspace by the GraphQL layer and again by Postgres row-level security. Both are tested with real tokens on every change.

Read-only, least privilege

Sync runs on short-lived GitHub installation tokens. Nobody’s personal token is stored or sent anywhere.

Sessions that never leak

Signed RS256 session tokens. Sign-in hands over a one-time code, so a token never appears in a URL.

Every privileged action, on record

An append-only audit log covers role changes, approvals, invites, exports and more. Updates are refused at the database.

Your data, portable

Export contributors, pull requests, reviews and rollups as JSON whenever you like. No ticket, no call.

Leave cleanly

Delete your workspace immediately, or uninstall and get a visible 30-day read-only window before deletion.

Questions

Asked, answered.

Something else? hello@kubeace.com

Does DevGlimpse read our source code?

No. The GitHub App reads pull-request, review, commit and membership metadata. It needs Contents (read) only to list commits, and it never fetches file contents or diffs.

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, my groups, or only myself), and the server enforces it.

How long does setup take?

Minutes. An org admin installs the GitHub App, and DevGlimpse backfills 90 days of history within GitHub’s rate limits. Dashboards fill in as the backfill lands; very large orgs take longer for the full history.

What does it cost?

DevGlimpse is free for design partners during early access. Paid plans will be priced per active contributor (a non-bot person with a commit, PR or review in the last 30 days), with no minimum seats. Founding partners keep a locked rate.

We use GitLab, Bitbucket or Jira. Is DevGlimpse for us?

GitHub is live today. Linear is next, and GitLab, Bitbucket, GitHub Enterprise Server, Jira and Asana are on the roadmap. Tell us your stack when you request access; it shapes the order.

How will you measure AI impact without surveillance?

From outcomes, not keystrokes. PR and commit signatures classify AI-assisted work, and assistants like Claude Code and Codex report usage over OpenTelemetry with a privacy allowlist. Results roll up per team and tool, and each developer gets a private view of their own.

What happens if we leave?

Export everything as JSON at any time. Uninstalling puts the workspace in read-only mode with a visible deletion date 30 days out, or an admin can delete everything immediately.

Design partners

Build it with us.

We're working closely with a small group of teams of 20 to 500 engineers on GitHub. You bring the questions you can't answer today; we build the answers into DevGlimpse.

  • Free through early access Use DevGlimpse in production at no cost while we build together.
  • Founding pricing, locked Your rate is fixed when paid plans arrive. No minimum seats, ever.
  • A direct line to the builders A shared channel with the engineers writing DevGlimpse, not a ticket queue.
  • Shape what ships next AI impact, DORA, Linear and Jira: your needs set the order.
Become a design partner → Email us