The licensing and acquisition risk
IBM purchased HashiCorp for $36 per share, a figure much lower than the $80 IPO price. This acquisition creates uncertainty regarding the future of the Terraform BSL v1.1 license. I see a primary risk in how IBM reconciles HashiCorp products with its own competing software. IBM might revert Terraform to an open license to support the OpenTofu project. This transition would move the tool to the MPL 2.0 license that the OpenTofu community uses. OpenTofu is a production-ready project under the Linux Foundation that grew from four months of development by over five dozen developers. The 1.6 release includes advanced testing features and an enhanced S3 state backend with new authentication methods. Upcoming versions like 1.7 aim to introduce parameterizable backends, providers, and third-party extensibility with a plugin system for new state backends. The OpenTofu community continues to grow with dozens of developers and thousands of Github followers.
| Tool | License | Primary Language |
|---|---|---|
| Terraform | BSL v1.1 | HCL |
| OpenTofu | MPL 2.0 | HCL |
| Pulumi | Apache 2.0 | Python, Go, etc. |
The provisioning tool rivalry
The competition between Terraform and Pulumi intensifies as teams evaluate different approaches to infrastructure. Pulumi holds the third rank in 2026 provisioning tools because its use of general-purpose languages like Python and Go introduces architectural complexity. You should watch for how Pulumi’s flexibility leads to non-idempotent logic or a junior developer’s for-loop that provisions 400 unintended resources. Terraform remains the standard. HCL is limited. The current pricing model for Pulumi’s team tier includes 150,000 free credits per month before charging $0.0005 per credit, and this makes it harder to forecast at scale than the flat per-resource pricing used by Terraform. Terraform’s HCP tier covers 500 managed resources for free. Pulumi’s individual tier provides 500 deployment minutes per month for free. Terraform also offers a massive provider ecosystem for managing AWS, GitHub, and DNS records. Pulumi provides IDE support through type checking, inline documentation, and refactoring tools in VS Code. Crossplane offers a fundamental shift. By using Kubernetes control loops, Crossplane avoids the need for a separate state file. Platform teams use Crossplane to create Composite Resource Definitions that turn low-level cloud resources into high-level abstractions. Developers use Claims to request resources against those abstractions. The continuous reconciliation model in Crossplane reduces configuration drift.
Corporate instability and integration
IBM faces internal turmoil following the RAs in June 2026. Employees use the term "RAs" instead of layoffs to avoid meeting legal requirements. I see reports of management telling employees to stop all non-essential personal spending as layoffs hit US teams. These layoffs often result in moving jobs to India to manage costs. IBM’s acquisition strategy differs from its acquisition of Red Hat because Red Hat operates fairly independently within the company. IBM struggles to unify HashiCorp tools into a cohesive platform while it manages these workforce reductions. Some HashiCorp products compete directly with IBM’s own offerings, which creates reconciliation challenges. I see difficulty in how IBM handles its broad portfolio while it tries to become a hybrid cloud powerhouse. The law firm Sanford Heisler Sharp McKnight is investigating IBM for potential retirement plan mismanagement and violations of employee rights regarding mass layoffs. Will IBM successfully integrate these tools while its leadership deals with accusations of corruption?
