

Get the report

We asked hundreds of professionals how they use Infrastructure-as-Code
Use of IaC (such as Terraform, Pulumi, and OpenTofu) is becoming a de facto standard. This report identifies the drivers, common approaches, and outcomes behind its use.
What benefits are most often achieved by using IaC?
How advanced teams are in their IaC journey?
What are the main challenges of cloud management?
How do teams manage cloud governance?
68%
of respondents now operate across multiple clouds
89%
of respondents have adopted IaC, but only 6% have complete coverage
65%
of respondents report cloud complexity increasing over the last two years
2025 themes • 2025 themes • 2025 themes • 2025 themes • 2025 themes • 2025 themes • 2025 themes • 2025 themes • 2025 themes • 2025 themes • 2025 themes • 2025 themes •
Terraform’s dominance is eroding and under threat
The start of a potential changing of the guard in IaC tools is here, even as Terraform retains market share. The majority of IaC users in the survey still leverage Terraform, but cracks in that dominance are appearing.
IaC framework popularity
.png)
Changes in the difficulty of cloud management
.png)
Cloud management is (still) getting more complex
As many as 65% of respondents report cloud complexity over the last two years is trending up. Another 27% feel it’s still just as difficult as it was two years ago.
IaC maturity is lagging despite clear benefits
Cloud engineers recognize IaC’s value, and find that the benefits they expect from using IaC are being realized, but only 6% of respondents have reached full cloud codification.
.png)
Top IaC benefits realized

Consistency (ensuring environments don’t drift)

Platform reliability and stability

Speed of deployment (faster provisioning)
Top IaC adoption hurdles

Lack of knowledgeable engineering resources

Tooling fragmentation, complexity, and/or cost

Lack of IaC coverage (for existing and legacy resources)
Average time to remediate drift

Drift management is a rising concern
Drift emerged as a hot topic in 2025, after being relatively underemphasized in 2024. Today, less than one-third of organizations continuously monitor drift; the rest are largely reactive, addressing drift only when it causes a problem.
Automation is becoming the norm in CI/CD pipelines
In the face of rising complexity, manual ways of working remains a problem. This has led to a shift in how practitioners work, and especially in how they approach new infrastructure deployment. Unsurprisingly, automation-first pipelines have become the gold standard.
Infrastructure deployment methods
.png)
AI usage for managing cloud infrastructure
.png)
AI adoption is gradually accelerating
Though not yet ubiquitous, AI is making inroads into cloud infrastructure management. And even in early adoption phases, cloud practitioners largely recognize the potential AI holds. Those investing early will be poised to gain a competitive edge.
But what’s next? In 2026, we might:
See more and new approaches to taming cloud complexity (and perhaps even more cloud consolidation, or more automation as a result)
Witness Terraform’s continued decline in market share, but expect it will still hold as the #1 IaC solution, especially among enterprises
Watch immutable infrastructure ideals skyrocket, as data indicates practitioners are —now more than ever— aware of the inefficiency drift causes
See automation and AI assistance compensating for the human IaC skills gap (imagine AI that flags non-compliant IaC changes before they deploy)