OpenStack Heat vs OpenTofu
OpenStack Heat
docs.openstack.orgOpenTofu
opentofu.orgSide by side
| Figure | OpenStack Heat | OpenTofu |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Infrastructure as Code Tools | 7.6 (#17) | 7.8 (#11) |
| Spec score · Infrastructure Automation | 7.6 (#14) | 7.8 (#12) |
| Spec score · IT Configuration Management Software | 7.6 (#18) | 7.8 (#16) |
| Spec score · Orchestration / Provisioning Software | 7.6 (#21) | 7.8 (#16) |
| Purpose | Heat orchestrates composite cloud applications from declarative templates through an OpenStack-native REST API. | OpenTofu is an infrastructure as code tool for defining cloud and on-premises resources in human-readable configuration files. |
Plans
In their own words
OpenStack Heat
OpenStack Heat is a free, open-source orchestration service for composite applications in OpenStack. Declarative templates describe infrastructure and relationships in human-readable files that can be version-controlled. Heat can create instances, floating IPs, volumes, security groups, and users, while supporting instance high availability, autoscaling, and nested stacks. It runs HOT templates written in YAML and also accepts AWS CloudFormation templates. Templates can integrate with Puppet and Ansible, and operators can extend capabilities with plugins. The service exposes an OpenStack-native REST API and a CloudFormation-compatible Query API. Access is available through a command-line interface, RESTful queries, and the OpenStack dashboard. Heat runs on Linux as a self-hosted service and is provided under the Apache 2.0 license. Installation assumes an existing OpenStack environment with Compute, Image Service, and Identity, with guidance covering Red Hat Enterprise Linux, CentOS, Ubuntu, and Debian.
OpenTofu
OpenTofu is a free infrastructure as code tool for defining cloud and on-premises resources in human-readable configuration files. Its workflow moves from writing configuration to generating a plan and applying approved changes in dependency order. Providers connect it with cloud platforms, SaaS services 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, builds a dependency graph and can change independent resources in parallel. Built-in client-side state encryption supports key providers such as PBKDF2, AWS KMS, GCP KMS and OpenBao. Providers can be installed from registries, local mirrors or caches, including for air-gapped environments. OpenTofu is presented as a Terraform replacement that preserves existing workflows and configurations. OCI registries can host modules and serve as a secondary provider source, but not yet the primary source. Official installation options cover Linux, macOS, Windows, FreeBSD and OCI container images.