Infrastructure Drift Count Calculator
Work out infrastructure drift count instantly with clear inputs, formula shown and shareable results.
About Infrastructure Drift Count Calculator
Drift is the gap between declared and actual infrastructure, and it accumulates at the rate of manual change multiplied by the reconciliation interval. Once a meaningful share of resources has drifted, the IaC repository stops being a reliable description of production, which means disaster recovery from code no longer works — the real cost of drift.
Formula
Drift accumulation
drift rate = drifted / managed; drift per cycle = manual changes per week x interval in weeks
Worked example
With the default values below, Infrastructure Drift Count Calculator returns Share of resources drifted of 4.00%. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Resources under IaC managementminimum 1
- 2,400
- Resources showing driftminimum 0
- 96
- Manual changes per weekminimum 0
- 12
- Reconciliation intervalminimum 0.1 days
- 7 days
Results
- Share of resources drifted
- 4.00%
- Drift accumulated between reconciliations
- 12.0
- Manual changes per year
- 624
- Assessment
- Moderate drift - investigate the sources of manual change
Step by step
- 1Values used
- 2Drift accumulation
- 3Share of resources drifted= 4.00
- 4Drift accumulated between reconciliations= 12.0
- 5Manual changes per year= 624
- 6Assessment= Moderate drift - investigate the sources of manual change
Assumptions and limits
- The result is derived only from the 4 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
- Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
How is drift eliminated?
Remove human write access to production and require all changes through the pipeline. Detection without prevention just produces a recurring report nobody acts on.
Should drift be auto-corrected?
Continuous reconciliation is ideal for stateless resources. Be careful with anything holding data, where reverting a manual change could destroy it.
Related Calculators
You might also need
- Partition Count CalculatorAlso in DevOps, SRE & Performance
- IaC Resource Count CalculatorAlso in DevOps, SRE & Performance
- Worker Process Count CalculatorAlso in DevOps, SRE & Performance
- Server Count For Load CalculatorAlso in DevOps, SRE & Performance
- Apdex Score CalculatorAlso in DevOps, SRE & Performance
- Artifact Retention CalculatorAlso in DevOps, SRE & Performance
