Change failure rate, measured properly.
Type your deploy numbers in. The needle below moves to your CFR, plots your team against the 2025 DORA percentile distribution DORA 2024 Report2024, and prices the annual engineering burn in dollars. Zero account. Zero demo. Math runs client-side.
Where your team plots vs DORA cohort
CFR (y) by deploys per week (x). Elite teams sit bottom-right: high throughput, low failure.
Would a DORA vendor pay back at this CFR?
Assumes a 40% CFR reduction (the published Sleuth median, scaled). Quote-only vendors do not display a per-seat rate.
Why this calculator exists
Every SERP competitor ships a printed formula and a static table. Sleuth, LinearB, Faros, DX and Jellyfish all maintain CFR landing pages but none let a VP Eng paste their own deploy counts in and walk out with a defensible board number in 90 seconds. That gap is what this site fills.
The math is the standard DORA definition: failed deploys divided by total deploys over a rolling window DORA Four Keys2024 Google Cloud CFR Guide2024. The default exclusions (fix-only forward-fixes, externally caused incidents) follow DORA guidance and the operational consensus across the four vendors above; both are toggleable.
What the gauge tells you
The semicircular dial maps your CFR onto the 2025 DORA percentile bands. The mint sliver at the left is the sub-2% region only the top 16.7% of surveyed teams reach DORA 2024 Report2024. The sulfur band covers the broad middle. The long graphite tail past 15% is where most teams actually sit, despite the marketing.
Below the dial, the dollar-burn ticker translates your CFR into an annual engineering cost using your MTTR, dev count, and blended FTE rate. Default $180,000 FTE is a defensible US Series-C blended anchor; override it to your number. The customer-impact churn estimate uses a $7,500 per customer-facing failure mid-anchor (see /methodology for derivation).
What about the four DORA keys together?
CFR is half of the DORA stability pair (MTTR is the other half) DORA Four Keys2024. The throughput pair is deployment frequency and lead time for changes. Looking at CFR in isolation is the most common DORA mistake; the 2D scatter below the calculator shows why (high-DF teams sustain low CFR through small batches and fast rollback, not through deploying less).
For the framework explainers, see /dora. For deeper cuts (by team size, industry, deploy frequency), see /benchmarks/2025-dora-report.