Getting Started
Last updated: September 2026
GitKraken Insights is the dashboard your engineering organization uses to see — in one place — how AI tools, code delivery, and team capacity actually interact. This section gets you oriented in about ten minutes.
First Dashboard
Guided walkthrough of the /teams page
For Executives
Four numbers and a story for your monthly report
For Engineering Leaders
Weekly scans, quarterly reviews, and settings checks
For Team Leads
Weekly pulse on flow, blockers, and review health
For Admins
Settings, roster, integrations, and data hygiene
What this product does
It connects your git provider, your AI coding tool telemetry, your Jira customer bugs, and your BambooHR PTO calendar, and produces a small set of trustworthy numbers for engineering leadership.
What this product does not do
- It does not rank or compare individual developers against each other for performance reviews. The scoring framework is designed for trend reading and cohort comparison, not for slotting people on a curve.
- It does not replace your standup, your retro, or your one-on-ones. It surfaces patterns that should become conversations.
- It does not produce real-time alerts. The numbers refresh on a window (default 14 days) and are designed for weekly / monthly / quarterly review.
Three pages that matter most
| Page | When to use it |
|---|---|
| /teams (the default landing) | Weekly leadership review. Team-by-team adoption and delivery, side by side. |
| /developers | When you want to drill into individuals: who’s a Power User, who’s struggling to adopt, who needs onboarding. |
| /executive | Monthly or quarterly reports up the chain. Pre-shaped for execs with hero KPIs and trend lines. |
A note on benchmarks
You’ll see ranges throughout the help center labeled “Strong / Fair / Needs attention.” These reflect our defaults and what we see across the orgs running Insights. They are not industry benchmarks — every team’s context matters too much — so treat the ranges as a starting frame, not a verdict.