Terraform Cloud Pricing and Tiers Explained (2026)

HCP Terraform (the renamed Terraform Cloud, now an IBM product) bills per managed resource: $0.10 on Essentials, $0.47 on Standard, $0.99 on Premium per resource per month, with the first 500 resources free and self-managed Enterprise quote-only. SSO is free on every tier; audit logs start at Standard. Here's what each plan costs and gates as of June 2026, and where the renewal levers are.

What are the Terraform Cloud plans in 2026?

As of June 2026, HCP Terraform has five tiers: Free, Essentials, Standard, Premium, and Enterprise (the self-managed edition). The first four are SaaS; Enterprise is the self-hosted offering with custom pricing. Higher tiers add features by organization size: team management, audit logs, no-code provisioning, and continuous validation arrive as you move up.

Concurrency is capped per tier and covered below. HashiCorp doesn't publish the exact per-tier numbers on its pricing page, so they're not in the table. Policy as code runs on every tier, but Free is limited to a single policy set of up to five policies; higher tiers raise that and allow VCS-connected policy sets.

How much does Terraform Cloud cost?

HCP Terraform's pricing metric is the managed resource: each resource in your state files with type = managed costs a fixed amount per month. An AWS security group with 9 rules counts as 10 resources, whether or not you get value from each one. As of June 2026 the per-resource rates are Essentials $0.10, Standard $0.47, and Premium $0.99 per resource/month; Enterprise is quote-based.

Because the meter is resource count, the bill scales with the size of your infrastructure, not how often you deploy. At 1,000 managed resources that is roughly $470/month on Standard or $990/month on Premium; at 10,000 resources it is about $4,700 or $9,900/month. The first 500 resources are free, but in our experience teams pass that line quickly, which is why renewal quotes tend to climb year over year.

Can you use Terraform Cloud SSO without the Enterprise plan?

Yes. SSO/SAML carries no extra charge on any HCP Terraform plan, including Free, so you don't need the Enterprise plan, or any paid plan, to log in through Okta, Ping, or Entra ID. HashiCorp confirmed the enhanced Free tier still ships "SSO, policy as code (Sentinel + OPA), run tasks, and the HCP Terraform agents" in its December 17, 2025 announcement, and the position was unchanged as of August 2026.

What is gated to paid tiers is team-membership mapping through your identity provider, which starts at Essentials. So the split is: authentication is free, and mapping IdP groups onto Terraform Cloud teams is not. Teams that hit a real paywall usually wanted the second thing.

The pricing page doesn't help here. Its plan-comparison table lists no SSO or SAML row at all as of August 2026, and it shows no free card, only a $500 trial credit, which is a large part of why the belief that SSO requires Enterprise keeps circulating.

Which Terraform Cloud tier includes audit logs?

Standard and Premium. The Audit Trails API is available on Standard and Premium only, not on Free or Essentials, and not on self-managed Terraform Enterprise. If an append-only record of logins, permission changes, and run approvals is a compliance requirement, that places you on at least the Standard tier. (For what a complete audit trail should capture and why a current-state report is not enough, see our guide to Terraform audit logs.)

Does Terraform Cloud limit concurrent runs?

Yes. HCP Terraform caps the number of concurrent runs by tier, and any run beyond the cap queues until a slot opens. HashiCorp's support KB puts Free at 1 and Standard at 3; the Essentials and Premium figures aren't published, so confirm your plan's limit in the application rather than trusting a third-party number. The practical effect is familiar to active teams: runs back up during releases and incidents, exactly when you want them to move. Most teams work in one time zone and trigger runs at the same hours, so the cap bites everyone at once. We cover why this matters and how decoupled, agent-based concurrency avoids it in why Terraform concurrency matters.

Is Terraform Cloud worth it in 2026?

It depends on your resource-to-run ratio and how invested you are in the HashiCorp ecosystem, so there's no single verdict. Renewing tends to be the right call if you are under the 500-resource free tier and you rely on Sentinel or Vault, where first-party integration across HashiCorp products carries real weight. Pricing alternatives makes sense when your resource-under-management bill grew with your infrastructure even though your workflow did not, when concurrency caps are queuing your team, or when you want native OpenTofu support. Our 2026 renewal decision guide walks through renew, renegotiate, migrate, and open-source as four explicit paths.

How can I reduce Terraform Cloud costs at renewal?

There are three practical levers at renewal time. You can request to be grandfathered into your existing plan, which the community reports usually requires a longer contract term. You can try to negotiate resource exceptions so certain resource types do not count toward the billed amount. Or you can evaluate a per-run-priced alternative, where the bill tracks activity instead of resource count. Which lever pays off depends on how fast your managed-resource count is growing relative to your run volume.

How does Scalr compare?

Scalr's pricing metric is the run, not the resource: you pay for work performed instead of infrastructure under management. It is free up to 50 runs/month, then $0.99/run with volume discounts, and the Business plan starts at $99/month for 100 prepaid runs. Drift-detection runs, runs stopped by an OPA policy before plan, security-scan-stopped runs, and failed init runs are not billed.

Scalr doesn't put everything on every tier either. SSO/SAML, drift detection, unlimited policies, team management, no-code provisioning, and self-hosted agents are free on every plan. Audit logs, SCIM, bring-your-own storage and keys, and Control Tower aren't; they sit on Enterprise, much like audit logs sit above Essentials on HCP Terraform.

What usually decides a renewal is the meter, not the feature grid. Per-run cost is capped by how much you deploy. Per-resource cost grows with everything you manage, whether or not it changed. The side-by-side has the numbers.

If you want to model your own numbers, the Scalr pricing page shows the per-run tiers in full, and Scalr is built as a drop-in remote backend, so a typical migration is measured in minutes rather than weeks.

First written when HashiCorp announced per-resource pricing in 2023 and kept current since. Prices verified as of June 2026; SSO and tier-name facts re-verified against HashiCorp's pricing page on August 25, 2026. Have evidence that contradicts a figure here? Email us at [email protected] and we'll correct it.