Pulumi Embraces Terraform and OpenTofu: A New Era for Infrastructure as Code

For years, the infrastructure as code (IaC) landscape has been dominated by a few key players, each with their own strengths and communities. Pulumi has consistently championed a modern, multi-language approach, empowering developers to use familiar programming languages like Python, TypeScript, Go, C#, and Java for their infrastructure. Our customers tell us they love the speed, security, and compliance benefits that come with this approach.

However, we also recognize a fundamental truth: many organizations have significant, long-standing investments in tools like Terraform. And, in the wake of recent changes and acquisitions impacting the IaC ecosystem, we’ve heard growing frustration from HashiCorp customers regarding rate increases, shifts in open-source philosophy, and unexpected changes to beloved tools like CDKTF.

Today, we’re incredibly excited to announce three major initiatives designed to empower these organizations, providing a clear path to a better, open-source-friendly, and modern IaC solution with Pulumi. We’re not just building a better tool; we’re building a more universal platform.

The TL;DR: More Choice, Less Friction

• Pulumi Cloud now manages Terraform/OpenTofu with full visibility, governance, and our infrastructure engineering AI agent, Neo.

• Pulumi IaC now speaks HCL natively, alongside general-purpose languages and YAML.

• Flexible financing to cover your costs until your HashiCorp contract ends, making the transition seamless.

Let’s dive into what this all means.

1. Terraform and OpenTofu in Pulumi Cloud: Your IaC Backend, Reimagined

Pulumi has always been two things: Pulumi IaC, our open-source, multi-language IaC technology, and Pulumi Cloud, our commercial platform for state management, visibility, AI, secrets, policy as code, and more. Think of it like Git (the tool) versus GitHub (the SaaS).

Historically, to benefit from Pulumi Cloud, you needed to use Pulumi IaC. But as we’ve scaled to thousands of customers, we’ve realized that the “how” of deploying infrastructure is less important than the “managing it safely” part. Our AI and governance features already work across any cloud accounts, regardless of how resources were deployed.

Today, we’re taking this philosophy a giant step further. You can now use Terraform, OpenTofu, or Pulumi IaC as your client-side tool of choice, while still leveraging the full suite of Pulumi Cloud capabilities.

What does this mean for you?

• Unified Visibility: Terraform state files and workspaces will appear and behave much like Pulumi stacks in the Pulumi Cloud UI. You’ll gain full visibility into who changed what, when, including detailed diffs and logs.

• Intelligent Governance: Apply sophisticated policy-as-code and governance across all your infrastructure, whether managed by Pulumi or Terraform.

• AI-Powered Operations: Our infrastructure engineering AI agent, Neo, will extend its capabilities to help manage and understand your Terraform-managed resources, offering insights and automation previously unavailable.

This isn’t about forcing an immediate migration; it’s about providing a single pane of glass and an intelligent control plane for all your infrastructure. Many teams need to maintain a mix of IaC tools, and ensuring all infrastructure is fully automated, secured, and managed is a more critical outcome than debating tool choice.

Support for Terraform/OpenTofu state is currently in private beta, with general availability anticipated in Q1 2026.

2. HCL Language Support in Pulumi IaC: Embracing the Polyglot World

At Pulumi, we truly love languages. Our existing support for Python, TypeScript, Go, C#, Java, and YAML provides developers with incredible power, access to vast ecosystems, and rich tooling. This choice of language is then married with the best of declarative IaC, ensuring safety and desired state management.

Yet, we constantly encounter teams where a significant portion of the workforce is comfortable with, or genuinely prefers, HCL. HCL was purpose-built for IaC and excels at simpler use cases. While our YAML support addresses some of these needs, the “muscle memory” around HCL in the IaC community is undeniable.

The good news? We are not dogmatic about languages; we believe in “come one, come all.” And the time has come for HCL.

Pulumi IaC will now natively support HCL, just like any of our other languages. This isn’t a bolt-on; it’s a deep integration that gives HCL users:

• Full Access to the Pulumi Ecosystem: Leverage thousands of providers, thanks to our robust Terraform bridge. If a Terraform provider exists, it works.

• Multi-Language Interoperability: Author modules in one language (e.g., a complex component in Go) and consume them directly from HCL (or vice versa!). This is a massive unlock for platform teams building reusable components.

• Modern IaC Engine Benefits: HCL users will benefit from Pulumi’s advanced engine, offering capabilities beyond what traditional HCL workflows provide.

This capability is explicitly not meant solely as a lift-and-shift migration option (we have other tools for that!). Instead, it’s for teammates who prefer HCL but want to leverage the modern, multi-language power of the Pulumi IaC engine.

HCL support is also currently in private beta, with general availability anticipated in Q1 2026.

3. Builds on Existing Coexist and Convert Capabilities

These two new capabilities augment an already powerful suite of tools designed to make Pulumi your IaC platform of choice, even in hybrid environments:

• Any Terraform Provider: Pulumi IaC already supports using any Terraform provider, either pre-built in the Pulumi Registry or generated on demand.

• Comprehensive Migration Tools:

  • Neo, our AI agent, has specific skills to migrate both Terraform code and state.

  • The pulumi convert --from terraform command intelligently converts HCL or CDKTF code into your chosen Pulumi language, preserving structure and migrating modules.

  • Directly importing resources from your cloud accounts, either via CLI or visually in Pulumi Cloud.

• Deploy Terraform Modules: Directly use off-the-shelf Terraform modules from any Pulumi language, including HCL, appearing as native Pulumi resources.

• Reference Terraform State Outputs: Easily consume outputs from Terraform state in your Pulumi programs, facilitating gradual migrations or long-term coexistence for hybrid teams.

A Path Forward

The IaC landscape is evolving rapidly. At Pulumi, we believe in empowering teams with choice, flexibility, and a truly modern approach to infrastructure. By embracing Terraform and OpenTofu through Pulumi Cloud and integrating HCL natively into Pulumi IaC, we are breaking down barriers and offering a more universal, open-source-friendly, and powerful platform for everyone.

We’re excited to partner with you on this journey. If you’re currently using Terraform or OpenTofu and are looking for a better way forward, we invite you to explore these new capabilities and see how Pulumi can help you achieve faster time to market with built-in security and compliance, all while respecting your existing investments.