Somebody on the platform team is going to open every state file before this renewal and count the entries where `mode = "managed"`, because that string is the billing unit now [5]. What teams tell themselves is that the count tracks the size of the estate. What the count actually tracks is module style. A security group with fifty rules is one object in the AWS console and 51 managed resources in HCP Terraform [7], which at the Premium rate of $0.99 works out to $50.49 a month for something AWS charges nothing for [2][1].
The hour is the unit and the peak inside the hour sets the price [3]. In the example Spacelift walks through, 500 resources created and 200 destroyed inside the same hour bill at 700, which is 40 percent above what still exists when the hour closes [4][4]. Partial hours round up, so short-lived test infrastructure bills as though it stayed [3].
HashiCorp's own worked example, quoted in the post, is $97.85 for 1,000 resources running non-stop through a 30-day month on Essentials [9]. That comes to about $0.000136 per resource-hour, which means the $0.10 headline is priced against a 730-hour month, and the calendar does the rest: a 31-day month costs roughly 3 percent more [5][10]. Trivial on a small estate. On a 10,000-resource Premium footprint at $9,900 a month [6], 3 percent is close to $297, and the annual run rate is $118,800 [6][2].
The $0.10 tier is also not available to everyone who wants it. An audit trail starts at Standard [15], so a team carrying a compliance obligation is really pricing at $0.47 per resource, 4.7 times the headline figure [2][7]. A free tier does still exist at 500 managed resources, though it lives in the FAQ rather than on the pricing page [13], and the $500 of trial credits given to new organisations expires in six months [14].
Spacelift, which sells a competing runner priced on concurrency [19], says renewal season is the only time you have leverage with a vendor [20]. Separate the leverage claim from the pricing claim. Since HashiCorp published per-tier list prices in February 2026 [11], the counting and multiplying no longer require a sales call, so anyone can price the term today. What renewal still controls is paper, which is why the per-resource rate, the overage rate and the concurrency cap belong in the contract rather than in a rep's reassuring email [18].
The forcing function is two columns. Column one holds resources a customer would notice if they vanished. Column two holds resources that exist because Terraform models them as resources. Multiply column two by your tier rate and look at what share of the bill it is. If column two is large, the invoice is tracking how your team writes modules rather than what you actually run, and cleanup stops being hygiene and becomes a funded project with a date on it. If column one dominates and your pipelines are quiet, inventory pricing is the honest model for your shape, and a concurrency-priced runner would charge you for pipeline capacity you do not use. The tradeoff inverts for teams with heavy plan and apply churn over a small, stable estate.
