HCP Terraform's Legacy Free Tier Ends March 31 as IBM's Post-Acquisition Commercialization Accelerates an IaC Ecosystem Shift
HashiCorp's March 31 deadline to kill its legacy free plan is pushing developers toward OpenTofu, Pulumi, and self-hosted alternatives as IBM's ownership tightens access to once-free tools.
Overview
On March 31, 2026, HashiCorp will retire its legacy HCP Terraform Free plan, automatically migrating remaining users to an enhanced free tier with tighter resource limits and operational constraints. The change is the latest in a series of access restrictions that have accelerated since IBM completed its $6.4 billion acquisition of HashiCorp in February 2025 — and it is reshaping the infrastructure-as-code landscape in real time.
What Is Actually Changing
The legacy free plan being discontinued was user-based and historically constrained organizations to five active team members. The enhanced free tier that replaces it is usage-based: it covers up to 500 managed resources with unlimited users and one concurrent Terraform run. For some teams — particularly small ones collaborating across many people — the switch may actually reduce friction. For others, particularly those managing large infrastructure footprints on a zero-cost basis, the implications are more complex.
According to HashiCorp’s official announcement, organizations still on the legacy plan as of March 31 will be transitioned automatically. HashiCorp has emphasized that this represents a continuation of free access, not an outright elimination. The enhanced tier was first introduced in May 2023 alongside a broader pricing restructure.
However, the transition is non-reversible once triggered. Organizations that opt to migrate early cannot return to the legacy plan. And beyond the free tier, paid plans have shifted to a per-resource model: the Essentials tier runs $0.10 per managed resource per month, Standard costs $0.47, and Premium reaches $0.99. A deployment managing 5,000 resources — a common footprint for mid-size engineering teams — costs approximately $2,450 monthly under Standard pricing.
The IBM Effect
The timing matters. IBM completed its acquisition of HashiCorp in February 2025 for $6.4 billion, integrating the company’s infrastructure automation tooling — Terraform, Vault, Consul, and others — into IBM’s hybrid cloud portfolio. The rationale was straightforward: nearly 75 percent of enterprises operate hybrid cloud environments, and HashiCorp’s tooling provided critical automation capabilities that IBM lacked natively.
But the acquisition has produced a visible pattern: features that were once freely available are being systematically placed behind paywalls or subject to new access controls. The legacy free tier discontinuation is the most recent signal of this, following HashiCorp’s controversial 2023 license change for Terraform from the Mozilla Public License to the Business Source License (BSL), which restricts certain commercial uses.
OpenTofu’s Position
The 2023 license change that alarmed the open-source community prompted the creation of OpenTofu, a community fork of Terraform now housed under the Linux Foundation’s Cloud Native Computing Foundation. OpenTofu uses the MPL 2.0 license — fully open-source — and maintains near-complete compatibility with Terraform’s HCL configuration language and provider ecosystem.
As reported by InfoQ covering OpenTofu 1.10’s release, the project has grown to approach 20 million total downloads, with major enterprises including Oracle and German insurer Allianz having formally adopted it. OpenTofu 1.10 introduced native OCI registry support for distributing providers and modules, native S3 state locking without requiring DynamoDB, and an MCP server enabling AI coding assistants to generate accurate infrastructure configuration. The project’s 1.11 release followed in December 2025, adding ephemeral resources — values that exist only in memory during an operation and are never written to state files — addressing a longstanding security concern for teams working with temporary credentials.
The project’s governance structure is a deliberate counterpoint to HashiCorp’s trajectory. As The Register has documented, the Terraform-OpenTofu split created two meaningfully different bets on the future of infrastructure automation: one backed by enterprise resources and IBM’s distribution network, the other by community governance and an explicit open-source commitment.
Pulumi’s Strategic Move
A third option has recently sharpened its pitch. Pulumi, which allows teams to write infrastructure configuration in general-purpose languages like TypeScript, Python, and Go rather than HashiCorp Configuration Language, announced in January 2026 that it would add native support for Terraform and HCL directly within its platform. The feature set, currently in private beta ahead of a Q1 2026 general availability release, allows teams to maintain existing HCL codebases while using Pulumi Cloud as their state backend — competing directly with HCP Terraform.
Pulumi has also introduced a credit program allowing organizations with remaining HashiCorp contracts to apply that value toward Pulumi usage, an explicit effort to reduce switching costs for teams considering migration. CEO Joe Duffy has framed the move in pragmatic terms: the company sees market demand and is responding accordingly.
For teams evaluating alternatives, self-hosted orchestration via GitHub Actions or GitLab CI with remote state in S3 remains a viable zero-cost path. Open-source tools like Atlantis (a Terraform pull request automation server) provide GitOps workflows without SaaS dependencies, though they require teams to own their own operational overhead.
What Organizations Should Consider
For teams currently on HCP Terraform’s legacy free plan, the March 31 deadline creates a concrete decision point. The enhanced free tier may be sufficient for small projects with fewer than 500 managed resources, particularly if the user-count constraints of the legacy plan were a source of friction. For larger infrastructure footprints or teams relying on multiple concurrent runs, the new pricing model may represent a material cost increase.
The broader question is not just about free tier access, but about the long-term trajectory of infrastructure tooling under IBM ownership. The license change, the free tier retirement, and the per-resource pricing model form a coherent picture of a company extracting commercial value from a developer ecosystem it acquired — a familiar pattern in enterprise software.
OpenTofu’s combination of Terraform compatibility, active development, and CNCF governance offers the clearest off-ramp for teams prioritizing open-source licensing. Pulumi’s native HCL support, once generally available, may lower the barrier for teams that want cloud-hosted state management without HSB lock-in.
What We Don’t Know
HashiCorp has not clarified what happens to state files for organizations that fail to migrate before the March 31 deadline. State files, which track the current configuration of all managed resources, are critical assets — their loss or inaccessibility would be a severe operational disruption. The company’s official end-of-life notice states that remaining organizations will be “automatically transitioned to the enhanced Free tier,” but the details of that transition, and what protections exist for state data during the process, have not been fully documented publicly.
It also remains unclear whether IBM’s integration strategy will ultimately push Terraform deeper into its enterprise stack — making it more capable but further from its open-source roots — or whether the combination of licensing, pricing, and acquisition concerns will continue accelerating the fragmentation of the IaC market.