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 September 3, 2026, AWS opened programmatic management of CloudFront flat-rate plans through the new PricingPlanManager API, the CLI, CloudFormation and the CDK. Teams can now codify subscribing, changing tiers and cancelling a no-overage monthly price, with a two-phase approval that prevents unintended billing.
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.
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.
On August 13, 2026 AWS shipped version 6.0 of its VPN client, rebuilt on OpenVPN3 with a full CLI and centralized administrative controls. Teams automating remote access can now script connections without third-party tooling.
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.
