DORA Metrics
16 minutes reading time

Top DORA Metrics Tools: The Ultimate Guide to Making the Right Choice (2026)

DORA metrics tools list

Axify, LinearB, and Swarmia are our top three picks for DORA metrics tools.

After we share our framework for evaluating tools’ software delivery metrics, developer friendliness, and integrations, we’ll analyze the top contenders. Feel free to use it if you’re doing your own shortlist.

Here's a sneak peek:

ToolBest forDORA metrics covered (4 or 5)Tracks AI impact (yes/no)Starting price
AxifyDORA metrics and AI impact in one dashboard4Yes$29/active contributor/month, billed annually
LinearBPull-request policies across repositories4Yes$29/user/month, billed annually (GitHub Cloud only)
SwarmiaWorking agreements and delivery retrospectives4YesFree for companies with up to 9 developers
JellyfishEngineering allocation and financial reporting4YesCustom quote
DXDeveloper surveys alongside delivery data4YesCustom quote
SleuthDeployment-focused delivery reviews4NoCustom quote
AllstacksDelivery deadlines and capacity forecasts4Yes$400/contributor/year
Harness (SEI)Reporting across teams and toolchains4YesCustom quote
PlandekSprint commitments and initiative tracking4Yes$25/contributor/month
GitLabTeams using GitLab repositories and pipelines4YesCustom quote for Ultimate
DatadogTeams monitoring production in Datadog4Yes - PreviewCustom quote
Faros (formerly Faros AI)AI engineering spending across development tools5YesCustom quote
Four KeysReference implementation for self-hosted reporting4NoFree software; hosting costs extra
Apache DevLakeMaintained, self-hosted DORA reporting4Yes - beta releasesFree software; hosting costs extra

Disclaimer: Axify publishes this list and includes its own product.

What Are DORA Metrics?

DevOps Research and Assessment (DORA) metrics are performance indicators for software development and operations teams. They measure software delivery throughput and instability using five indicators that we’ll discuss below.

  • Throughput describes how quickly a team delivers code and changes and recovers from failed deployments. Higher throughput means the system can push more changes to production. It’s tracked through three metrics: lead time for changes, deployment frequency, and failed deployment recovery time.
  • Instability measures how well deployments go. When they go well, teams can confidently ship more code and code changes with fewer post-deployment issues. It’s tracked through two metrics: change fail rate and rework rate.

Pro tip: You can learn more about how to use them to measure and improve your performance in our complete DORA metrics guide.

Axify DORA metrics dashboard showing deployment frequency, lead time, change failure rate and recovery time with performance levels.

1. Deployment Frequency

Deployment frequency measures how often your team deploys code to production over a given period.

Pro tip: Axify detects deployments from multiple sources, so you can track deployments even when teams use different tools or workflows.

Axify deployment frequency chart showing weekly deployments rising from April to July.

2. Lead Time for Changes

Lead time for changes measures the average time between the first commit made in the development environment and when that change is successfully running in production.

Axify lead time for changes split into coding, pickup, review and deployment time.

3. Change Failure Rate

Change failure rate measures the percentage of deployments that cause production failures requiring immediate intervention, such as a hotfix, rollback, or patch.

Pro tip: Axify can measure this because it associates an incident with its last deployment.

Axify change failure rate chart showing 6 failed deployments out of 126, a 4.8% failure rate.

4. Failed Deployment Recovery Time

Failed deployment recovery time measures how long your team takes to restore service after a failed production deployment. It's formerly known as mean time to recovery.

Axify list of resolved incidents by service with their recovery times and the average.

5. Rework Rate

Deployment rework rate, DORA’s fifth metric, measures the percentage of deployments that are unplanned responses to production incidents.

What Changed in DORA Metrics in 2025 and 2026

DORA replaced its elite/high/medium/low tiers with seven team archetypes in 2025, then published AI ROI guidance and paused its annual survey in 2026.

The ROI of AI-assisted Software Development report explains how to estimate AI’s costs and savings in your development process.

But in September 2026, DORA confirmed there would be no annual survey or State of AI-assisted Software Development report that year. So the 2025 data remains the latest annual benchmark from DORA research.

So, when choosing a tool, check that it doesn’t score your team performance against the old tier tables.

How We Chose These Tools

We chose these tools by checking each provider’s website and documentation against the criteria in the section below. Our team applied the same checks to every tool, including Axify.

