HCP Terraform Explained: What Changed From Terraform Cloud

If you studied for an earlier version of the Terraform Associate exam, you learned a product called Terraform Cloud. Open the objectives for the current Terraform Associate 004 exam and that name is gone, replaced by HCP Terraform. Nothing was quietly removed. HashiCorp rebranded Terraform Cloud to HCP Terraform in April 2024 to fold it under the HashiCorp Cloud Platform umbrella, and the 004 exam now carries a dedicated domain for its capabilities. This guide explains what HCP Terraform actually is, the features you are expected to recognise, how the free and paid tiers differ at a high level, and why HashiCorp made it its own exam objective.

What HCP Terraform is

HCP Terraform is HashiCorp's managed SaaS platform for running Terraform. Instead of executing terraform plan and terraform apply on your laptop or a CI runner, you connect a workspace to a version control repository, and HCP Terraform runs the workflow for you in a consistent remote environment. It stores your state, streams run logs, gates applies behind approvals, and gives a team a shared place to collaborate on infrastructure rather than passing state files and credentials around by hand.

The rebrand was cosmetic in terms of behaviour. The same product, the same APIs, and the same core concepts carried over. Only the name changed, plus the ongoing plan and pricing evolution described below. HashiCorp itself was acquired by IBM in early 2025, but that did not change how the product works day to day.

Key capabilities to know for the exam

The 004 objectives ask you to recognise what HCP Terraform provides beyond the open-source CLI. The core building blocks are worth knowing by name:

• Remote state management — state is stored and encrypted by HCP Terraform, with locking during runs and full version history, so you avoid the manual S3-plus-DynamoDB backend setup.
• Remote runs — plans and applies execute on HashiCorp-hosted infrastructure (or self-hosted agents), giving consistent runs and a shared audit trail.
• Workspaces — the central organising unit. Each workspace has its own state, variables, and run history, and typically maps to one collection of infrastructure. Note this differs from CLI workspaces, which are just alternate state files within one backend.
• VCS integration — connect GitHub, GitLab and similar so a pull request triggers a speculative plan and a merge triggers an apply.
• Policy as code — enforce guardrails with Sentinel or Open Policy Agent (OPA) before an apply is allowed to proceed.
• Private module and provider registry — publish and share reusable modules across your organisation.
• Run tasks and team access controls — integrate third-party checks into the run lifecycle and manage who can do what.

You do not need to configure these under time pressure for the Associate exam, but you should be able to say what each one does and how it differs from plain CLI usage.

Free vs paid tiers at a high level

HCP Terraform bills on a Resources Under Management (RUM) model, meaning you pay per managed infrastructure resource per month rather than per user or per seat. The free tier is generous and is where most learners will practise.

At the time of writing, HashiCorp's published pricing lists a free tier plus paid SaaS tiers and a self-managed Enterprise option. Prices change, so treat the figures below as orientation rather than something to memorise.

The enhanced free tier was expanded to include capabilities that were previously paid, such as single sign-on, policy as code, run tasks, and HCP Terraform agents. HashiCorp retired the older legacy free plan on 31 March 2026 and migrated remaining organisations onto this enhanced free tier. Exam questions will not quiz you on exact dollar figures, so the point to carry into the exam is conceptual: a free option exists, billing is resource-based rather than per-seat, and higher tiers unlock more governance and support.

Why it is now a 004 exam domain

The Terraform Associate 004 exam, which launched on 8 January 2026 and tests Terraform 1.12, lists eight objective domains. One of them is dedicated to HCP Terraform capabilities. This is the most notable addition compared with the retired 003 exam, and it reflects how HashiCorp sees real-world Terraform being run: increasingly through a managed collaboration platform rather than purely from individual command lines.

For the exam this means you should be comfortable explaining remote state and remote operations, the role of workspaces, VCS-driven runs, private registry publishing, and policy enforcement, and you should be able to contrast the HCP Terraform workflow with the local CLI workflow. Expect conceptual, scenario-style questions rather than deep configuration.

One useful piece of adjacent context: after the 2023 licence change, the community created OpenTofu, an open-source fork of Terraform now under the Linux Foundation. It is worth knowing it exists, but the exam is about Terraform and HCP Terraform, not OpenTofu.

How to fold this into your prep

The fastest way to internalise HCP Terraform is to create a free account, connect a small demo repository, and watch one plan and apply run end to end. Seeing a remote run, a locked state, and a speculative plan on a pull request makes the terminology stick far better than reading definitions.

When you are ready to build a full study plan around all eight domains, start with our Terraform Associate overview guide and map out your timeline with the study planner. To pressure-test your understanding of HCP Terraform and the rest of the syllabus, work through our practice exams.