Terraform’s biggest competitor just made a move that could redefine infrastructure-as-code in 2026.
Pulumi now runs Terraform and HCL natively—better than HashiCorp does. That’s not a migration tool, not a compatibility shim, but full native execution through the Pulumi engine, plus Terraform state hosted in Pulumi Cloud and financial credits to help teams exit existing HashiCorp contracts.
In this episode of the Platform Engineering Playbook Daily Podcast, we break down why this announcement is one of the most important platform engineering stories of the year—and what it actually means for SREs, platform teams, and infrastructure leaders.
We cover:
- Why Pulumi supporting Terraform is not cooperation, but displacement
- How native HCL execution inside the Pulumi engine actually works
- What “polyglot infrastructure” means in practice for platform teams
- Pulumi Cloud as a Terraform Cloud replacement (state, RBAC, policy, AI)
- The real risks: compatibility gaps, lock-in concerns, and beta limitations
- A practical framework for deciding whether your organization should care
We also cover today’s top platform engineering headlines:
- How AI is shifting SRE from reactive firefighting to failure prevention
- Cloudflare’s observability redesign for large-scale configuration management
- RunPod’s unlikely rise to $120M ARR
- CoreWeave’s infrastructure challenges and why execution matters more than hype
If you’re managing Terraform at scale, evaluating OpenTofu, building an internal developer platform, or navigating the post–HashiCorp license-change landscape, this episode will directly impact decisions you’ll be making over the next 6–12 months.
Subscribe for daily platform engineering analysis, deep dives, and practical insights you can actually apply.
Links and sources discussed are in the show notes.