Here’s what we looked at:

  • AI assistant adoption and delivery impact
  • DORA metrics coverage and calculation methods
  • Setup, usability, and developer experience
  • CI/CD integration and other supported connections
  • Data accuracy, security, and dashboard performance
  • Support and community resources

How to Pick a DORA Metrics Tool

Getting accurate DORA metrics can be difficult when data is inconsistent, teams define metrics differently, or integrations miss deployments and incidents. These problems can skew your dashboard and make it harder to identify delays or recurring failures.

Picking the right tool solves the majority of those problems. We’ve used our experience at Axify to discuss the most important criteria that will help you make an informed choice.

Pro tip: We’ll show you how we use these criteria in the next section, where we compare 14 DORA metrics tools.

1. AI/Next-Gen Metrics

AI and automation change how code is written, reviewed, and shipped, but DORA metrics by themselves don’t show whether those tools help your team.

Besides, AI use is already widespread. DORA’s 2025 report found that 90% of respondents used AI at work, so your team is most likely using it too.

That means you need a DORA metrics tool that also tracks AI impact.

Here are the key questions to guide your evaluation:

  • Does it track AI adoption? Check whether you can see usage of GitHub Copilot, Cursor, and Claude Code by team.
  • Can it correlate AI usage with delivery performance? The tool should show how AI adoption affects DORA metrics for the same teams and reporting periods (while considering other factors that may have influenced the results, of course). You should also be able to review changes before and after an AI rollout.
  • Can it help explain changes in the metrics? For example, some DORA metrics tools let you ask questions such as “Why did Payments lead time go up?” and follow up using the team’s delivery data. Their MCPs also help you find answers to those questions right from the agents you’re using.
  • Can it help you make decisions? Your AI dashboard tool should allow you to make informed decisions based on the insights you discover.

2. Metrics Measurement

A good tool should cover the core DORA metrics and let you check how each number was calculated. Here are some questions to help assess a tool's metrics measurement capabilities:

  • Does the tool cover the four core DORA metrics? Check how it defines and calculates deployment frequency, lead time for changes, change failure rate, and failed deployment recovery time.
  • How are the metrics visualized and reported? Look for dashboards that show trends clearly and let you switch between reporting periods.
  • Does the tool provide organization-wide insights? You should be able to view metrics across your engineering organization, then filter by team or project.
  • Can we trust the data’s accuracy? Check whether you can drill into individual deployments and incidents, review historical records, and validate the calculations.

3. Developer Friendliness

A developer-friendly tool ensures your team adopts and uses it effectively. Consider the following questions:

  • Is the tool easy to use and understand? Developers should be able to find a delayed pull request or deployment without extensive training.
  • Does it provide useful detail without overwhelming users? Look for clear summaries with the option to inspect the records behind each metric.
  • How does the tool support continuous improvement? You should be able to track whether process changes are followed by shorter review waits, fewer failed deployments, or faster recovery.

4. Integrations

The tool should offer flexible integrations to fit seamlessly into your existing workflows. In Stack Overflow’s 2025 Developer Survey, 54% of respondents used six or more tools to do their work. That’s from 27,378 recorded responses that excluded operating systems and browsers from the tool count.

However, you want to avoid jumping from one tool to another, to make sure context stays the same and to avoid attention loss.

A DORA metrics dashboard can help, if you ask the right things:

  • Does it integrate with our existing tools and platforms? Check compatibility with your repositories, CI/CD pipeline, project management tools, incident sources, and other DevOps tools. It should handle deployments and incidents from multiple systems.
  • How easy is it to set up and maintain integrations? Check the initial setup steps and how much ongoing maintenance your team will handle.
  • How customizable is it to fit your workflow? Look for custom dashboards and filters by team or repository.
  • Can it alert you in Slack, Teams, or email? Check which channels and alert types are currently available on your plan, along with how you choose recipients.

5. Data Reliability and Performance

Reliable syncing matters, and so does how the tool handles your data. In Stack Overflow’s 2025 survey, security or privacy concerns ranked No. 1 among reasons respondents would reject a technology. That question received 34,188 responses.

