Terraform

OpenTofu has matured significantly since its fork from Terraform. Here’s where things stand and what it means for teams managing cloud infrastructure.

A year and a half after forking from Terraform, OpenTofu is proving that community-driven infrastructure tooling can thrive — but challenges remain.

OpenTofu hits its first GA release, proving that the open-source fork of Terraform is more than a protest — it’s a viable alternative.

As OpenTofu approaches its first stable release, the HashiCorp license change continues to reshape how we think about open source infrastructure tooling.

OpenTofu, the community fork of Terraform born from HashiCorp’s license change, is rapidly building momentum under the Linux Foundation.

HashiCorp’s switch to the Business Source License has triggered a community fork of Terraform called OpenTofu, and the implications for infrastructure-as-code are enormous.

HashiCorp’s decision to relicense Terraform and other products under the Business Source License has sent shockwaves through the infrastructure community.

Terraform 1.1 brings refactoring support and moved/imported blocks, signaling that Infrastructure as Code tooling is growing up.

After years of 0.x releases, Terraform hits 1.0 with stability guarantees. What this means for the IaC ecosystem and your existing workflows.

Terraform 0.13 brings count and for_each to modules, automatic provider installation, and custom validation rules. A look at what changes in practice.

The sudden shift to remote work has stress-tested Infrastructure as Code practices at unprecedented scale. Here’s what’s working, what’s breaking, and what we should learn.