Terraform vs Pulumi vs CDK in 2026: The IaC Comparison

Infrastructure as Code has consolidated around several options. The 2023-2026 period has seen substantial dynamics — HashiCorp’s BSL relicensing of Terraform and the OpenTofu fork, the IBM acquisition of HashiCorp, plus the broader ecosystem evolution.

I want to walk through where the IaC landscape actually sits in 2026.

Terraform / OpenTofu#

Terraform (HashiCorp, now IBM) remains the most-widely-deployed IaC tool. The 2023 BSL relicensing produced the OpenTofu fork under Linux Foundation governance. By 2026:

• Terraform continues commercial development with substantial enterprise customer base.
• OpenTofu has the open-source community trajectory.
• Most enterprises continue with Terraform but increasingly evaluate OpenTofu.

Strengths:

• Mature provider ecosystem.
• Strong multi-cloud support.
• Substantial enterprise tooling.

Pulumi#

Pulumi offers programming-language-based IaC (TypeScript, Python, Go, C#, Java):

Strengths:

• Programming language familiarity.
• Strong testing patterns.
• Cross-cloud abstractions.

Trade-offs:

• Smaller ecosystem than Terraform.
• Programming-language IaC has trade-offs (state management complexity).

AWS CDK#

AWS CDK (Cloud Development Kit) is AWS’s native programming-language-based IaC:

Strengths:

• Tight AWS integration.
• Programming language patterns.

Trade-offs:

• AWS-only (CDK for Terraform extends but is less mature).
• Generates CloudFormation underneath.

Cloud-provider-native alternatives#

AWS CloudFormation — direct AWS.

Azure Bicep — Microsoft’s modern IaC.

Google Cloud Deployment Manager / Config Connector.

The cloud-native options work best when committed to a single cloud.

The choice framework#

For most production deployments in 2026:

Pick Terraform / OpenTofu if you want the largest ecosystem and team familiarity.

Pick Pulumi if your team prefers programming-language IaC.

Pick CDK if you’re substantially AWS-anchored.

Pick cloud-native if you’re committed to a single cloud and want native integration.

What’s coming in 2026 and 2027#

Three things to watch:

OpenTofu trajectory continues to evolve.

AI-augmented IaC for code generation and review.

Crossplane and Kubernetes-native IaC patterns continue to mature.

Where pdpspectra fits#

Our DevOps practice uses Terraform/OpenTofu as the primary IaC across most engagements.

Related reading: the Kubernetes production patterns post, the platform engineering post, and the GitOps post.

---

IaC choice depends on team and context. Talk to our team about your platform.