Here are key issues to evaluate:

  • How reliable is the data? Check how regularly it syncs and whether you can see when the data was last updated.
  • How long does it take to synchronize for the first time? Ask how much historical data is imported and how long the initial sync takes for repositories of your size.
  • How does the tool protect our data? Check whether it reads or stores source code, and review access permissions and retention policies. Look for tools that collect only the metadata needed to calculate metrics.
  • Does the tool clone our repositories? Some tools copy entire repositories to calculate metrics, while others pull only the metadata for each pull request, such as timestamps, status, and authors. If your codebase contains sensitive or proprietary code, ask why a tool needs access to all of it. Metrics like lead time or deployment frequency don’t require reading the code itself.

6. Support and Community

Reliable support can save your team time when an integration stops syncing, or a metric looks wrong. Here's what to look for:

  • What support options are available? Check the available channels, support hours, and response times for your plan.
  • Are there comprehensive resources available? Look for documentation, tutorials, and any user community where you can find answers to setup or reporting questions.
  • What onboarding help is included? Check whether someone will help you connect your tools, configure dashboards, and verify the first results.

The Best DORA Metrics Tools

The best DORA metrics tools include Axify, LinearB, Swarmia, and Jellyfish. Your choice depends on your existing tools and whether you need AI usage data alongside deployment frequency and lead time.

Here are the options, with their key features, pricing, and the teams they suit.

1. Axify

Best for: Engineering leaders who want DORA metrics and AI impact in one dashboard.

Key features:

Pricing: Pro costs $29 per active contributor/month, billed annually. Enterprise pricing is available on request. There’s no free plan, but both plans include a 14-day free trial with no credit card required.

Axify brings your Git, deployment, incident, and AI-tool records together, so you can investigate slowdowns without rebuilding reports from separate systems. You can inspect the deployments behind a failure rate or find whether coding, pickup, review, or deployment accounts for a longer wait.

When AI usage rises, its Adoption and Impact feature shows whether the same teams see improvements in their DORA metrics, throughput, or time to production. Axify Intelligence recommends the next action based on those insights (allowing you to implement it directly from the dashboard), while its read-only MCP connection answers questions in Claude, ChatGPT, or Cursor using your existing permissions.

Axify Intelligence explaining why pull request cycle time went up, with pickup time as the main cause.

2. LinearB

Best for: Engineering teams standardizing pull-request policies across repositories.

Key features:

  • Four DORA metrics with coding-to-deployment phase breakdowns.
  • AI adoption, suggestion acceptance, and assisted-work comparisons.
  • Programmable review policies and pull-request routing rules.
  • Incident data from Jira or the Incident API for failure and recovery calculations.
  • Git metadata extracted through temporary shallow repository clones, which are deleted after processing.

Pricing: From $29/user/month, billed annually (Essentials plan, GitHub Cloud only).

LinearB connects repository, deployment, incident, and AI-tool data to report how engineering work moves from the first commit into production. Its workflow automation applies rules to reviews, labels, and handoffs, while the platform records changes in delivery timing over successive reporting periods. LinearB performs a temporary shallow clone to extract Git metadata, then deletes the cloned data after processing.

Deployment detection can use tags, pull requests, dedicated branches, or API events, so the configuration determines which activity counts as a production deployment. Incidents can arrive through Jira or the Incident API, which accepts records from other incident tools for change-failure and recovery calculations.

For a closer look at how LinearB compares on pricing and data access, see our LinearB alternatives guide.

3. Swarmia

Best for: Teams reviewing working agreements and recurring delivery delays during retrospectives.

Key features:

  • DORA metrics with team views and historical trends.
  • AI impact comparisons across review time and batch size.
  • Working agreements with Slack and Microsoft Teams notifications.
  • Developer surveys and investment-allocation reporting.
  • Custom reports, Swarmia AI, and an MCP interface.

Pricing: Free for companies with ≤9 developers.

Swarmia connects engineering-system records with developer feedback to describe how work moves through teams and where daily routines create delays. Its investment views categorize engineering effort. Meanwhile, its survey module records how developers experience the tools and processes behind those measurements.

The Productivity & AI Impact module contains DORA metrics, while AI comparisons examine cycle time, review duration, and batch size across different usage patterns. Current integrations extend beyond GitHub, Jira, and Linear to GitLab and Azure Boards, with Shortcut and GitHub Issues listed as beta.

If Swarmia’s team-level focus doesn’t match how you report, our Swarmia alternatives guide compares other options.

4. Jellyfish

Best for: Engineering leaders preparing allocation reviews with product and finance teams.

