Из ленты dev.to devops — кратко, чтобы не потерять.
For most of the last decade, “infrastructure as code” and “Terraform” were nearly synonymous. That stopped being true in 2023, when HashiCorp relicensed Terraform under the Business Source License (BSL), and the community responded by forking the last MPL-licensed version into what became OpenTofu under the Linux Foundation. Two and a half years later, the dust has settled enough to make a real decision. I spent several weeks running all three — Terraform, OpenTofu, and Pulumi — against the same set of stacks: an AWS VPC with ECS services and RDS, a Cloudflare DNS and Workers setup, and a small Kubernetes cluster. The goal was not to find a single winner but to figure out which tool fits which team, because the honest answer in 2026 is that it depends heavily on what your engineers already
Полный текст и контекст у первоисточника: https://dev.to/pickuma/pulumi-vs-terraform-vs-opentofu-infrastructure-as-code-in-2026-1bff