HashiCorp Terraform
Terraform is HashiCorp’s flagship — the de-facto-standard Infrastructure as Code tool that provisions multi-cloud & hybrid infrastructure as declarative code. Write, Plan, Apply — with the biggest provider registry in IaC. (Honest: the 2023 BSL relicense spawned the open OpenTofu fork.)
Buy through TechBag
Same software. Better outcome — at a lower cost.
How it’s rated
Full scoreboard ↓Quick answer
The HashiCorp platform family
This page covers Terraform — the flagship (Infrastructure as Code). The rest of the HashiCorp stack:
Quick facts
30-second orientation- Product
- Terraform — Infrastructure as Code
- Vendor
- HashiCorp, an IBM Company (founded 2012)
- The category
- Infrastructure as Code (IaC)
- What it does
- Provision cloud/on-prem infra as code
- The workflow
- Write → Plan → Apply (declarative HCL)
- The superpower
- Huge provider registry — any cloud
- The honest story
- BSL relicense (2023) → OpenTofu fork
- Ownership
- IBM (deal closed Feb 27, 2025)
- Vs
- OpenTofu, Pulumi, CloudFormation/CDK, Bicep, Crossplane
- In India via
- TechBag — scoping, licensing, GST
Understand Infrastructure as Code before you buy it
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
What is HashiCorp Terraform?
Infrastructure as Code (IaC) — provision cloud & on-prem infrastructure as declarative, version-controlled code (HCL). The de-facto standard, with the biggest provider registry in IaC.
Manual provisioning vs Terraform IaC — the honest table
What consolidation actually replaces, dimension by dimension.
| Dimension | Unprotected / signature email | Terraform (HashiCorp) |
|---|---|---|
| Provisioning | Click consoles / scripts | Declarative code (IaC) |
| Changes | Blind, risky | Plan preview before apply |
| Repeatability | Snowflake environments | Idempotent, reproducible |
| Cloud coverage | One-cloud native IaC | Multi-cloud, one workflow |
| Ecosystem | Fragmented | Biggest provider registry |
| Governance | Ad-hoc | Policy-as-code (Sentinel/OPA) |
| Licensing | (was MPL open-source) | BSL — OpenTofu is the open fork |
| Best fit | (varies) | The multi-cloud IaC standard |
Terraform is the de-facto Infrastructure-as-Code standard — provision multi-cloud & hybrid infrastructure as declarative code (Write/Plan/Apply) with the biggest provider registry in IaC. Honest: the 2023 BSL relicense spawned the truly-open OpenTofu fork (some teams choose it for licensing freedom), and HashiCorp is now an IBM company. TechBag scopes it & adds GST.
The five pieces of the platform
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
Write — Declarative Code (HCL)
Define infrastructure declaratively in HCL, describing the desired end state as version-controlled, reviewable, reusable code. Terraform works out how.
Plan — Preview Before You Touch
terraform plan shows exactly what will be created, changed or destroyed to match your code, before anything is touched. No surprises.
Apply — Make It So
terraform apply calls provider APIs to make real infrastructure match your code, tracking it in state. Run it again and nothing changes unless the code did.
Providers — The Registry
Thousands of providers (AWS, Azure, Google Cloud, Kubernetes and countless SaaS) mean one workflow provisions almost anything: the biggest ecosystem in IaC.
State & Collaboration
HCP Terraform and Terraform Enterprise add remote state, policy-as-code (Sentinel), a private module registry and collaboration for whole teams.
One declarative plan before any change — the same HCL provisions any provider, with state shared across the team.
Twelve capabilities. Write, plan, apply.
Terraform provisions any cloud as declarative code — Write, Plan, Apply, with the biggest provider registry — the Infrastructure-as-Code flagship of the HashiCorp portfolio.
Declarative IaC in HCL
Declarative, human-readable HCL describes the desired state, versioned in Git and reviewed like any code.
Modules — Reusable Building Blocks
Package a VPC, Kubernetes cluster or app stack as reusable modules, shared via a public or private registry.
Multi-Cloud & Hybrid
One workflow provisions AWS, Azure, Google Cloud, on-prem, Kubernetes and SaaS from a single codebase.
Plan — Preview Every Change
terraform plan shows exactly what will be created, changed or destroyed before you apply. No blind changes.
Dependency Graph & Ordering
Builds a dependency graph and provisions resources in the right order, in parallel where safe.
Policy-as-Code (Sentinel / OPA)
Policy-as-code (Sentinel in HCP/Enterprise, or OPA) blocks public S3 buckets, unapproved regions or untagged resources before apply.
Apply — Provision the Real Thing
terraform apply calls provider APIs to make reality match your code, idempotently: rerun it and nothing changes unless the code did.
State & Drift Detection
Tracks managed resources in state, so it knows what it owns, detects drift from manual changes, and reconciles back to code.
Public & Private Registry
A public registry of thousands of providers and modules, plus a private registry (HCP/Enterprise) for your approved modules.
HCP Terraform — Team Workflow
HCP Terraform (formerly Terraform Cloud) and Enterprise add remote state, run pipelines, VCS integration, private registry and policy.
OpenTofu — the Open Fork (be honest)
Since the 2023 BSL relicense, OpenTofu, an MPL, Linux Foundation drop-in fork, is a real alternative. TechBag covers both sides.
Anchor of the HashiStack
The anchor of the HashiCorp stack: provision with Terraform, then add Vault, Consul, Nomad and Boundary.
Watch Terraform in action
The overview, getting started, and the core workflows.
Introduction to HashiCorp Terraform with Armon Dadgar
Infrastructure as Code, explained.
Introduction to Terraform
The core IaC workflow, walked through.
Introduction to HashiCorp Cloud Platform (HCP): Goals and Components
HCP, the managed platform behind HCP Terraform.
Want a live, India-context walkthrough for your environment?
Book a guided demo →Shipping code is the goal. One flow gets you there.
Here’s what genuinely sets Terraform apart (and the honest OpenTofu / IBM-ownership context).
The de-facto IaC standard — the biggest ecosystem and mindshare
Terraform is the de-facto standard for Infrastructure as Code. Clicking consoles or brittle scripts can’t be versioned or reproduced; Terraform turns infrastructure into code, with thousands of providers, the most modules and integrations, and the deepest hiring pool of any IaC tool.
Write, Plan, Apply — safe, repeatable, multi-cloud provisioning
Infrastructure changes are risky. Terraform’s Write, Plan, Apply loop previews exactly what will change before anything happens, orders resources through a dependency graph, tracks state so runs are idempotent and drift shows up, and works the same on AWS, Azure, Google Cloud and Kubernetes.
Multi-cloud from one codebase — avoid cloud lock-in workflows
Each cloud’s native IaC (CloudFormation, Bicep, Deployment Manager) stays inside that cloud. Terraform uses one language and workflow across AWS, Azure, Google Cloud, Kubernetes, on-prem and SaaS, so skills and modules are portable. IBM ownership raises neutrality questions, and OpenTofu is the open alternative.
The honest one: BSL relicense & the OpenTofu fork
On August 10, 2023, HashiCorp moved Terraform from the open MPL to the source-available Business Source License. The community forked it as OpenTofu, an MPL, Linux Foundation project. For most internal use, BSL Terraform is fine; if open licensing is a hard requirement, OpenTofu is a drop-in choice.
Now an IBM company — with TechBag adding local India support
HashiCorp, founded in 2012, was acquired by IBM (deal closed February 27, 2025) and now sits beside Red Hat Ansible. Terraform has a free CLI, HCP Terraform priced per managed resource, and quote-priced Terraform Enterprise. TechBag scopes the tier and the OpenTofu question, in INR with 18% GST.
The honest scope
Terraform is the default multi-cloud IaC tool. Caveats: the 2023 BSL relicense created the open OpenTofu fork; IBM ownership raises neutrality questions; and HCL and state take learning. Pulumi suits general-purpose languages, and CloudFormation or Bicep suit single-cloud shops.
The numbers behind the platform
What your Terraform journey looks like
Scoping (& the OpenTofu question)
Map your clouds, team and governance needs, and CLI vs HCP vs Enterprise. TechBag covers OpenTofu and IBM ownership honestly.
Write — codify your infrastructure
Write infrastructure as declarative HCL, package reusable modules and version it in Git as your source of truth.
Plan & Apply — safely provision
Preview each change with plan, apply across your clouds, and add Sentinel or OPA policy-as-code guardrails.
Scale with HCP & the HashiStack
Adopt HCP Terraform or Enterprise for remote state and governance, then extend to Vault, Consul, Nomad and Boundary.
The review scoreboard
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
Quick poll — what’s driving your evaluation?
Talk to an advisor“One version-controlled workflow across AWS, Azure and GCP. The plan step alone has saved us from countless production mistakes.”
“Whatever we need to provision, a provider already exists. Nothing else in IaC matches that ecosystem.”
“We run genuinely multi-cloud and Terraform is the only tool that gives us one consistent workflow across all of it. Portable skills, portable modules.”
“The BSL relicense made us evaluate OpenTofu. TechBag walked us through both sides rather than ignoring the fork.”
“HCP Terraform gave us remote state, policy-as-code and a private module registry, so IaC works for the whole org.”
“Our GCC in Bengaluru runs Terraform at scale with a deep local hiring pool. TechBag scoped HCP vs the free CLI and INR/GST.”
“Plan and apply turned risky infrastructure changes into reviewed, previewed, repeatable ones.”
“We chose Terraform over Pulumi for the ecosystem, and TechBag was candid about IBM ownership and the OpenTofu option.”
Where everyone sits — the grids
Analyst firms bury this view behind paywalls, and review-site grids score satisfaction, not fit for your estate. So here’s TechBag’s synthesis of the IaC market — tap any vendor to see why it sits where it does.
TechBag Developer-Tools Grid
Execution strength vs product vision — the classic market map, minus the paywall.
The de-facto IaC standard. This page's product.
IaC Depth × Ecosystem Breadth
The grid nobody publishes — IaC depth vs ecosystem & multi-cloud breadth.
Ecosystem + multi-cloud depth.
Positions are TechBag’s illustrative synthesis of public review-platform data and vendor documentation — not a reproduction of any analyst graphic. Verify before relying on it.
Terraform vs the IaC field
OpenTofu, Pulumi, AWS CloudFormation/CDK, Azure Bicep/ARM and Crossplane — honest lanes; the edge is the biggest ecosystem + genuine multi-cloud. Need open licensing? OpenTofu (the fork). Want real languages? Pulumi. All-in on one cloud? Native IaC. We say so.
| Dimension | Terraform | OpenTofu | Pulumi | AWS CloudFormation/CDK | Azure Bicep/ARM | Crossplane |
|---|---|---|---|---|---|---|
| Position | The IaC standard (this page) | Truly-open Terraform fork | IaC in real languages | AWS-native IaC | Azure-native IaC | IaC via Kubernetes/CRDs |
| Multi-cloud breadth | Broadest (huge registry) | Same providers (fork) | Multi-cloud | AWS only | Azure only | Provider-based |
| Ecosystem / mindshare | Biggest by far | Growing (community) | Solid | Large (AWS) | Large (Azure) | Niche (K8s) |
| Licensing openness | BSL (source-available) | MPL (truly open, LF) | Apache 2.0 (open) | Vendor (free) | Vendor (free) | Apache 2.0 (CNCF) |
| Language / model | HCL (declarative) | HCL (declarative) | Python/TS/Go/C# | YAML/JSON + CDK | Bicep (declarative) | YAML (CRDs) |
| Team / governance (policy, state) | HCP/Enterprise + Sentinel | Community + OPA | Pulumi Cloud | AWS-native | Azure-native | Via K8s/GitOps |
| Best fit | The multi-cloud IaC standard, biggest ecosystem | Want truly-open licensing (drop-in) | Want IaC in Python/TypeScript | All-in on AWS | All-in on Azure | Kubernetes-native control planes |
Which developer-platform approach fits you?
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
Choose Terraform if…
- ✓You want the de-facto IaC standard — the biggest provider registry, ecosystem, tooling and talent pool
- ✓You want genuine multi-cloud/hybrid from one codebase and one workflow
- ✓You want a safe, repeatable Write/Plan/Apply workflow with policy-as-code governance (HCP/Enterprise)
- ✓You want the anchor of the HashiCorp stack — with TechBag adding scoping, the honest OpenTofu view & GST
OpenTofu if…
- ✓Open-source licensing/governance is a hard requirement — it’s a truly-open (MPL, Linux Foundation), drop-in-compatible fork of Terraform
Pulumi if…
- ✓You want to write IaC in a general-purpose language (Python, TypeScript, Go, C#) rather than HCL
Native cloud IaC if…
- ✓You’re all-in on one cloud — AWS CloudFormation/CDK or Azure Bicep/ARM are deeply integrated for that single cloud
Crossplane if…
- ✓You want Kubernetes-native infrastructure control planes (IaC via CRDs and GitOps)
HashiCorp Terraform is one of 36 developer tools products TechBag carries. The Developer Tools guide narrows them to a shortlist and shows the reasoning. →
What could this save you?
Drag the sliders (environments/deployments per month; engineer-hour cost as loaded rate). Estimates contrast manual/scripted provisioning (slow, error-prone, snowflake environments, no preview) vs Terraform (declarative code, plan-before-apply, idempotent, reproducible) — the wins are provisioning time saved, mistakes avoided, and reproducible environments. Illustrative — TechBag scopes your clouds.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models your actual environment and modules.
Three ways to consume it
The Terraform CLI is free to use under the source-available BUSL licence (or use the open OpenTofu fork). HCP Terraform is free up to 500 managed resources, then priced per managed resource per month (HashiCorp lists Essentials from $0.10, Standard from $0.47 and Premium from $0.99); Terraform Enterprise (self-hosted) is quote-priced. Both add team governance (remote state, policy-as-code, private registry). TechBag scopes the CLI vs HCP vs Enterprise and handles INR/GST (18%).
Terraform (free CLI / HCP / Enterprise)
Best for multi-cloud IaC
- Free CLI under BUSL (or the open OpenTofu fork); HCP Terraform from $0.10 per resource/mo
- Write/Plan/Apply — declarative, multi-cloud, biggest registry
- Paid HCP Terraform / Enterprise add team state, policy & governance
+ Platform add-ons
Best for a broader rollout
- Scoped to your estate
- Add-on modules as needed
- Phased, right-sized deployment
+ scoping & local support
Best value with TechBag
- CLI vs HCP vs Enterprise scoping + the honest OpenTofu question
- Now an IBM company; HashiCorp has Bengaluru R&D
- TechBag adds INR/GST (18%), IBM-channel options & local support
Buy it for less — TechBag pricing beats list
Whatever the list prices above, TechBag negotiates a significantly better deal — with GST-compliant INR invoicing and local support. Ask us for your discounted quote.
Get an India-ready quote
Tell us your requirements and current tools — we’ll model it against what you spend today.
The 8 questions to ask every vendor
Take this into your next vendor call — including ours.
Provisioning across AWS/Azure/GCP or hybrid? Terraform gives one consistent workflow across all of them, from one codebase.
Worried about risky infrastructure changes? Terraform’s plan step previews exactly what will change before you apply.
Is open-source licensing a hard requirement for us, given Terraform is BSL and OpenTofu is the MPL fork?
Need remote state, policy-as-code and collaboration? HCP Terraform / Terraform Enterprise add governed, team-scale IaC.
Need to provision something specific? Terraform’s registry has thousands of providers — the biggest ecosystem in IaC.
Weighing long-term neutrality/roadmap? HashiCorp is now an IBM company (deal closed Feb 2025). TechBag gives you the honest context.
Building a platform-engineering practice in India? Terraform has deep community and hiring depth; HashiCorp has Bengaluru R&D.
Free CLI, HCP Terraform (per managed resource, free up to 500) or quote-priced Enterprise: which fits, with INR/GST (18%)?
Questions buyers ask
Ready to standardise on Terraform?
Scope HashiCorp Terraform (the de-facto Infrastructure-as-Code standard — provision multi-cloud & hybrid infrastructure as declarative code, Write/Plan/Apply, biggest provider registry) — and let a TechBag advisor scope the free CLI vs HCP vs Enterprise, give the honest OpenTofu & IBM-ownership view, compare vs Pulumi and native IaC, and add INR/GST and local support.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.