Key features:

  • DORA, SPACE, and AI metrics within engineering reporting.
  • AI adoption, token spending, and multi-tool impact analysis.
  • Developer surveys alongside operational engineering data.
  • Custom metrics and natural-language queries through Data Hub.
  • Investment allocation, software capitalization, and R&D reporting.

Pricing: Custom quote.

Jellyfish aggregates engineering activity from connected development systems and organizes that work by teams, initiatives, and categories of engineering investment. Its reporting includes the distribution of effort across planned work and maintenance, with separate financial capabilities for capitalization and R&D reporting requirements.

For AI evaluation, Jellyfish compares delivery records before and after adoption and examines differences in pull-request timing between assisted and unassisted work. Data Hub adds organization-specific metric definitions, dashboard filters, and queries, so reporting can use the dimensions maintained in the connected systems.

5. DX

Best for: Organizations collecting developer surveys alongside engineering-system measurements.

Key features:

  • DORA reporting through Data Cloud.
  • AI usage cohorts and before-and-after adoption comparisons.
  • Developer experience Snapshots and reported time savings.
  • Lifecycle analysis across refinement, coding, review, and deployment.
  • Custom SQL reports and configurable engineering dashboards.

Pricing: Custom quote.

DX is a developer intelligence platform that places operational engineering records alongside survey responses about developers’ experience of their working environment. Atlassian acquired DX in November 2025 following a deal announced at approximately $1 billion.

Its Data Cloud contains system activity. And Snapshots gather feedback that can explain why engineers report difficulty with a workflow despite apparently normal dashboard figures.

AI impact reports compare groups with different usage levels and can examine windows of up to 90 days before and after adoption. Time-saving estimates come from developer responses, while the lifecycle analysis uses work-tracking and repository records to separate different parts of the software delivery lifecycle.

Since the Atlassian acquisition, some teams are reviewing their options. Our DX alternatives guide compares them.

6. Sleuth

Best for: Teams organizing delivery reviews around production deployment events.

Key features:

  • Four DORA metrics with deployment-level drill-downs.
  • AI chart summaries, scorecards, and anomaly detection.
  • Configurable definitions for deployment failures.
  • Review templates for engineering meetings and sprint reviews.
  • Pull-request checks, notifications, and cross-tool automations.

Pricing: Custom quote.

Sleuth follows production deployment events and connects them with the code changes, development work, and operational signals associated with each deployment. Its integrations span repositories, CI/CD systems, issue trackers, application monitoring, and error tracking.

The lead-time calculation follows the first commit through actual deployment, and the wider timeline can include issue creation, rollbacks, and incidents. Review templates arrange charts around meeting agendas, while automation definitions cover individual actions or multi-step workflows and can be expressed in YAML.

7. Allstacks

Best for: Engineering managers responsible for initiative deadlines and capacity forecasts.

Key features:

  • DORA, Flow, and SPACE reporting.
  • AI usage, delivery-impact, and cost comparisons.
  • Historical delivery forecasts and scenario modeling.
  • Initiative risk and blocked-dependency analysis.
  • Configurable engineering metrics and investment-allocation views.

Pricing: From $400 per contributor per year.

Allstacks connects project, code, delivery, collaboration, and documentation systems, then organizes their historical records into what it calls a Context Graph. That model links a forecast or identified risk back to the work records used in its calculation, including activity across connected teams.

Its predictive analytics use previous delivery patterns to estimate completion dates, while initiative views identify blocked dependencies and changes in team progress. AI analysis compares usage cohorts against delivery timing, defect rates, and throughput, with configurable metrics available for more specific questions about connected projects.

To compare Allstacks’ forecasting and pricing with other platforms, see our Allstacks alternatives guide.

8. Harness (SEI)

Best for: Organizations standardizing measurement across several engineering hierarchies and toolchains.

Key features:

  • DORA dashboards by organizational group and team.
  • AI adoption, active sessions, and AI-attributed commit tracking.
  • AI-assisted and unassisted pull-request timing and throughput comparisons.
  • Deployment records and review-stage drill-downs.
  • Configurable measurement profiles and organizational trees for reporting scope.

Pricing: Custom quote.

Harness added Software Engineering Insights after acquiring Propelo. And its current documentation describes the offering under the AI DLC Insights name. The platform ingests records from source control, CI/CD, work-tracking, and incident systems.

