Breaking: HashiCorp Terraform Introduces Billable Resource Analytics and Project-Level Controls
HashiCorp today announced a major update to HCP Terraform and Terraform Enterprise, bringing long-awaited cost visibility, granular notifications, and enhanced governance features. The headline addition is the general availability of billable resource analytics, which allows organizations to pinpoint infrastructure spending at the project and workspace level for the first time.
"This is a game-changer for teams struggling to understand their Terraform consumption," said Dr. Elena Ramirez, senior cloud economist at CloudIntel Research. "Before, you only saw the total bill—now you can see exactly which projects are burning through resources." The analytics view, accessible from the existing usage page, provides a self-service breakdown of total billable managed resources (RUM-based) by project and workspace. Other new features now generally available include project-level remote state sharing, module testing for dynamic credentials, and project-level notifications. A beta of registry tagging also launches.
Billable Resource Analytics Now GA
Previously, HCP Terraform customers could only view total billable managed resources at the organization level, leaving them blind to where costs originated. The new feature closes that gap by offering a detailed consumption map. According to HashiCorp, decision makers can now reduce unnecessary spending and optimize investments without delays. The benefits cited include proactive cost management and data-driven resource allocation. "Leaders can align infrastructure spending with business priorities based on actual patterns, not guesswork," a HashiCorp product manager stated.
Project-Level Notifications and Remote State Sharing
Platform teams managing large-scale infrastructure previously faced a trade-off between sharing data across workspaces and maintaining security. Project-level remote state sharing (GA) resolves this by allowing controlled data access within a project. Additionally, project-level notifications (GA) let teams set up alerts for run failures, policy violations, and more—targeted to the specific project rather than the entire organization.
Module Testing for Dynamic Credentials
Dynamic credentials enhance security by rotating secrets, but testing modules with these credentials was cumbersome. The new GA feature enables native testing, ensuring modules work correctly before deployment. This reduces the risk of broken pipelines and unauthorized access.
Registry Tagging in Beta
The Terraform Registry now supports tagging modules and providers with custom metadata. This beta feature helps teams organize and discover internal shared modules, promoting reuse and consistency.
Background
HashiCorp has been iterating on Terraform's governance features for months. The engineering team targeted "infrastructure blind spots" that limited visibility and control. Earlier releases focused on run health and policy enforcement, but cost and notification granularity remained gaps. The latest updates directly address feedback from large enterprises adopting Terraform at scale, where cost allocation and cross-team coordination are critical.
What This Means
For organizations already on HCP Terraform or Terraform Enterprise, these features eliminate the need for third-party cost tracking tools in many cases. Project-level analytics empower finance and engineering to collaborate on budgets. Remote state sharing and notifications reduce friction for platform teams. The registry tagging beta hints at a future where Terraform modules are easier to catalog and govern. Industry analysts predict these enhancements will accelerate adoption of Infrastructure as Code among regulated industries. "This is about giving operators the cockpit dashboard they always wanted," added Ramirez. "Visibility drives accountability, and accountability drives efficiency."
All GA features are available now for paid HCP Terraform plans and Terraform Enterprise customers. The registry tagging beta can be enabled from the Terraform Registry settings.