IBM closed its $6.4 billion acquisition of HashiCorp on February 27, 2025, after the U.K. Competition and Markets Authority gave its approval. The transaction follows an announcement from April 2024 that IBM would buy HashiCorp for $35 per share in cash. This acquisition adds the suite of HashiCorp products to the IBM portfolio, including Terraform and Vault. IBM now manages the Terraform Cloud brand as IBM HCP Terraform. The deal followed regulatory reviews by the U.S. Federal Trade Commission and the U.K. Competition and Markets Authority.
The BSL 1.1 license creates legal uncertainty
The shift from the Mozilla Public License 2.0 to the Business Source License 1.1 in August 2023 changed the legal terms for developers. This license restricts commercial production use that competes with HashiCorp offerings. Any code released under BSL 1.1 converts to a GPL-compatible license exactly four years after its release date. The community responded to this change by forming OpenTofu under the Linux Foundation. OpenTofu uses the MPL 2.0 license to ensure permanent open-source status.
The BSL 1.1 is not open source by the definition of the Open Source Initiative. It is source-available, meaning users can read and modify the code for non-production purposes. However, the Additional Use Grant in the license forbids production use that competes with the commercial offerings of HashiCorp. Because the language in the license is ambiguous, many legal teams view it as a source of risk. You already know the frustration of managing legal compliance for core infrastructure tools. Will the community ever forgive the BSL change?
Unpredictable RUM pricing models
The Resources Under Management model calculates costs based on the highest number of managed resources during any sixty minute window. If a team provisions 2,000 resources at 3:05 pm and destroys 500 of them at 3:30 pm, the bill reflects the 2,000 resource peak. This peak-based billing makes budget forecasting difficult for teams with fluctuating workloads. IBM discontinued the Terraform Cloud Free tier in 2025. Every tier now relies on a $500 trial credit that users consume at the specific rate of their plan.
| Tier Name | Monthly Cost per Resource | Hourly Cost per Resource | Key Capabilities |
|---|---|---|---|
| Essentials | $0.10 | $0.00013 | Remote state, 3 concurrent runs, 1 self-hosted agent |
| Standard | $0.47 | $0.00064 | Drift detection, 10 concurrent runs, 10 self-hosted agents |
| Premium | $0.99 | $0.00135 | Private VCS, HYOK, 200 concurrent runs, 300 self-hosted agents |
For an organization with 500 resources, the $500 credit lasts 10 months on the Essentials tier. On the Standard tier, that credit lasts 2.1 months. On the Premium tier, the credit lasts only 1 month. The Essentials tier is limited because it does not include drift detection or audit logging. The Standard tier provides more tools but costs more per resource. The Premium tier is the most expensive option and costs $0.99 per resource monthly.
Visibility gaps in multi-tool environments
Terraform Cloud is only able to see resources that exist within its own state files. It is unable to detect resources created through the AWS or Azure consoles. It also lacks visibility into infrastructure stacks that use Pulumi or CloudFormation. This creates a governance gap where security teams believe they have full coverage but miss unmanaged infrastructure.
A fintech platform team runs Terraform for core infrastructure and Pulumi for application stacks. When a security audit finds EC2 instances from the Pulumi stack, Terraform Cloud shows 100% compliance because it cannot see the Pulumi resources. The dashboard only shows the status of the workspaces that the team explicitly manages in Terraform. This blindness to out-of-band changes makes it difficult to maintain a true inventory of all cloud assets.
Technical constraints and feature gating
The Essentials tier is designed for small teams but it has significant limitations. It includes only three concurrent runs and one self-hosted agent. It also limits users to one policy set with five policies, and only one of those policies can be mandatory. The Standard tier adds drift detection and audit trails but still lacks the advanced security of the Premium tier. The Premium tier is required for private VCS access and custom deployment groups called Stacks.
The platform has other technical hurdles for large organizations. Workspace dependencies do not exist natively in the tool. Teams must use workarounds like remote state data sources or external secrets managers to pass outputs between different workspaces. This makes the orchestration of complex, multi-tier infrastructure difficult. The execution environment is also rigid. Users cannot bring their own runner images or inject custom tooling into the execution pipeline. They are limited to using the run tasks that the platform provides.
OpenTofu as a functional alternative
OpenTofu is a viable alternative for teams that want to avoid the BSL 1.1 license. It is a fork of Terraform that remains under the MPL 2.0 license. The project is governed by the Linux Foundation and is not controlled by a single vendor. It maintains command compatibility for terraform init, terraform plan, and terraform apply.
OpenTofu provides several features that the standard Terraform version does not. It provides native end-to-end encryption for state files. This feature is useful for teams that need to protect sensitive data in state files without a dependency on Vault. OpenTofu also allows variables and locals within terraform blocks and module sources. The version 1.12 release arrived in May 2026. The tool is a drop-in replacement for most users who use HCL.
Competition from Spacelift and ControlMonkey
Spacelift and ControlMonkey provide different ways to manage infrastructure. Spacelift is an orchestration platform that supports multiple frameworks. It works with Terraform, OpenTofu, Pulumi, and Ansible. It allows users to define dependencies between stacks and pass outputs between them. It also provides policy enforcement through Open Policy Agent.
ControlMonkey is a governance and resilience platform. It scans cloud accounts to build a real-time inventory. It can identify resources that are unmanaged or drifted. It also converts existing cloud resources into Terraform or Pulumi code. ControlMonkey detects drift against live provider state rather than just comparing state files. This makes it more effective for catching changes made in a cloud console.
The decision to migrate or stay
The decision to move away from Terraform depends on the specific needs of the infrastructure stack. If a team uses only AWS, CloudFormation or the AWS CDK is a low-risk option. These tools have no licensing fees and provide day-one support for new AWS services. The state is managed by AWS, so there is no need for manual backend configuration.
For teams that use HCL and want to avoid the BSL 1.1 license, OpenTofu is the most direct path. The migration is simple because the syntax and provider ecosystem are the same. For teams that need to manage multiple different tools, Spacelift is a stronger choice. The most effective way to avoid the costs and legal risks of the IBM acquisition is to move to OpenTofu or native cloud tools.