DORA drill-downs expose the records behind deployment frequency, lead time, failed changes, and recovery. And there's also reporting available across the configured organizational hierarchy. The current AI Engineering Insights dashboard requires a local Harness AI DLC Agent on developer machines and activation through Harness Support.

9. Plandek

Best for: Delivery managers overseeing sprint commitments across several development systems.

Key features:

  • Four DORA metrics with organization and group views.
  • AI adoption, usage, and delivery-impact tracking.
  • DeliveryRadar forecasts and initiative risk analysis.
  • Dekka assistant for engineering-data questions.
  • Custom dashboards and API-based data connections.

Pricing: From $25 per contributor per month.

Plandek aggregates engineering records from systems such as Jira, Azure DevOps, GitHub, GitLab, and Bitbucket, with custom APIs accepting additional data. Its dashboards cover work moving through planning, development, and deployment. And reporting can be grouped around the teams or initiatives being reviewed.

AI reporting includes daily activity, license utilization, and use of multiple coding tools, alongside changes in the delivery records collected from connected systems. DORA views offer metric and repository drill-downs. And other reporting examines sprint commitments and the risks attached to work that has not yet finished.

10. GitLab

Best for: Organizations already managing repositories and deployment pipelines inside GitLab.

Key features:

  • Four DORA metrics in the Ultimate tier.
  • GitLab Duo adoption and development-trend analytics.
  • Value stream reporting and workflow-stage analysis.
  • Deployment records submitted through an API.
  • Integrated continuous integration, security scanning, and deployment management.

Pricing: Custom quote for Ultimate.

GitLab operates as a DevSecOps platform with repositories, merge requests, pipeline execution, security checks, and production deployment records in the same system. It is available through GitLab.com, Self-Managed, and Dedicated, and external deployment tools can submit the events used by its analytics through an API.

The platform measures lead time from merge to production and calculates failure and recovery metrics from incidents. Duo reports track AI usage alongside development and pipeline metrics, while AI features use GitLab Credits.

11. Datadog

Best for: Organizations already collecting application and production telemetry in Datadog.

Key features:

  • Four DORA metrics and deployment trend analysis.
  • AI Impact comparisons, currently in Preview.
  • Commit, review, merge, and deployment timing breakdowns.
  • Rollback detection and configurable hotfix rules.
  • Filters by team, service, repository, and environment.

Pricing: Custom quote. Contact Datadog for pricing.

Datadog is an observability and security platform whose delivery performance offering contains DORA reporting and a separate AI Impact analysis capability. Deployment events arrive through APM Deployment Tracking or the DORA API and CLI, with repository URLs and commit identifiers connecting them to Git metadata.

Its DORA views track delivery timing, deployments, and failures. AI Impact, currently in Preview, compares AI-assisted and non-assisted work across metrics including PR cycle time, throughput, change failure rate, and recovery time. Datadog identifies AI involvement using several signals, including commit metadata, integrations, PR labels, and customer-provided data. These signals are useful for comparison, but they don’t prove that AI caused a change in performance.

12. Faros AI

Best for: Enterprises examining AI engineering spending across multiple development systems.

Key features:

  • DORA reporting, including deployment rework rate.
  • AI adoption and usage-cohort comparisons.
  • Token spending associated with engineering activity.
  • MCP queries and generated engineering dashboards.
  • Metric breakdowns by team, repository, tool, or model.

Pricing: Custom quote.

Faros AI, now branded Faros, describes its current product as a Token Engineering Platform built around a shared model of engineering activity. It connects repositories, issue tracking, delivery systems, incidents, workforce information, and AI coding agents, then associates the records with teams and initiatives.

The engineering reports examine lead time, failure rates, rework, pull-request size, and review duration, with filters for the relevant repositories and AI tools. Usage cohorts distinguish different adoption patterns. Meanwhile, coding-agent and review-agent signals provide additional context about where AI appears in the development work.

13. Open-Source Options: Four Keys and Apache DevLake

Best for: Teams prepared to host and maintain their own DORA reporting.

Key features:

  • Configurable deployment and incident definitions in DevLake.
  • Grafana dashboards and DORA data troubleshooting.
  • Connectors and webhooks for engineering systems.
  • Docker Compose and Helm deployment options.

Four Keys was archived after its last update in January 2024, and its repository explicitly states that it is no longer maintained. It remains a reference implementation for collecting and transforming delivery events.

