Home / Companies / Harness / Blog / Post Details
Content Deep Dive

Terraform License Change: BSL vs Open Source Guide

Blog post from Harness

Post Details
Company
Date Published
Author
Richard Black All this author’s posts
Word Count
1,983
Company Posts That Month
13
Language
English
Hacker News Points
-
Post removed?
No
Summary

HashiCorp's transition of Terraform from the Mozilla Public License v2.0 to the Business Source License has significantly impacted the Infrastructure as Code (IaC) community, highlighting the importance of licensing as a platform risk rather than a mere legal footnote. The change restricts Terraform's use in creating competing commercial services, forcing teams to reconsider their IaC strategies and sparking a fork of the last MPL-licensed version into OpenTofu, which is governed under the Linux Foundation. OpenTofu offers a clear, open-source alternative to Terraform, maintaining compatibility and continuity without legal ambiguity, while Terraform remains a strong option for teams with existing investments. This shift emphasizes the need for infrastructure teams to design resilient platforms that can adapt to future licensing changes, underscoring the operational challenges of balancing openness with commercial needs. Harness Infrastructure as Code Management (IaCM) supports both OpenTofu and Terraform, providing consistent workflows and governance to facilitate gradual transitions and reduce disruption, allowing organizations to navigate these changes effectively.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Kubernetes 13 1,390 242 97 -19%
Observability 2 3,277 563 170 +12%
Developer Experience 1 509 261 106 -11%
Platform Engineering 1 425 134 62 -24%
Secrets Management 1 1,271 215 97 -1%
Vector Search 1 2,057 332 133 +28%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.