Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

OpenTofu

opentofu.org

  • Free plan
  • Windows
  • macOS
  • Linux
  • Self-hosted
7.4 Club score Visit opentofu.org

What OpenTofu is

OpenTofu is an infrastructure as code tool for describing cloud and on-premises resources in human-readable configuration files. Its workflow moves from writing configuration to generating a plan, then applying approved changes in dependency order. It is presented as a Terraform replacement that preserves existing workflows and configurations. Providers connect it to cloud services, SaaS products and APIs, including AWS, Azure, Google Cloud Platform, Kubernetes, Helm, GitHub, Splunk and Datadog. Reusable modules and a public registry support configurable infrastructure collections. OpenTofu tracks resources in a state file and uses a dependency graph to apply changes, working on independent resources in parallel. Built-in client-side state encryption supports PBKDF2, AWS KMS, GCP KMS and OpenBao. Providers can come from registries, local mirrors or caches, including for air-gapped environments. OCI registries support modules and secondary provider installation, but are not yet the primary provider source. The project is maintained under the Linux Foundation. The listed plan costs nothing.

Who it suits

OpenTofu suits infrastructure teams that want to define and manage cloud or on-premises resources through configuration. It can also suit users who need provider installation from local mirrors, caches or registries, including in air-gapped workflows.

Good to know, and what to watch

  • Configuration and approved changes follow a defined plan workflow.
  • Independent resources can be created or modified in parallel.
  • Built-in client-side state encryption supports several key providers.
  • Provider installation supports registries, local mirrors and caches.
  • Self-hosted execution is supported.
  • OCI is not yet the primary provider source.
  • Official installation methods cover listed operating systems and OCI images.

OpenTofu

Free

Free plan

Getting started

  1. Open the OpenTofu website
  2. Choose an official installation method for Linux, macOS, Windows, FreeBSD, or an OCI container
  3. Install OpenTofu on your system or self-hosted environment
  4. Write infrastructure configuration in HCL
  5. Generate an execution plan
  6. Apply approved changes in dependency order

Limits to check

OCI registries can provide modules and secondary provider installation, but they are not the primary provider source. OpenTofu tracks infrastructure through a state file used as the source of truth for required changes.

The verdict

OpenTofu combines configuration-driven infrastructure changes with state tracking, provider integrations and reusable modules. OCI provider installation remains limited to a secondary source for now.

Questions people ask

How much does OpenTofu cost?

OpenTofu is free, with a listed plan price of free open-source infrastructure as code tool.

Which systems can run OpenTofu?

Official installation methods cover Linux distributions, macOS, Windows, FreeBSD, and OCI container images. Self-hosted execution is supported.

Can OpenTofu replace Terraform?

OpenTofu is presented as a drop-in replacement for Terraform that preserves existing workflows and configurations.

Which providers does it support?

Examples include AWS, Azure, GCP, Kubernetes, Helm, GitHub, Splunk, and Datadog. Providers can be installed from registries, local mirrors, or caches.

Does OpenTofu support reusable infrastructure components?

Yes. It supports reusable modules and provides a public registry of modules and providers.

How is infrastructure state handled?

OpenTofu stores infrastructure state in a state file used to determine required changes. Built-in client-side encryption supports key providers including PBKDF2, AWS KMS, GCP KMS, and OpenBao.

What the maker publishes

Community support
The project directs users to community Slack, GitHub discussions, issues, RFC discussions, and contributions. source
Founded
2023 source
Governance
OpenTofu is hosted and maintained under the Linux Foundation as a community-driven, impartial open-source project. source
Modules
OpenTofu supports reusable modules for configurable collections of infrastructure and provides a public registry of modules and providers. source
OCI integration
OpenTofu supports OCI registries for modules and as a secondary provider installation source, but not yet as the primary provider source. source
Parallel execution
OpenTofu builds a resource dependency graph and creates or modifies non-dependent resources in parallel. source
Project scale
The official website reports an ecosystem of more than 3,900 providers and 23,600 modules. source
Provider installation
Providers can be installed from registries, local mirrors, or caches, and OpenTofu supports workflows for air-gapped environments. source
Providers
Providers let OpenTofu manage cloud platforms, SaaS providers, and other APIs, with examples including AWS, Azure, GCP, Kubernetes, Helm, GitHub, Splunk, and Datadog. source
Purpose
OpenTofu is an infrastructure as code tool for defining cloud and on-premises resources in human-readable configuration files. source
State encryption
Built-in client-side state encryption supports key providers including PBKDF2, AWS KMS, GCP KMS, and OpenBao. source
State tracking
OpenTofu stores infrastructure state in a state file that acts as the source of truth for determining required changes. source
Supported systems
Official installation methods cover Linux distributions, macOS, Windows, FreeBSD, and OCI container images. source
Terraform compatibility
OpenTofu is presented as a drop-in replacement for Terraform that preserves existing workflows and configurations. source
Workflow
Its core workflow consists of writing configuration, generating an execution plan, and applying approved changes in dependency order. source

Checked against the maker's pages on 30 Sept 2026.