gitdailies.com

What It Is

GitDailies is a GitHub engineering metrics tool from Norway-based Lysning Digital AS, positioned as “Engineering Metrics for GitHub.” It is installed into an organization account via a GitHub App and reads existing GitHub activity to automatically generate PR metrics, DORA metrics, daily reports, and alerts—without requiring teams to change code, add manual data entry, or alter their workflow. A case study on the site shows MongoDB using it to alert on PR review SLAs and stale PRs, with some teams seeing reduced review times.

Core Features and Integrations

Its core capabilities focus on PR flow efficiency: teams can set time thresholds for PR review, PR age, PR inactivity, and more, with rules configurable by team, repository, and label. Alerts can be sent to Slack, Email, and Telegram, and Slack @mentions can be directed to the responsible person. On the metrics side, it supports aggregated views of PR metrics and DORA metrics by time period, team, repository, and PR label. Pro/Max include the full DORA set, including Deploy Rate, Lead Time for Change, Change Failure Rate, and Mean Time to Restore. It also provides daily team activity summaries and personal daily reports showing opened/closed PRs, commits, reviews, pending items, and triggered alerts. Integrations include GitHub Marketplace, Slack App, Telegram Bot, Metrics API, Grafana, Kibana, as well as commit-linking scenarios with Jira, Trello, Asana, Kitemaker, and others.

Pricing and Documentation

Pricing follows a freemium plus subscription model. Community is free but limited to 50 PRs/month, 2 repositories, 7 days of history, and 2 alert rules. Pro 250 is $49/month, or $41/month billed annually, and is aimed at small to mid-sized teams. Max 1000 is $299/month, or $249/month billed annually, and unlocks Metrics API, multiple GitHub organizations, 18 months of history, Live support, audit exports, and more. The documentation structure is fairly complete, covering installation, permissions, metrics, reports, projects, alerts, Expression Builder, Slack, API, and Webhooks. The API can be used for internal dashboards and third-party panels, but access to the OpenAPI specification and credentials requires contacting support.

Pros, Cons, and Who It’s For

The advantages are lightweight deployment, automatic collection around GitHub activity, granular alerting, and a clear statement that it does not clone repositories or read/store source code, making it suitable for engineering organizations with strong security-boundary requirements. The downsides are that the available materials do not show support for GitLab/Bitbucket, nor is there self-hosting information; API and enterprise-level capabilities are concentrated in higher-tier plans, and the free plan is clearly limited. It is especially suitable for teams using GitHub that want to shorten PR review cycles, establish a DORA metrics system, evaluate the impact of GitHub Copilot, or build engineering productivity dashboards.

Access from China

The official materials do not provide information on access from mainland China, payment methods, or local compliance, so china_access can only be assessed as unknown. Since it depends on ecosystems such as GitHub, Slack, Telegram, Grafana/Kibana, domestic teams will still need to evaluate network connectivity, organizational GitHub access policies, and overseas SaaS procurement processes in actual use. Comparable engineering productivity tools include LinearB, Swarmia, Athenian, Haystack, Jellyfish, and DX.