OpenTofu — Trivia & Interesting Facts¶
Surprising, historical, and little-known facts about OpenTofu.
OpenTofu was created in 5 days as a response to HashiCorp's license change¶
When HashiCorp changed Terraform's license from MPL to BSL on August 10, 2023, the OpenTofu manifesto was published on August 15 — just 5 days later. Over 140 companies and 10 prominent projects signed the manifesto calling for Terraform to remain truly open source. When HashiCorp didn't reverse course, the fork proceeded.
The Linux Foundation adopted OpenTofu in record time¶
The Linux Foundation accepted OpenTofu as a project in September 2023, just weeks after the fork was announced. This rapid adoption signaled that major industry players — including Oracle, Cloudflare, Gruntwork, and Spacelift — viewed the fork as strategically important rather than a symbolic protest.
OpenTofu was originally going to be called "OpenTF"¶
The project was initially announced as "OpenTF" (Open Terraform), but HashiCorp's trademark on "Terraform" made the name legally problematic. The community voted on alternatives, and "OpenTofu" won — a playful name that references tofu's nature as a versatile, adaptable foundation that takes the flavor of whatever it's paired with.
OpenTofu forked from Terraform v1.6 and quickly diverged¶
OpenTofu forked from Terraform at version 1.6 and maintained backward compatibility while adding features that HashiCorp's Terraform didn't have. State encryption (encrypting the .tfstate file) was one of the first major OpenTofu-exclusive features — a capability the Terraform community had requested for years without HashiCorp implementing it.
The fork split the Terraform provider ecosystem¶
Terraform's power comes from its providers (AWS, Azure, GCP, etc.), which are maintained separately from the core. OpenTofu uses the same Terraform Registry providers, creating an unusual situation where provider authors support both tools simultaneously. The provider protocol compatibility was a deliberate design decision by the OpenTofu team.
HashiCorp accused OpenTofu of copying code, OpenTofu denied it¶
In April 2024, HashiCorp sent a cease-and-desist letter accusing OpenTofu of copying BSL-licensed code. OpenTofu's team conducted an internal review and denied the accusation, stating that the disputed features were independently implemented. The dispute highlighted the legal complexities of forking a project when the original continues to develop.
State encryption was OpenTofu's first "killer feature"¶
Terraform state files contain sensitive information (resource IDs, connection strings, sometimes passwords) in plaintext. The community had requested state encryption for years. OpenTofu made it a priority feature, supporting client-side encryption of state files with multiple key providers. This feature alone motivated some teams to switch from Terraform.
OpenTofu is governed by a steering committee, not a single company¶
Unlike Terraform, which was controlled by HashiCorp's product decisions, OpenTofu is governed by a steering committee with representatives from multiple companies. This distributed governance model was a direct response to the community's frustration with HashiCorp making unilateral decisions about a project that thousands of companies depended on.
The migration from Terraform to OpenTofu is designed to be trivial¶
OpenTofu deliberately maintains near-100% compatibility with Terraform configurations. Migration typically requires changing the binary name from terraform to tofu and optionally updating provider lock files. This low-friction migration path was a strategic decision to make switching as painless as possible.