Pulumi Expands Native HCL Interoperability and OpenTofu State Backend Integration

Pulumi has expanded its cross-ecosystem interoperability by providing direct runtime execution for HashiCorp Configuration Language (HCL) files and serving as a centralized state, secrets, and governance backend for the Terraform and OpenTofu CLIs. Under this model, existing .tf definitions run natively on the Pulumi deployment engine while pointing directly to OpenTofu and Terraform provider registries. Furthermore, platform teams can utilize Pulumi Cloud to manage encrypted state locking, role-based access control, resource search, and policy enforcement across heterogeneous CLI invocations. This development fundamentally shifts the operational calculus for platform architects. Previously, adopting a programming-language-based IaC toolchain (like Python, TypeScript, or Go) required costly code translations, dual state pipelines, or awkward wrappers. By running HCL directly and managing OpenTofu/Terraform state natively, organizations no longer need to execute high-risk, multi-quarter rewrite projects. Infrastructure leaders can unify fragmented observability, compliance, and secrets management at the control plane layer without forcing application and DevOps teams to abandon their preferred syntax immediately. This shift reflects a broader evolutionary phase in cloud infrastructure management: the convergence of declarative configuration and general-purpose software engineering. The IaC landscape has undergone substantial fragmentation following the 2023 license transition of Terraform and the rapid community maturation of Linux Foundation's OpenTofu. Concurrently, the growth of platform engineering has increased demand for real programming constructs—such as object-oriented encapsulation, integrated unit testing, and dynamic pipeline generation—that HCL cannot natively provide. By treating HCL as just another supported language runtime alongside Python and Go, the modern control plane decouples organizational policy and state governance from front-end syntax. In practice, engineering organizations should adopt a pragmatic, multi-tier IaC operational strategy. Teams can maintain core landing zones, VPC topologies, and IAM foundational modules in their existing HCL repositories while immediately ingesting them into a consolidated governance backend. Greenfield application infrastructure, complex dynamic services, and microservice components can then be authored in TypeScript or Python, consuming outputs directly from the underlying HCL state files. Practitioners must evaluate the remaining trade-offs: while native HCL support simplifies orchestration, debugging hybrid stacks across bridged provider wrappers and native schema generators still introduces cognitive overhead. Platform teams should formalize clear linting, policy-as-code guardrails, and module boundary standards to prevent architectural sprawl across mixed-language codebases.