On Scalr’s platform, OpenTofu now runs 63% of Terraform-compatible runs and powers 72% of newly created workspaces — not a snapshot of the global market, but of where new work is heading. Version 1.12 adds dynamic prevent_destroy and full provider checksums. For teams provisioning infrastructure, new projects should default to OpenTofu.
On August 31, 2026, between 07:35 and 21:45 UTC, an attacker compromised a Coder Cloudflare API key and redirected part of the module registry’s traffic to a malicious server that exfiltrated cloud credentials. Check your logs for coder-infra[.]com and rotate the affected secrets.
In August 2026, Pulumi brought its Terraform backend, cross-language module conversion, and an OpenTofu-compatible HCL runtime to general availability. Terraform teams can keep their code and state while gaining remote execution, preventive policies, and Neo code reviews.
GitLab extends its OpenBao-powered Secrets Manager to the External Secrets Operator, Terraform, and a direct API, beyond CI/CD alone. The pitch: replace scattered secret stores across CI/CD, Kubernetes, and IaC with a single audited source of truth.
On August 12, 2026 HashiCorp shipped Terraform 1.16 in release candidate, with two major changes: import blocks now work inside modules, and the new store block on terraform_data keeps ephemeral and sensitive values across plan and apply. Teams adopting Terraform over existing infrastructure gain the lever they were missing.
OpenTofu is three years old and running in production at Boeing, Capital One, and AMD. Pulumi is growing 45% year-over-year and just shipped an AI agent that provisions infrastructure from natural language.
OpenTofu v1.12 shipped in May 2026 with native state encryption, provider for_each, and early variable evaluation — features Terraform’s open-source CLI still lacks. Three years after the fork, the question is no longer why you should leave Terraform, but why you would stay.
