🌱 Terraform has competition. OpenTofu enters the game

#terraform #devops #learning #linux

👋 New to Infrastructure as Code? Heard of Terraform and OpenTofu but not sure which one to use? Don’t worry — this post is for you!

Let’s break it down with a real-world example and explain why both exist, how they differ, and which one to pick.

🔍 What Are These Tools?

Both Terraform and OpenTofu help you define your cloud infrastructure as code.

Instead of clicking around the AWS console, you can write code like this:

resource "aws_s3_bucket" "my_bucket" {
  bucket = "my-dev-bucket"
  acl    = "private"
}

And BOOM 💥 — your bucket is created!

✅ Terraform and OpenTofu use the same syntax
✅ Both work with AWS, Azure, GCP, and more
✅ Both manage your infrastructure automatically

📖 Why OpenTofu Exists?

Terraform was 100% open-source — until 2023, when HashiCorp changed its license.

That new license (BSL) added restrictions on how Terraform could be used — especially for companies building tools on top of it.

So, the open-source community said:

"Let’s keep the freedom alive!" 🚀

They forked Terraform v1.5, kept it open-source, and created 👉 OpenTofu, now backed by the Linux Foundation.

🧑‍💻 Beginner-Friendly Example

Let’s say you want to create a virtual server (EC2 instance) on AWS.

Here’s the code

provider "aws" {
  region = "us-east-1"
}

resource "aws_instance" "example" {
  ami           = "ami-0c55b159cbfafe1f0" # Amazon Linux 2
  instance_type = "t2.micro"
}

You can run this code with:

terraform apply (if using Terraform)
tofu apply (if using OpenTofu)

💡 The exact same code works in both tools!

⚙️ Key Differences (Simple Table)

Feature	Terraform	OpenTofu
License	BSL (some restrictions)	MPL (fully open-source)
Maintained By	HashiCorp (a private company)	Linux Foundation (community-led)
Code Syntax	HCL (HashiCorp Configuration Language)	HCL
Use Case	Enterprise support, stable releases	Open, community-driven, freedom