Skip to content
SPECIFICTION
Get listed

OpenStack Heat

docs.openstack.org

Free plan LinuxAPISelf-hosted
Visit docs.openstack.org
Spec score 7.6 #17 of 31 in Infrastructure as Code Tools

What it is

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.

Spec sheet

Purpose
Heat orchestrates composite cloud applications from declarative templates through an OpenStack-native REST API.Read 9 Oct 2026 · docs.openstack.org
Audience
The documentation is aimed at end users, operators and developers of Heat.Read 9 Oct 2026 · docs.openstack.org
Integrations
Heat templates integrate with configuration management tools such as Puppet and Ansible.Read 9 Oct 2026 · docs.openstack.org
License
The OpenStack project is provided under the Apache 2.0 license.Read 9 Oct 2026 · docs.openstack.org
Access
Heat can be accessed through a CLI, RESTful queries and the OpenStack dashboard web interface.Read 9 Oct 2026 · docs.openstack.org
Advanced orchestration
Heat supports instance high availability, instance autoscaling and nested stacks.Read 9 Oct 2026 · docs.openstack.org
APIs
The service provides an OpenStack-native REST API and a CloudFormation-compatible Query API.Read 9 Oct 2026 · docs.openstack.org
Deployment requirement
Installation assumes a working OpenStack environment with Compute, Image Service and Identity already installed.Read 9 Oct 2026 · docs.openstack.org
Extensibility
Operators can customize Heat capabilities by installing plugins.Read 9 Oct 2026 · docs.openstack.org
Resource types
Templates can create OpenStack resources including instances, floating IPs, volumes, security groups and users.Read 9 Oct 2026 · docs.openstack.org
Supported install guidance
The installation documentation links instructions for Red Hat Enterprise Linux and CentOS, Ubuntu and Debian, and says installation varies by distribution.Read 9 Oct 2026 · docs.openstack.org
Template formats
Heat runs HOT templates written in YAML and also supports AWS CloudFormation templates.Read 9 Oct 2026 · docs.openstack.org
Templates
Heat templates describe infrastructure and resource relationships in human-readable text files that can be managed with version control.Read 9 Oct 2026 · docs.openstack.org

Plans and prices

OpenStack Heat Free Requires a working OpenStack environment with Compute, Image Service and Identity · Installation and configuration vary by distribution Read 9 Oct 2026 · docs.openstack.org

Every OpenStack Heat plan and price →

Strong points and limits

Strong points

  • Free Apache 2.0 software
  • YAML and CloudFormation template support
  • Instance autoscaling and high availability
  • CLI, REST, and dashboard access
  • Plugin extensibility

Limits

  • Requires a working OpenStack environment
  • Installation varies by Linux distribution
  • Self-hosted operation required

Who it suits

Heat suits OpenStack end users, operators, and developers who manage infrastructure through declarative templates and self-hosted services.

Verdict

Heat provides template-driven orchestration with multiple APIs, interfaces, and extensibility options. Its prerequisite OpenStack services make it suitable for established OpenStack environments rather than standalone deployment.

Where Specifiction places it

Alternatives to OpenStack HeatAll alternatives →