Terraform — Declarative infrastructure as code: write config, preview a plan, apply - providers for nearly every cloud.
What it is
Terraform is HashiCorp's infrastructure-as-code tool: you declare the desired state of cloud and platform resources in HCL, preview a plan, then apply it. The CLI is a free single binary; HCP Terraform adds paid team collaboration.
Editor's review
Long-form introduction by the BetterPicker editors · checked against the official site · Oct 23, 2026
Terraform is still the reference point for infrastructure as code, and its core loop - declare the desired end state in HCL, preview a plan, apply - is the pattern most competitors imitate. HashiCorp ships it as a single static binary for macOS, Windows, Linux, FreeBSD, OpenBSD and Solaris; the current release is 1.17.0, and the CLI itself is free to use. Instead of clicking through consoles, you describe what should exist, Terraform compares that with its recorded state file, and it works out exactly what to create, change or destroy. Reviewers keep praising the same strengths: the plan preview that makes changes reviewable before they touch anything, providers covering every major cloud plus a long tail of platform services, and one consistent workflow across AWS, Azure and Google Cloud. Two objections surface in nearly every serious assessment. The license is no longer open source - since 2023 Terraform ships under the Business Source License 1.1, which pushed part of the community to the OpenTofu fork - and the workflow has sharp edges, because state files demand careful storage and locking, can contain secrets, and HCL error messages are famously terse. Teams that outgrow the CLI typically move runs, collaboration and policy up into HCP Terraform, a paid cloud service with a free tier.
What it does well
Plans you can review: every apply is preceded by a diff of the intended changes, so reviewers describe infrastructure work becoming closer to code review than console clicking, with destructive surprises caught before they happen.
One workflow, every platform: a single binary and a provider model let the same configuration language span compute, networking, DNS, Kubernetes and SaaS features across clouds, which users report is the main reason they standardize on it.
A deep ecosystem: the public registry of modules and providers, years of tutorials and established certification paths mean most problems have documented answers, and walkthroughs commonly assemble whole environments from reusable modules.
Who it's for
Terraform is for platform, DevOps and SRE teams that provision infrastructure repeatedly and want it reproducible, reviewable and version-controlled - spinning up identical development, staging and production environments from one codebase is the canonical use case. It suits organizations that prefer declarative, tool-managed change over hand-edited consoles and tribal knowledge. It is a weaker fit if your main need is configuring software after servers already exist; reviewers note configuration-management tools such as Ansible usually complement it rather than compete with it.
Where it falls short
Not open source anymore: the 2023 move to the Business Source License 1.1 restricts offering Terraform itself as a competing service and split the community; teams with open-source mandates often standardize on the OpenTofu fork instead.
State is a discipline: the state file is the source of truth for every plan, must be stored remotely with locking for teams, and frequently holds sensitive values, so leaked or corrupted state is the classic Terraform accident users report.
HCL takes patience: the language is approachable at first, but debugging failed plans, count and for_each logic and terse error output carries a real learning curve, and large dependency graphs make each plan-apply cycle slow.
Specs at a glance
Facts from the official site · not editorial opinion
| Latest version | 1.17.0 |
|---|---|
| Price | CLI free; HCP Terraform cloud service is paid, with a free tier |
| Platforms | macOS, Windows, Linux, FreeBSD, OpenBSD and Solaris |
| Open source | No - source-available under the Business Source License 1.1 |
| Core capability | Declarative infrastructure as code with plan, apply and state tracking |
| Integrations | Providers for AWS, Azure, Google Cloud, Kubernetes and more; Terraform Registry; HCP Terraform |
| Best for | Platform and DevOps teams provisioning multi-cloud infrastructure as reviewable, repeatable code |
Frequently asked questions
▸Is Terraform still open source?
No. Since 2023 it has been licensed under the Business Source License 1.1, which is source-available but not an open-source license and restricts offering Terraform as a competing service. The community-led OpenTofu fork continues under an open-source license.
▸Does Terraform cost money?
The CLI is free to download and use. Costs begin with HCP Terraform, the hosted collaboration service, which has a free tier and paid plans for teams that need remote state, managed runs and policy controls.
▸What is the state file and why do people worry about it?
It records what Terraform believes exists in your infrastructure and drives every plan. Teams should keep it in remote storage with locking, restrict access and treat it as sensitive, since it can contain secrets and corrupting it makes changes unpredictable.
▸Terraform or OpenTofu - which should I choose?
They are near drop-in compatible, since OpenTofu forked from Terraform to preserve an open-source license. Reviews suggest choosing Terraform for official vendor backing and HCP integration, and OpenTofu if open-source licensing or community governance is a requirement.
Video reviews
4 review videos aggregated · praise and criticism included alike · click through to the original video
Channels that covered it
Channels are aggregated as sources only — we don’t rate creators
Related tools
Where to go next
External links open in a new tab; external content is independent of this site.
Link down? Every object page is re-checked monthly.