The AI landscape doesn't move in one direction — it lurches. Some techniques leap from experiment to table stakes in a single quarter; others stall against regulatory walls, technical ceilings, or organisational inertia that no amount of hype can dislodge. Knowing which is which is the hard part. The State of Play cuts through the noise with a rigorously maintained index of AI techniques across every major business domain — classified by maturity, evidenced by real-world adoption, and updated daily so you always know where you stand relative to the field. Stop guessing. Start knowing.
A daily newsletter distilling the past two weeks of movement in a domain or two — delivered to your inbox while the index updates in the background.
Each dot marks the weighted maturity of practices within a domain — hover for a brief summary, click for more detail
AI that monitors infrastructure configurations for drift from desired state and can automatically remediate deviations. Includes policy-as-code enforcement and drift alerting; distinct from change risk assessment which evaluates planned changes rather than detecting unplanned ones.
Configuration drift detection and remediation is a mature, proven practice with GA tooling from every major cloud vendor and a growing ecosystem of specialized platforms. The question for infrastructure teams is no longer whether to detect drift but how to remediate it safely and automatically at scale. Drift detection itself — comparing live resources against IaC definitions — reached commodity status by 2024 across AWS, Azure, GCP, Oracle, and Kubernetes. The frontier has shifted to AI-assisted remediation, policy-to-code workflows, and continuous governance that translate detected deviations directly into versioned fixes. Documented deployments show concrete ROI: reduced MTTR, six-figure annual savings, and significant cuts to cloud waste. Yet a persistent adoption paradox constrains the practice's impact. Surveys show only 6% of organisations achieve full cloud codification despite 89% claiming IaC adoption, and fewer than a third proactively monitor for misconfigurations. The core tension remains operational: ClickOps — manual console changes during incidents — continues because enforcing IaC discipline conflicts with incident-response speed. Tooling has outpaced organisational readiness, making culture and change management the binding constraint rather than technical capability.
The vendor ecosystem now treats drift remediation — not just detection — as a core platform capability. AWS's Managed Services Trusted Remediator shipped with 116 automated remediations and claims a 95% reduction in remediation time. CloudFormation's drift-aware change sets, independently validated in production, offer three-way comparisons between templates, prior state, and live resources, letting operators revert drift without rewriting templates. Firefly, env0, and Devonair have each released AI-assisted remediation features that translate policy violations into IaC code fixes across multi-cloud environments. Early June 2026 vendor announcements accelerate the shift: Scalr released drift detection for Terraform/OpenTofu with three remediation pathways (ignore, sync state, revert) and automatic pause-after-failed-runs safety controls; Gruntwork positioned drift detection as a monetized, core platform feature in Terragrunt 1.0 (signaling table-stakes status even for open-source-adjacent vendors); Remedio, a purpose-built autonomous remediation platform, launched with zero-disruption rollback and predictive impact preview. IBM/HashiCorp's HCP Terraform public preview integrates Infragraph knowledge graphs for unified drift management across multi-cloud deployments with real-time asset state tracking; Pulumi shipped Helm Chart v4 with enhanced drift remediation across all SDKs (TypeScript, Go, Python, .NET, Java, YAML). AWS DevOps Agent (GA March 2026) demonstrates autonomous security remediation with architecture claims of 75% MTTR reduction via topology-aware agents and Model Context Protocol integration. Firefly customer case studies document measurable outcomes: Comtech reports $180K in annual savings, Basis Technologies cut cloud waste by 83% through continuous governance.
Evidence from May-June 2026 confirms the core tension persists: detection is mature and widely deployed, but remediation gaps and organisational discipline remain unresolved. A Qualys analyst report (250+ enterprise survey, May 2026) identifies a critical bottleneck: 49.4% of organisations still rely on monitoring + manual response workflows rather than infrastructure-as-code-driven remediation, leaving organisations vulnerable to delayed response. In parallel, a separate survey of 250 security professionals across FinServ, Retail, Public Sector, Healthcare, and Critical National Infrastructure found that 97% of organisations experienced drift-related incidents in the past 12 months, yet remediation cycles average 8+ days, leaving organisations in exploitable exposure windows. Platform engineering practitioners articulate that the gap is no longer detection (which is universal and commodity) but safe remediation: teams can identify drift reliably but struggle to correct it without infrastructure ontology encoding resource relationships, policies, and ownership. A security-specific case (WAF configuration drift) documents 70% failure to block common attack patterns due to drift in rule modes, thresholds, and rule staleness—demonstrating that drift is not just an operational inconvenience but a security control failure in high-consequence systems. Drift detection coverage across IaC frameworks (Terraform, OpenTofu, CloudFormation, Kubernetes) has become a baseline procurement criterion, actively driving platform switching decisions. Academic research (ICDCA 2026 Best Paper Award, selected from 2,600 submissions) on AI-driven predictive drift detection signals the frontier shift: from reactive detection-then-remediation to predictive identification and prevention, combining machine learning with risk scoring and automated response mechanisms. However, operational research reveals real limitations: drift detection remains reactive by design, correction can be operationally disruptive, and immutable-infrastructure approaches show 90% reduction in drift-related incidents and MTTR compared to detection-based remediation—suggesting that for many organisations, detection alone is insufficient without fundamental architectural change.
Emerging operational patterns highlight new drift vectors. Particle41 consulting firm documents AI agents making direct infrastructure changes that bypass IaC pipelines, creating untracked drift (e.g., resource right-sizing creating IaC-reality divergence). Client case studies show one organisation reduced infrastructure audit time from 40 hours/quarter to 4 hours through enforced IaC gates for agent outputs; another caught security misconfiguration before agent deployment through continuous drift monitoring. Recovery and disaster-recovery testing surfaces detection gaps: NTCTech documented a quarterly recovery drill that exposed four months of silent drift (service endpoints changed via manual updates, certificate trust paths rotated, security policies tightened without runbook updates) — the backup was consistent but the recovery environment was not. Organisational adoption barriers remain despite mature tooling. Firefly's 2025 IaC Report found that fewer than a third of organisations proactively monitor and remediate misconfigurations, and only 6% have codified their full cloud footprint — despite near-universal claims of IaC adoption. Real-world deployment data from April–May 2026 confirms these constraints persist: a practitioner case study documents 47 drifted resources accumulating silently over 4 months across 3 AWS accounts from incident-response console changes; remediation consumed 3 engineers for 2 full days. A critical failure case (GitLab.com incident April 2026, root cause July 2023) shows how stale Terraform plans can execute against live production with catastrophic results (130+ minute site outage, 617 resources marked for destruction). The gap is not tooling but discipline: practitioners still resort to manual console changes during incidents because IaC enforcement introduces friction when speed matters most. A 2025 breach analysis (Secure.com) found that 55% of cloud breaches trace to drift/misconfiguration and 82% of configuration errors originate from manual changes — evidence that drift remains a primary breach driver even as detection maturity increases.
August 2026 evidence reinforces mature deployment and agentic infrastructure integration: Rutagon's consulting methodology embeds drift detection in enterprise change-control architecture via CODEOWNERS-based ownership routing, reducing manual triage cycles; Firefly's agentic infrastructure guidance positions drift remediation as essential control for AI agents writing infrastructure code, with autonomous pattern detection and policy-gated PRs becoming standard; and quantified prevention metrics show risk reduction from 15–30% baseline drift to under 2% with IaC enforcement (SCP + Atlantis). Product GA milestones (Quali Operate, Remedio Baseline at City of Phoenix with 70% configuration finding reduction and MTTR improvements from days to minutes) confirm autonomous remediation approaching production readiness at enterprise scale. The practice has arrived as good-practice; rolling it out is an organisational change management challenge, not a technology procurement one.
— Firefly CEO Eran Bibi describes autonomous drift remediation patterns: AI agents detect configuration drift, determine whether to codify or revert changes, and execute remediation with IaC as control plane for auditability and rollback.
— Remedio Baseline GA product deployment at City of Phoenix: 70% fewer configuration findings, MTTR reduction from days to minutes, autonomous drift remediation across Windows, Linux, cloud resources with zero-disruption rollback.
— DevOpsKit tutorial on Terraform drift prevention with quantified outcomes: without prevention 15-30% of resources drift within 30 days, with SCPs and Atlantis enforcement this drops to under 2%.
— Rutagon consulting firm deployed production drift detection automation with ownership routing via CODEOWNERS, safe/unsafe remediation policies, and staged rollout procedures for customers.
— Quali Operate GA product for Day 2 operations with native drift detection and auto-remediation capabilities, comparing live environments to IaC specs and routing remediation through approval workflows.
— Independent Perun Engineering analysis of production Spacelift failures including silent drift detection failures when cloud provider credentials expire mid-scan, revealing operational fragility in orchestrated drift workflows.
— Rack2Cloud critical assessment distinguishing security drift (authorized state becoming less secure) from configuration drift, revealing a fundamental practice limitation: detection tools can show perfect convergence while security posture decays silently.
— CISGuard defines three-level drift detection maturity: Level 1 periodic manual audits, Level 2 scheduled automation, Level 3 continuous monitoring; positions drift detection as foundational to compliance frameworks (PCI DSS, NIST 800-53, ISO 27001).