Getting Started with GitKraken Insights
Last updated: March 2026
GitKraken Insights turns raw Git data into clear, useful metrics for developers and leaders. It pulls code activity, pull requests, issues, and CI/CD results into a single view that fits directly into existing workflows. Instead of surface-level stats, GitKraken Insights shows how work connects to team goals and points out ways to improve flow and productivity.
Explore GitKraken Insights
Deploy Frequency, Change Lead Time, Mean Time to Repair, and Defect Rate.
Cycle Time, First Response Time, Open Time, PR Size, and review activity.
Prompt Acceptance Rate, Duplicated Code, Code Rework, and AI usage.
Bug Work Percent, Documentation and Test Percent, and Code Change Rate.
Commit Count and Estimated Coding Hours for delivery consistency.
Configure filters, layouts, and dashboard views for your team.
Customize thresholds, date ranges, and metric calculation settings.
Common questions about setup, data sources, metrics, and troubleshooting.
Requirements
GitKraken Insights (available by request)
Lead, Admin, or Owner
GitHub, GitLab, Bitbucket, Azure DevOps, Jira Cloud
Claude Code, Cursor, GitHub Copilot (optional)

Request Access
GitKraken Insights is available by request only. To get started,
request a guided tour.
A member of the GitKraken team will contact you right away to walk you through GitKraken Insights and explain how to enable access for your organization.
Note: GitKraken Insights is a standalone product. Contact GitKraken to get started.
Connecting Your Data
Once your access is approved, you can connect GitKraken Insights to your repositories and configure settings for your organization. Currently, Insights supports connections with GitHub, GitLab, Bitbucket, Azure DevOps, and Jira Cloud.
In addition, you can connect AI providers to enable AI Impact insights (like Duplicated Code, Prompt Acceptance Rate, and more).
Import Your Repositories
-
In GitKraken.dev, go to Insights > Data Connection.
-
Click to connect with GitHub, GitLab, Azure DevOps, Claude Code, Cursor, GitHub Copilot, Bitbucket, or Jira Cloud.
-
Authorize GitKraken Insights to connect with GitHub.
-
Select which repositories to track. Use the filter option at the top of the page to quickly narrow down the list.



Avoiding GitHub API Rate Limits
If you’re importing a large number of repositories, depending on size and commit history, you may encounter GitHub’s hourly API rate limits. This can temporarily throttle other GitHub services used by your organization.
To avoid this, additional members of your organization can connect to GitKraken Insights using a Lead role. When multiple people are connected, the app distributes processing across their GitHub tokens to help avoid throttling.
After the initial import is complete, rate limit issues are unlikely to recur.
Connect an AI Provider (Optional)
As of February 2026, GitKraken Insights only supports connections with Claude Code, Cursor and GitHub Copilot to enable AI insights.
To enable AI Impact insights, connect your preferred AI provider:
-
In GitKraken.dev, go to Insights > Data Connection.
-
Click to
Managewith Claude Code, Cursor or GitHub Copilot. -
In the new window, select the AI provider you wish to connect with and enter the provider Token.
-
Click Connect AI Provider to finish the connection.

Confirm Your Profile Details
After connecting repositories, confirm your personal details:
- First and last name
- Time zone
- Job role

Monitor Data Import Progress
Once setup is complete, GitKraken Insights will begin importing your repository data.
- Past month’s activity appears within a few hours.
- Full year’s activity is usually ready within one to two days.
- Track import progress anytime from the Dashboard tab.

Exploration Notes: Version 3 — Enhanced HTML/CSS
Approach: Builds on V2’s HTML/CSS card layout with additional visual polish and native HTML5 collapsible sections (<details>/<summary>). Originally included embedded JavaScript for a sticky TOC, search/filter, progress bar, and back-to-top button.
Key finding — JS is stripped: WordPress strips inline <script> tags from post content imported via Git It Write. All JS-dependent features (TOC, search, progress bar, back-to-top) were non-functional. This version has been updated to use only CSS and native HTML — the collapsible section now uses <details>/<summary> which works without JS.
What this proves: The ceiling for the Git It Write + Parsedown approach is HTML + CSS only. No JavaScript. Interactivity is limited to what native HTML elements provide (details/summary, anchor links, CSS hover states). Features like search/filter, dynamic TOC, or scroll-tracking require either a WP plugin, a theme customization, or a different platform entirely.
Features over V2:
- Native collapsible sections — the API Rate Limits warning uses
<details>/<summary>(click to expand, no JS required) - Enhanced card hover effects — teal glow, lift animation on card hover
- Refined typography and spacing — tighter visual hierarchy
What was removed (non-functional in WP): Sticky TOC sidebar, reading progress bar, card search/filter, smooth scroll navigation, back-to-top button — all required JavaScript that WordPress strips from post content.
Implications for platform decision: If interactive features (search, TOC, scroll tracking) are required, they cannot be delivered through the current Git It Write + WordPress pipeline without server-side changes. A purpose-built docs platform (Starlight, Mintlify) or a headless WP approach would be needed.