The foundational guide to infrastructure as code in 2026 — the declarative model and why the state file is the hard part, the Terraform BUSL license change and the OpenTofu fork, real configuration and workflow, remote state and locking after the DynamoDB era, modules, the broader landscape from Pulumi to Crossplane, and the failure modes nobody warns you about.
Opentofu
-
Infrastructure as Code in 2026: Terraform, OpenTofu, and the State You Have to Manage -
Terraform vs OpenTofu vs Pulumi in 2026 A three-way comparison of the infrastructure-as-code tools that actually matter in 2026: the Terraform/OpenTofu fork that split one tool into two, and Pulumi's bet that real programming languages beat a config DSL. The architectural differences honestly, the state story, where each genuinely wins, and what is worth migrating.
-
Making Proxmox Cloud-Like: OpenTofu, the API, and the Placement Gap You already run Proxmox VE. This is how to bolt self-service onto it: the REST API, the OpenTofu/Terraform provider for declarative VM-plus-network-plus-disk, and an honest accounting of the one thing Proxmox historically did not do — pick the best node for you at provision time. Plus what changed in PVE 9.0's affinity rules and 9.2's dynamic load balancer, and the point where you should stop bolting and adopt a real cloud platform.
-
OpenTofu vs Terraform: The Fork One Year In The Terraform and OpenTofu fork, one year on — what HashiCorp's BSL relicensing actually changed, how the two tools have diverged since, and how to decide which one to standardize on for the next decade.