Apache DevLake is the maintained option, with ongoing releases and project-based DORA reporting. The adopting team handles hosting, integration configuration, credentials, upgrades, and ongoing maintenance.

How to Read DORA Metrics Together

You read DORA metrics together by correlating speed (deployment frequency, lead time for changes, and failed deployment recovery time) with stability (change failure rate and deployment rework rate).

Here are the four patterns to watch:

ThroughputInstabilityWhat to investigate
ImprovesDecreasesChanges reach production and failures are resolved faster, while fewer deployments cause failures or require unplanned fixes. Look at which practices may be helping, and keep monitoring the trend.
ImprovesIncreasesDelivery or recovery is faster, but more deployments cause failures or require unplanned fixes. Review recent incidents, testing, and deployment practices.
WorsensDecreasesDelivery or recovery is slower, but fewer deployments cause failures or require unplanned fixes. Investigate where work is waiting and whether any process changes contributed.
WorsensIncreasesDelivery or recovery is slower, while failures or unplanned fixes are increasing. Investigate delays and production incidents together.

Pro tip: Our DORA metrics dashboard guide explains how to display and review these measures together, so check it out.

DORA Metrics Measurement Challenges

You track DORA metrics for a reason, but the process can feel messy when the data isn’t clear or consistent. That confusion grows once different tools and workflows get involved. So, here are the main challenges you should keep in mind:

  • Deployment frequency: One challenge is relying on multiple sources of deployment data across different environments, such as different teams, tools, or automated systems. All this can make it challenging to get a unified view of all deployments. Also, tracking the production environment is harder for on-premise apps or mobile apps because their deployments differ from cloud systems.
  • Lead time for changes: The main challenge lies in standardizing the starting point, such as the first commit, and accounting for different Git workflows. Long-lived branches complicate tracking, while trunk-based development simplifies it.
  • Change failure rate: Determining what qualifies as a failure and accurately tracking these incidents can be complex, especially if you don't have a standardized incident management system. Also, it's challenging to capture all incidents because they have many different sources to account for. And another challenge is attributing the failure to the correct deployment or team.
  • Failed deployment recovery time: Accurately tracking recovery time can be complex due to incident severity and response efficiency variability. For accurate measurement, you need consistent incident reporting and management tools. Another challenge is having different incident sources to support.

How to Improve DORA Metrics

Improving your DORA metrics starts with stage-level visibility into review queues, deployment delays, and recovery steps. Our DORA implementation guide shows you how to connect your tools and track these metrics across your engineering org.

Look Beyond DORA Metrics

Once your DORA metrics are in place, you know how your team delivers. What you probably don’t know yet is whether your AI tools have changed that, and what to do about it. Most teams use AI at work now, so leadership keeps asking, and a deployment frequency chart can’t answer.

That’s where Axify comes in.

We correlate AI adoption with your delivery data, interpret what changed and why, and suggest actions your team can implement right away. You decide where to invest and which teams need support based on your own numbers. We keep working with you as your tools and processes change, so the recommendations match how your team works at that point.

If you’d like to see this with your own data, book a demo with Axify. We’ll go through your current setup and pick the first thing to tackle.

FAQs

What is the best DORA metrics tool?

Axify is our pick for engineering leaders tracking software delivery performance alongside AI adoption. Its value stream management views show where work waits. Axify Intelligence adds proactive guidance on which delays your team should investigate first.

Are there free DORA metrics tools?

Yes, Apache DevLake offers free, open-source DORA reporting. Your team handles hosting, maintenance, and project configuration to match your team structures. GitLab’s built-in DORA analytics require the paid Ultimate tier, so its Free plan doesn’t include them.

Can Jira track DORA metrics?

Jira can track deployment frequency and commit-to-production timing through connected development tools. You’ll need additional reporting for failure and recovery metrics. For full SDLC integration, check that your setup also connects production incidents with the relevant changes.

Which DORA tools track AI impact?

Axify, LinearB, Swarmia, Jellyfish, and DX track AI impact. Your AI Measurement Framework should compare usage with deployment frequency and lead time for the same teams. DX also collects development feedback through developer surveys to add context to those measurements.

Is there a 2026 DORA report?

Yes, DORA published an AI ROI report in 2026. It skipped the annual survey and State of AI-assisted Software Development report. The 2025 data remains the latest annual reference, while your own delivery history can inform custom benchmarks.