Infrastructure Has a New Interface
For a decade, infrastructure as code meant writing declarative configuration files — HCL for Terraform, YAML for CloudFormation, TypeScript for Pulumi and AWS CDK. You described the desired state of your cloud resources in code, committed it to version control, and ran a plan/apply cycle to make it real.
In 2026, AI coding agents have inserted themselves into that workflow. Claude Code, Cursor, Codex, and Gemini CLI can generate Terraform modules, write Pulumi programs, scaffold Kubernetes manifests, and debug failed deployments. Pulumi shipped Neo, a purpose-built infrastructure agent that takes natural language requests and autonomously plans and executes infrastructure changes. AI agents already drive 20% of all operations on Pulumi's platform [1] — up from virtually zero a year ago.
The IaC market has reached $2.1 billion with a 28.2% CAGR. [2] But the shift isn't just about market size — it's about who is writing the infrastructure code. The answer, increasingly, is agents. And that changes the risk profile of every deployment.
The 2026 Tool Landscape
The IaC ecosystem has consolidated around a few major players, each with a different relationship to AI agents:
Terraform and OpenTofu
Terraform remains the most widely deployed IaC tool, with HCL as its configuration language. HashiCorp is positioning HCP Terraform as the governance and control plane for AI-driven infrastructure [3] — arguing that as agents write more configuration, the critical challenge shifts from authoring to verifying and safely executing it. Policy enforcement, state management, and approval workflows become the value layer.
OpenTofu, the CNCF-governed fork created after HashiCorp's license change, offers a drop-in Terraform replacement for teams that need vendor-neutral, open-source IaC. For agent workflows, both Terraform and OpenTofu work identically — agents generate HCL, and the plan/apply cycle remains the same.
Pulumi
Pulumi uses general-purpose programming languages — TypeScript, Python, Go, C#, Java — instead of a domain-specific language. This gives it a structural advantage for AI-agent workflows: coding agents like Claude Code and Cursor already understand TypeScript and Python. No IaC-specific tooling to bolt on. The agent writes infrastructure code the same way it writes application code.
Pulumi Neo takes this further. It's a purpose-built infrastructure agent that can reason over deployed infrastructure, generate or modify IaC, run previews, apply policy-as-code, operate within the initiating user's RBAC permissions, and create pull requests for human review. Neo is available in the Pulumi CLI, in GitHub (mention on PRs to investigate failures), and in the Pulumi Cloud console. One customer migrated 500 Terraform workspaces to Pulumi in an hour using Neo.