Getting Started with GitKraken Insights
Last updated: March 2026
GitKraken Insights turns raw Git data into clear, useful metrics for developers and leaders. GitKraken Insights 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
DORA Metrics
Deploy frequency, change lead time, mean time to recover, and defect rate.
Pull Request Metrics
Cycle time, review count, open time, PR size, and code review hours.
AI Impact Metrics
Prompt acceptance rate, duplicated code, code rework, and active users.
Code Quality Metrics
Bug work percent, documentation and test percent, and code change rate.
Velocity Metrics
Commit count and estimated coding hours.
Dashboard Management
Configure filters, group views, and chart display options.
Metric Settings
Adjust thresholds, targets, and metric calculation parameters.
FAQ
Common questions about data, accuracy, access, and configuration.
Plan: GitKraken Insights (available by request)
Platform: Browser only via gitkraken.dev
Role: Lead, Admin, or Owner (for access). The User role does not grant access to GitKraken Insights but tells Insights to begin tracking that user for metrics.
Integrations: GitHub, GitLab, Bitbucket, Azure DevOps, Jira Cloud
AI providers: 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).
1. 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.

2. Confirm your profile details
After connecting repositories, confirm your personal details:
- First and last name
- Time zone
- Job role

3. Monitor data import progress
Once setup is complete, GitKraken Insights will begin importing your repository data.
- Expect past month’s activity to appear 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 1 — CSS-Only Enhancement
Approach: Added a <style> block at the top of the Markdown file. All content remains in standard Markdown. CSS targets the HTML elements that WordPress generates from Markdown rendering.
What this tests: Whether CSS-only changes inside the .md file, processed through Git It Write, can meaningfully improve the visual presentation without changing the content structure.
Limitations: No control over the WordPress page template, header, footer, or sidebar. CSS can only style what’s inside the post content area. Three-column layout, sticky TOC, and modal search are not possible with this approach. Breadcrumbs and card navigation require inline HTML additions.
Maintenance: Low — CSS block at the top of each file, content stays as Markdown. Could extract shared CSS to a WordPress custom CSS area to avoid duplication across files.