OpenTofu

OpenTofu describes infrastructure in a high-level configuration syntax and applies it safely and efficiently. The blueprint of a datacenter becomes a file you version, review and reuse like any other code, which pulls provisioning out of the realm of undocumented console clicks and tribal memory.

Changes are never applied blind. A planning step generates an execution plan showing exactly what will happen before anything is touched, and a resource graph resolves dependencies so that unrelated resources are created and modified in parallel. Popular service providers and custom in-house solutions are managed through the same mechanism.

Four properties carry most of the value.

• Infrastructure as code: configuration is versioned, shared and reused the way source is.
• Execution plans: the plan step shows what apply will do, which removes surprises.
• Resource graph: dependencies are computed and non-dependent work runs in parallel.
• Change automation: complex changesets apply with minimal human interaction and in a known order.

Development happens in the open, with community meetings every Wednesday, a technical steering committee every other Tuesday, and day-to-day discussion in a channel on the CNCF Slack. The tool is distributed under the Mozilla Public License v2.0. Nightly builds of the main branch are published for anyone testing unreleased changes, though they are experimental, removed after thirty days and explicitly not meant for production.