Compare tools
Pick 2–5 published tools. Values come from our evidence-checked profiles — an em-dash means unknown, never “no”. Ranking rows reflect the current published methodology for the comparison context.
Terraform vs AWS CloudFormation
Context: Infrastructure as Code (IaC) Tools · 19 rows
| Attribute | TerraformHashiCorp | AWS CloudFormationAmazon Web Services |
|---|---|---|
| Identity · Taxonomy | ||
| Documentation | https://developer.hashicorp.com/terraform | https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/ |
| Tags | iac, multi-cloud, declarative, provisioning | aws, iac, provisioning, cloud |
| Platform · Deployment | ||
| Delivery model | SaaS, self-hosted | managed-cloud |
| Pricing · Licensing | ||
| Free plan | — | true |
| Free trial | true | — |
| License model | source-available | proprietary |
| Pricing model | usage, subscription | free, usage |
| Source repository | https://github.com/hashicorp/terraform | — |
| SPDX license IDs | BUSL-1.1 | — |
| Starting price | 0.1 | — |
| Features · Product · Fit | ||
| Core capabilities | declarative configuration language, infrastructure provisioning and versioning, multi-cloud provider ecosystem, team collaboration via HCP Terraform, policy enforcement, registry module publishing | template-based AWS provisioning in JSON or YAML, stack and change management, multi-account and multi-region deployment, drift detection, registry extensions and hooks |
| Api · Integrations · Ecosystem | ||
| CLI | true | true |
| Audience · Use · Case | ||
| Best for | Teams standardizing multi-cloud provisioning with a declarative workflow; paid editions add collaboration and governance features. | AWS-centric teams that want native, template-based provisioning of AWS resources across accounts and regions. |
| Company-size fit | individual, enterprise | — |
| Primary use cases | cloud infrastructure provisioning, multi-cloud standardization, team infrastructure workflows | AWS resource provisioning, multi-account multi-region deployments, CI/CD infrastructure automation |
| Lifecycle · Versioning | ||
| Maintenance status | active | active |
| Vendor · Maintainer | ||
| Founded year | 2014 | 2011 |
| Headquarters country | United States | United States |
| Vendor type | commercial | commercial |
“—” means unknown (we never treat missing evidence as a negative). Cells reflect each value's current evidence state; superseded or stale values are excluded. Ranking rows are editorial assessments under the cited methodology version — see the Infrastructure as Code (IaC) Tools category for definitions.