Summary
- HCP Terraform defines a managed resource at the state-file level and starts the count at the first plan or apply. The exclusions, the partial-hour rule, the hourly peak and the cross-organisation sum are all printed on pages a customer can quote.
- The same unit is priced three ways: a $0.10 per month card footnoted at $0.00013 an hour, a Flex table headed Standard Edition that zero-rates the first 500 resources and charges $0.0001359 for 501–1,000, and an Essentials worked example that charges all 1,000 at $0.0001359. On my arithmetic those readings of 1,000 resources sit a factor of two apart.
- None of the eight documents read for this piece states which of the three governs an Essentials pay-as-you-go organisation, or which document takes precedence.
The unusual thing about this bill is not the number. It is the paper behind it.
Open HashiCorp's page for HCP Terraform subscription plans and the counting rule is there in prose you can carry to a meeting. The defining sentence reads: "A managed resource is a resource in an HCP Terraform-managed state file", and the attribute that makes it billable is the one printed beside it, mode, set to managed. The clock starts not at signup or at the invoice date but, in the page's words, "from the first terraform plan or terraform apply operation on the resource."
That is rarer than it should be. The population being billed is a file the customer wrote, and the attribute that decides whether an object belongs to that population is printed in the same breath as the object.
What does not count, and what counts more than once
The exclusions are printed too, which is the part most vendors leave to a support ticket. null_resource and terraform_data do not count. Neither do data sources where the mode attribute reads data, nor local values and variables. What does count: every instance created by the count and for_each meta-arguments, counted separately, plus resources provisioned by modules and no-code ready modules. A module that wraps twenty resources for tidy code is twenty billable resources, not one tidy thing.
The companion page on workspace state supplies the mechanics in a single sentence: "HCP Terraform reads all the workspaces' state files to determine the total number of managed resources." Workspace and Stacks resources are combined in the same calculation, the plans page adds. So the estate is not a workspace inventory. It is a state-file inventory gathered across both surfaces.
The observation is the hour's peak
The definition is half the audit. The other half is when the count is read, and that sentence is printed as well: "Each partial hour is billed as a full hour. The peak number of managed resources in a given hour determines the cost for that hour." Charges run per managed resource per hour, from provisioning until destruction.
A resource that exists for four minutes in an hour whose peak is 1,000 costs the same as one that exists for the full sixty, and a resource destroyed before the peak may never appear on the bill at all. Churn inside an hour is not what costs money. Concurrency at the peak is.
The boundary is printed with equal care. HashiCorp's HCP billing definitions define Hourly Peak Managed Resources as "The sum of the maximum number of concurrent "Managed Resources" of each HCP Terraform Org that exist in an hourly billing period." Read that twice. The metric does not measure the peak of the combined estate. It sums each Terraform Org's own maximum across every Org linked to one HCP org.
On my arithmetic — mine, not HashiCorp's — the billed figure is therefore at least the peak the whole estate actually shared, and can exceed any single instant that all the linked Orgs held in common. Splitting workspaces into more Terraform Orgs inside one HCP org cannot lower that sum, and if the Orgs peak at different times it raises it.
The same page keeps the reading honest about its own age: usage and costs accrue from the start of the month, update hourly, carry up to a thirty-minute delay, and remain estimates until the statement is finalised. You are not auditing a ledger. You are auditing a running estimate that becomes one.
Where the free tier stops
The Free plan is bounded at 500 managed resources, and the bound is printed three ways on one page: "Free organizations are limited to 500 managed resources", "Up to 500" in the plan table against "Unlimited" for the paid plans, and "Free plan: No charge for up to 500 managed resources." The December 2025 announcement of the enhanced free tier restates the allowance and dates the end of the legacy user-based Free plan to 31 March 2026.
What happens to a Free organisation that grows past 500 is not on those pages. The only printed consequence sits on the plan management page: verify 500 or fewer managed resources before downgrading, "Otherwise, you won't be able to downgrade." That is a gate on the way back, not a rule about the way through. A reader who assumes the one sentence covers the other is assuming.
And then the price
Here the paper stops being tidy.
HashiCorp's public pricing page prints three cards. Essentials: "Starting at $0.10 per month per resource", footnoted "*Rated hourly at $0.00013 per hour". Standard: $0.47 per month per resource, $0.00064 an hour. Premium: $0.99 per month per resource, $0.00135 an hour.
The Flex pricing table and terms, effective 1 July 2025, print a banded ladder under the heading "Table 1(a): Resource Under Management (RUM) Standard Edition Pricing (per hour per managed resource)". Its first band, "First 1-500", reads $0.0000000 under both Silver Support and Gold Support. The next, "Next 501-1,000", reads $0.0001359 and $0.0001418. From there the rate declines through seven more bands to 1,000,001+ at $0.0000113 and $0.0000118.
The developer page on estimating HCP Terraform cost prints a worked example headed "HCP Terraform Essentials plan with 1,000 managed resources": "1,000 managed resources × $0.0001359 = $0.14" per hour, and "$0.14 × 24 hours × 30 days = $97.85" per month. The same page walks a three-hour peak sequence — 1,000 resources for $0.14, a peak of 2,000 for $0.27 and a running total of $0.41, a peak of 1,500 for $0.20 and $0.61 overall — and calls the example illustrative and undated.
Three documents. Three labels for what a buyer would reasonably call one product. Two methods for applying one rate: charge all of it, or charge only the part above the zero-rated band.
The arithmetic, labelled mine
HashiCorp's example multiplies out cleanly. $0.0001359 × 1,000 = $0.1359 an hour, rounding to the printed $0.14; × 720 hours gives $97.848, rounding to the printed $97.85. The month in that example is 720 hours, not 730 — a convention the page uses without naming it.
Now the same 1,000 resources at the same rate, read the way the Flex ladder reads. Five hundred resources at $0.0000000 plus five hundred at $0.0001359 is $0.06795 an hour, and $48.92 over the same 720 hours. Divide one figure by the other and you get 2.0002. Two readings of one quantity at one rate, a factor of two apart.
The 501st resource is where the split becomes visible. On the ladder reading it adds one billable unit at $0.0001359 for 720 hours, which is under ten cents a month. On the flat reading, moving from 500 resources to 501 adds 501 billable units at the same rate: $0.0680859 an hour and $49.02 a month. One resource, two printed methods, two answers five hundredfold apart.
The pricing page's own card has a third behaviour. $0.10 ÷ $0.0001359 = 735.8 hours, so the Essentials monthly figure reconstructs from the worked example's rate at roughly a 720-hour month. $0.10 ÷ $0.00013 = 769.2 hours, so it does not reconstruct from the card's own footnote at any ordinary month. Standard and Premium behave the other way round: $0.47 ÷ $0.00064 = 734.4 hours, and $0.99 ÷ $0.00135 = 733.3, both close to a 730-hour month. The worked example's rate sits 4.5 percent above the Essentials footnote on the same product line.
One more, because it shows how far the ladder travels: at the top band, 1,000,000 resources × $0.0000113 = $11.30 an hour, and the fall from $0.0001359 to $0.0000113 across nine bands is a factor of about twelve.
What none of the eight documents says
Set out plainly, this is what the eight pages read on 21 November 2026 do not supply. No precedence rule among the pricing page, the Flex table and the worked example. No statement of which rate card or which first-500 treatment governs an Essentials pay-as-you-go organisation. No statement whether the Flex table's Standard Edition heading is meant to include or exclude Essentials. No statement of what happens to a Free organisation that grows past 500 beyond the bar on downgrading. No statement whether $0.0001359 is the current general Essentials rate or a figure used for illustration.
And no governing contract term that would unify the three presentations into one.
That is a narrow absence, and it should stay narrow. These pages print a great deal, and the counting rule is not in doubt. What is in doubt is which rate card a given buyer is standing on, and the eight documents do not answer for them. The directory record for HashiCorp is where the company's other coverage sits.
What precision on the unit entitles you to demand
An operator that defines the population to the attribute, names the event that starts the clock, prints the exclusions, prints the peak rule, prints the aggregation boundary and warns that the running figure is an estimate has done the hard half. It has made the quantity legible.
That legibility raises the standard for the other half. If I can rebuild the count from my own state file, I should be able to point at one rate card, dated, and say this is the one my organisation is billed under; here is the rate for my plan, my tier and my support level; here is what happens to my first 500 resources under this billing method and not another; here is why the monthly card and the hourly footnote agree to the hour; and here is the clause that decides which document wins when two of them speak.
None of that is an exotic demand. Each item is a field a customer could fill in from one versioned page.
The count is auditable. The invoice is not — not yet, and not from these eight pages.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






