IBM’s ownership of Terraform and Vault has moved past the announcement phase and into the phase that actually matters to buyers: renewal quotes, tier restructuring, and product retirements. IBM closed its $6.4 billion acquisition of HashiCorp on February 27, 2025, after clearing both UK and US antitrust review, and organisations running Terraform, Vault, Consul, or Nomad in production are now living with the commercial consequences of that closing rather than speculating about them.
What Has Actually Changed Since Closing
The most visible change so far has been branding and packaging rather than a single dramatic price shock. Effective September 1, 2025, HashiCorp’s business operations formally transitioned to IBM, with product names updated to align with IBM’s Automation portfolio and billing statements reflecting the new naming. IBM has been explicit that no features or functionality changed as part of that rename, but the administrative shift is a visible marker of a broader integration process still working through IBM’s commercial systems.
Underneath the rebranding, the free tier for HCP Terraform has been steadily narrowed. The legacy user-based free plan reached end of life, terraform import was restricted to paid tiers in January 2026, and per-tier pricing was formally published in February 2026. None of these changes happened as a single announced price increase. Each arrived as a smaller, separately timed adjustment, which is precisely the pattern worth watching for at the next renewal rather than assuming the current terms are stable.
What Terraform Actually Costs Today
HCP Terraform’s commercial structure is built around Resources Under Management rather than users, which means cost scales with infrastructure footprint regardless of team size. Current published pricing runs Essentials at ten cents, Standard at forty seven cents, and Premium at ninety nine cents per managed resource per month, with a free tier covering up to five hundred resources. Self-hosted Terraform Enterprise remains quote-based rather than published, which keeps that segment of pricing squarely in negotiation territory rather than list-price territory.
The practical implication for any organisation running Terraform at meaningful scale is that resource count, not user count, is the number worth tracking closely ahead of a renewal. An estate that has grown its managed resource count significantly since the last commercial conversation, whether through genuine infrastructure growth or simply more thorough tagging and discovery, may find itself facing a considerably larger bill at the next tier boundary than the prior year’s budget assumed.
Vault’s Cost Structure Is Even Less Transparent
Vault Enterprise carries no public price list at all, with commercial terms built around client count, cluster configuration, replication, premium modules, support tier, and contract length, all negotiated individually. HCP Vault Dedicated does publish some figures, with production tiers running from roughly one and a half to over nine dollars per cluster hour depending on size, plus per-client charges layered on top.
One detail worth flagging directly for any organisation currently on HCP Vault Secrets: that product has been sunset, with end of sale in mid-2025 and full end of life in July 2026, pushing existing customers toward HCP Vault Dedicated or the self-hosted Community Edition. Any Vault Secrets customer who has not already begun that migration is working against a deadline that has already passed the point of comfortable planning time.
The License Change That Predates IBM but Still Shapes Everything
It is worth separating what IBM has changed from what HashiCorp itself changed before the acquisition closed. The shift from the Mozilla Public License to the Business Source License happened in August 2023, well before IBM’s involvement, and that licensing change is what created OpenTofu, the community fork that retained the open source MPL license. IBM inherited the BSL structure rather than creating it, but IBM’s ownership is what determines how that structure evolves from here, including whether IBM ever considers reverting to a more permissive licence.
Industry commentary on this point has been split. Some analysts argue IBM’s broad consulting-driven revenue model, rather than a SaaS-first one, gives it less pressure to monetise Terraform and Vault aggressively than HashiCorp faced as an independent company. Others point to IBM’s post-acquisition history with Red Hat, where subscription requirements were introduced for Red Hat Enterprise Linux, as a more cautionary precedent for what could eventually happen to Terraform and Vault’s remaining free tiers.
Why Some Customers Are Already Moving
The uncertainty has translated into measurable customer movement rather than remaining a purely theoretical concern. OpenTofu, the open source Terraform fork, reported roughly three hundred percent annual download growth since the BSL change, reaching close to ten million downloads, and industry surveys have found a meaningful share of Terraform users actively evaluating alternatives rather than waiting to see how IBM’s ownership plays out. That evaluation activity is itself a useful data point for any organisation currently negotiating a HashiCorp renewal, since it strengthens the credibility of citing a viable alternative during commercial discussions.
The Talent Question Behind IBM’s Investment
One detail worth weighing alongside the pricing uncertainty is what IBM’s resourcing decisions suggest about its actual commitment to the products rather than just its public statements. Community discussion following the acquisition has pointed to a genuine expansion in engineering headcount dedicated to Vault and Terraform under IBM, with public job postings suggesting meaningfully more investment than HashiCorp could sustain as an independent company of its prior size. That kind of resourcing signal is a reasonable, if imperfect, proxy for how seriously IBM intends to keep developing the platform rather than simply harvesting existing revenue from it.
It does not resolve the pricing uncertainty directly, but it does suggest that customers weighing whether to stay on Terraform and Vault or migrate to an alternative are not choosing between a well-invested platform and a neglected one. Both paths currently carry genuine ongoing development, which shifts the decision back toward commercial terms and licensing philosophy rather than a concern about the product being abandoned.
The Consulting Revenue Model Argument
One recurring argument in analyst commentary deserves direct attention because it cuts against the more pessimistic reading of IBM’s incentives. IBM’s revenue model, weighted heavily toward consulting and services rather than pure software licensing, is structurally different from HashiCorp’s own SaaS-first business before the acquisition. A company earning the bulk of its revenue from implementation and advisory services around infrastructure automation has less immediate pressure to monetise the underlying tooling as aggressively as a company whose entire revenue depended on that tooling’s own subscription fees.
That argument should not be taken as a guarantee of continued generosity, since IBM’s Red Hat history shows the same parent company introducing subscription requirements where none previously existed. It is, however, a genuinely different starting incentive structure than HashiCorp faced independently, and it is worth weighing as one input among several rather than dismissing outright.
What to Do Before Your Next Renewal
Organisations with an active Terraform or Vault relationship approaching renewal should start by getting a precise, current count of managed resources and Vault clients rather than relying on figures from the last commercial conversation, since both metrics tend to drift upward between renewals without anyone deliberately tracking the change. That current count is the single most useful piece of leverage in any renewal conversation, since it lets a buyer challenge a proposed tier or quote with real data rather than accepting IBM’s own usage estimate.
It is also worth confirming directly, in writing, what happens if managed resources exceed a plan’s stated cap, since HashiCorp’s own public documentation has been notably unclear on whether an organisation nearing the five hundred resource free tier limit will see runs blocked, queued, or simply billed without warning. Getting that answer before it becomes an operational surprise is considerably better than discovering it live.
Considering OpenTofu as a Genuine Parallel Path
For organisations with a genuinely adversarial relationship to the BSL licence change, or simply a strong preference for community-governed open source infrastructure tooling, OpenTofu deserves serious evaluation rather than dismissal as a fringe fork. Command compatibility with Terraform is high, the backing coalition includes credible infrastructure vendors, and the growth trajectory suggests a project with genuine staying power rather than a short-lived protest fork that fades once initial anger subsides.
The realistic assessment for most enterprise organisations is that a full migration away from Terraform carries genuine short-term cost and risk, even where OpenTofu is a credible long-term destination. Treating OpenTofu evaluation as a parallel workstream, tested on a defined subset of new infrastructure rather than a wholesale migration mandate, is a more measured response than either ignoring the option entirely or committing to full migration before the alternative has been proven at the organisation’s own scale.
Conclusion
IBM’s ownership of HashiCorp has not produced a single dramatic price shock in the way some early commentary predicted. It has produced a steady sequence of smaller changes, tier restructuring, free tier narrowing, product sunsets, and rebranding, that collectively add up to a materially different commercial position than the one many organisations negotiated their original HashiCorp agreements under.
Treating the next Terraform or Vault renewal as a genuine negotiation, backed by an accurate current resource and client count and a credible understanding of the OpenTofu and Vault alternative landscape, is the practical response to a vendor relationship that is still actively being reshaped a year after the deal closed.
