
This post is part of our series on Terraform Cloud. It was first written when HashiCorp announced per-resource pricing in 2023 and is kept current; the figures below are verified as of June 2026.
Terraform Cloud — renamed HCP Terraform and now part of IBM — bills on managed resources, and the tier you land on decides both your monthly cost and which features you can use. If you are evaluating a renewal, comparing plans, or just trying to work out why the quote went up, this is what each tier costs and gates today.
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.
| Capability (as of June 2026) | Free | Essentials | Standard | Premium | Enterprise (self-managed) |
|---|---|---|---|---|---|
| Per-resource price / month | $0 (≤500 resources) | $0.10 | $0.47 | $0.99 | Custom |
| SSO / SAML | ✓ | ✓ | ✓ | ✓ | ✓ |
| Team management / fine-grained RBAC | — | ✓ | ✓ | ✓ | ✓ |
| Audit logs (Audit Trails API) | — | — | ✓ | ✓ | — |
| No-code provisioning | — | — | ✓ | ✓ | ✓ |
| Policy as code (Sentinel / OPA) | ✓ (1 set, ≤5 policies) | ✓ | ✓ | ✓ | ✓ |
Concurrency is capped per tier and is covered separately below — HashiCorp does not publish the exact per-tier numbers, so it is not in the table.
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.
Every tier, including Free. SSO/SAML carries no extra charge on any HCP Terraform plan as of June 2026, so the common belief that you must be on Enterprise to use single sign-on is wrong. What is gated to paid tiers is team-membership mapping through your identity provider, which starts at Essentials. If your only requirement is logging in through Okta, Ping, or Entra ID, the Free tier already covers it.
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.)
Yes. HCP Terraform caps the number of concurrent runs by tier, and any run beyond the cap queues until a slot opens. HashiCorp does not publish the exact per-tier concurrency numbers on its pricing page as of June 2026, so confirm your plan's limit in the application rather than trusting a third-party figure. The practical effect is familiar to active teams: runs back up during releases and incidents — exactly when you want them to move — because most teams develop in the same time zone and trigger work at the same hours. We cover why this matters and how decoupled, agent-based concurrency avoids it in why Terraform concurrency matters.
Beyond audit logs, a few capabilities move up the ladder:
None of this is unusual packaging for a SaaS product. The point to weigh at renewal is whether the features you depend on day to day sit on the tier you are actually paying for.
It depends on your resource-to-run ratio and how invested you are in the HashiCorp ecosystem — there is no single verdict. Renewing is the right call when you are under the 500-resource free tier, lean on Sentinel or Vault, or value first-party integration across HashiCorp products. 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.
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.
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.
To keep the comparison fair: Scalr does not put everything on every tier. SSO/SAML is free on all plans — there is no SSO tax — and so are drift detection, unlimited policies, team management, no-code provisioning, and unlimited self-hosted agents. But audit logs, SCIM, bring-your-own storage and encryption keys, and Control Tower sit on Scalr's Enterprise tier, the same way audit logs sit above Essentials on HCP Terraform. The difference that tends to matter at renewal is the meter itself: per-run cost is bounded by how much you deploy, while per-resource cost rises with everything you manage. For a side-by-side breakdown, see Scalr vs Terraform Cloud pricing.
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.
Have evidence that contradicts a figure here? Email us at [email protected] and we'll correct it.
