Skip to main content

Menu

LEVEL 0
0/5 XP
HomeAboutTopicsPricingMy VaultStats

Categories

πŸ€– Artificial Intelligence
☁️ Cloud and Infrastructure
πŸ’Ύ Data and Databases
πŸ’Ό Professional Skills
🎯 Programming and Development
πŸ”’ Security and Networking
πŸ“š Specialized Topics
HomeAboutTopicsPricingMy VaultStats
LEVEL 0
0/5 XP
GitHub
Β© 2026 CheatGridβ„’. All rights reserved.
Privacy PolicyTerms of UseAboutContact

OpenTofu Open-Source Terraform Fork Cheat Sheet

OpenTofu Open-Source Terraform Fork Cheat Sheet

Back to DevOps
Updated 2026-05-22
Next Topic: Platform Engineering Cheat Sheet

OpenTofu is a community-driven, MPL 2.0-licensed fork of Terraform created in September 2023 after HashiCorp relicensed Terraform under the restrictive Business Source License (BSL). Governed by the Linux Foundation and accepted into the CNCF Sandbox in April 2025, it is the open-source answer to the question of who controls the future of Infrastructure as Code. The project uses the tofu binary with a CLI workflow nearly identical to Terraform's, but has diverged in meaningful ways β€” native state encryption, provider for_each, early variable evaluation, ephemeral resources, and OCI registry support are all OpenTofu-only features. The key mental model: OpenTofu and Terraform share the same HCL language and provider protocol but are now separately governed products, and the divergence grows with every release.

What This Cheat Sheet Covers

This topic spans 16 focused tables and 151 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.

Table 1: Origins, Governance, and LicensingTable 2: Installation MethodsTable 3: Core CLI CommandsTable 4: OpenTofu-Exclusive FeaturesTable 5: State Encryption ConfigurationTable 6: Backend Configuration and State ManagementTable 7: Providers and the OpenTofu RegistryTable 8: Import and Resource Lifecycle ManagementTable 9: Testing and Code QualityTable 10: Migration from TerraformTable 11: CI/CD and Automation Platform IntegrationTable 12: OpenTofu vs. Terraform Feature ComparisonTable 13: OpenTofu vs. Pulumi (IaC Tool Comparison)Table 14: Security Scanning for OpenTofu ConfigurationsTable 15: Common Pitfalls and Upgrade IssuesTable 16: OpenTofu Roadmap and Version History

Table 1: Origins, Governance, and Licensing

OpenTofu's founding story and governance structure explain why many organizations choose it over Terraform. Understanding the BSL vs MPL 2.0 distinction, and who controls the roadmap, is essential context before evaluating any technical feature.

ConceptExampleDescription
OpenTF Manifesto
Gruntwork, Spacelift, Harness, env0, Scalr co-authored the manifesto β€” Aug 2023
β€’ Coalition response to HashiCorp's BSL relicense
β€’ called for Terraform to remain open-source or be forked under a neutral foundation
Linux Foundation stewardship
Project moved under Linux Foundation β€” Sep 2023
β€’ Ensures vendor-neutral governance
β€’ no single company can unilaterally change licensing or roadmap direction
CNCF Sandbox acceptance
Accepted to CNCF Sandbox β€” Apr 23, 2025
β€’ Gives OpenTofu the same foundation that hosts Kubernetes and Prometheus
β€’ confirms long-term community commitment
MPL 2.0 license
License: Mozilla Public License 2.0 (OSI-approved)
β€’ Unambiguous open-source license
β€’ permits any use including building commercial products on top, with no "competing service" restriction
BSL 1.1 vs MPL 2.0
Terraform β‰₯ 1.6 β†’ BSL 1.1; OpenTofu all versions β†’ MPL 2.0
β€’ BSL restricts building competing hosted services using Terraform
β€’ MPL 2.0 has no such restriction β€” key for vendors and regulated sectors

More in DevOps

  • OpenTelemetry Observability Standard Cheat Sheet
  • Platform Engineering Cheat Sheet
  • AI-Powered DevOps Copilots and Agents Cheat Sheet
  • Configuration Drift Cheat Sheet
  • GitOps Cheat Sheet
  • Pulumi Programmatic IaC Cheat Sheet
View all 49 topics in DevOps