TechWhoKnows
Log inSign up
Latest
AI
Startups
Venture
Tech
Security
Hardware
Biotech & Climate
Markets & Policy
Companies
TopicsNewsletterAbout
TechWhoKnows

Independent tech news from Singapore, with the sources linked.

Sections

  • AI
  • Startups
  • Venture
  • Tech
  • Security
  • Hardware
  • Biotech & Climate
  • Markets & Policy

TechWhoKnows

  • Companies
  • About
  • Newsletter
  • All topics
  • Search
  • Account

© 2026 TechWhoKnows. All rights reserved.

  • Privacy
  • Terms
Home/Tech/Enterprise & Cloud

Terraform vs OpenTofu vs Pulumi in 2026: Licensing, State, and Multi-Cloud Costs

Compare Terraform, OpenTofu, and Pulumi in 2026 across BSL vs MPL-2.0 licensing, state encryption, programming languages, and team pricing.

Terraform vs OpenTofu vs Pulumi in 2026: Licensing, State, and Multi-Cloud Costs

By Aarav Mehta, Cloud & Enterprise Tech

16 Nov 20269 min read

Choosing an infrastructure-as-code tool in 2026

Infrastructure teams provisioning AWS, Google Cloud, Azure, and Kubernetes clusters in 2026 face a three-way split between HashiCorp Terraform, the Linux Foundation's OpenTofu fork, and Pulumi. While all three manage cloud resources through declarative state graphs and provider plugins, their licensing terms, state security models, and authoring languages create distinct operational and financial trade-offs.

Picking the wrong tool locks platform teams into awkward CI/CD wrappers or unexpected commercial licensing bills once managed resource counts pass a few thousand.

Feature and licensing comparison

| Dimension | Terraform | OpenTofu | Pulumi | |---|---|---|---| | Licence | BSL 1.1 (source-available) | MPL-2.0 (OSI open source) | Apache 2.0 (core CLI/SDK) | | Authoring language | HCL (declarative) | HCL (declarative) | TypeScript, Python, Go, C#, YAML | | Client-side state encryption | No (backend-level only) | Yes (native AES-GCM / KMS) | Yes (per-stack secrets provider) | | Provider ecosystem | Terraform Registry | OpenTofu Registry | Native + bridged Terraform providers | | Managed SaaS model | HCP Terraform (per-resource) | Third-party TACOs (Spacelift, Env0, Scalr) | Pulumi Cloud (credits / seats) |

Licensing and vendor lock-in: BSL vs MPL-2.0

The split between Terraform and OpenTofu began when HashiCorp moved Terraform to the Business Source Licence (BSL 1.1), restricting commercial products that compete with HashiCorp offerings. For internal enterprise platform teams building standard infrastructure pipelines, the BSL rarely blocks normal usage, though legal teams at SaaS vendors and managed service providers often forbid BSL dependencies inside customer-facing control planes.

OpenTofu operates under the Mozilla Public Licence 2.0 (MPL-2.0) within the Linux Foundation and Cloud Native Computing Foundation ecosystem. Companies building internal developer platforms, multi-tenant SaaS provisioning engines, or commercial infrastructure tooling can embed OpenTofu without BSL commercial restrictions. Pulumi's core engine and language SDKs use the permissive Apache 2.0 licence.

State management and client-side encryption

Every declarative infrastructure tool relies on a state file that frequently holds sensitive outputs such as database passwords, API tokens, and private keys. Both Terraform and OpenTofu store state as JSON, typically in Amazon S3, Google Cloud Storage, or a managed backend.

OpenTofu holds a clear security advantage for self-hosted teams: it supports native client-side state and plan encryption using PBKDF2 passphrases, AWS KMS, GCP KMS, or OpenBao before the state file ever leaves the runner. Terraform relies on server-side encryption at rest (such as S3 SSE-KMS) or HashiCorp's managed HCP Terraform platform, meaning any administrator with read access to the raw bucket object can inspect plaintext secrets inside terraform.tfstate.

Pulumi encrypts individual secret values inside its state JSON automatically using either Pulumi Cloud, a cloud KMS key, or a local passphrase, avoiding plaintext secret storage in state snapshots by default.

HCL vs general-purpose languages

Terraform and OpenTofu share HashiCorp Configuration Language (HCL). HCL's narrow syntax keeps pull requests readable across operations and security teams because engineers cannot bury arbitrary HTTP calls, file-system mutations, or complex runtime loops inside a module. The drawback surfaces when platform teams need dynamic loops, conditional nested objects, or unit testing across dozens of microservices, where HCL's for_each and dynamic blocks become verbose.

Pulumi replaces HCL with TypeScript, Python, Go, C#, and Java, alongside a YAML option for simple stacks. Application engineers can share type definitions directly between application code and cloud infrastructure, run standard unit tests using Jest or pytest, and package reusable patterns as npm or PyPI libraries. That flexibility requires discipline: without strict code review, engineers can write imperative logic inside infrastructure definitions that breaks repeatability.

Pricing and CI/CD runner costs

Running the open-source OpenTofu CLI or Terraform CLI inside GitHub Actions or GitLab CI costs nothing in tool licences. Costs appear when teams adopt managed orchestration:

  • HCP Terraform prices by managed resources per month beyond a small free tier, which can escalate rapidly for teams managing fine-grained DNS records, IAM policies, or Kubernetes objects.

  • OpenTofu has no single commercial SaaS from the project itself, letting teams pair it with GitHub Actions, Atlantis, or competing orchestration platforms (TACOs) such as Spacelift, Env0, or Scalr.

  • Pulumi Cloud charges based on resource-hours or seats depending on the tier, though teams can also self-host state in S3 or GCS using the open-source CLI to avoid SaaS fees.

Which tool should your team choose?

Choose OpenTofu if your team already knows HCL, wants a drop-in open-source replacement for Terraform with native client-side state encryption, or builds commercial products subject to BSL restrictions. Choose Terraform if your organisation already standardises on HCP Terraform Enterprise and HashiCorp Sentinel policies with an active support contract. Choose Pulumi if your infrastructure is authored primarily by software engineers who want type-safe TypeScript or Python modules, real unit testing, and tight integration with application repositories.

Frequently Asked Questions

Is OpenTofu a drop-in replacement for Terraform in 2026?

For most HCL codebases using Terraform 1.5 and earlier state formats, OpenTofu serves as a direct replacement with identical CLI workflows. Teams migrating from newer Terraform 1.9+ features should verify syntax and state-version compatibility before switching.

Does OpenTofu support Terraform providers?

Yes. OpenTofu uses its own public registry mirroring major cloud providers such as AWS, Google Cloud, Azure, and Kubernetes, and remains compatible with the Terraform provider protocol.

Can Pulumi import existing Terraform state?

Yes. Pulumi provides built-in conversion tools (pulumi convert) to translate HCL to TypeScript, Python, or Go, and can reference or import resources managed by existing Terraform state files.

Which IaC tool is cheapest for a 50-engineer team?

Self-hosting OpenTofu or Pulumi CLI with S3 state locking inside existing CI/CD runners incurs zero per-seat or per-resource software fees, making both far cheaper than commercial SaaS tiers.

More on

  • Guide
  • Comparison
  • Terraform
  • Opentofu
  • Pulumi
  • Enterprise-cloud
  • Devops

Further reading

Enterprise & Cloud

Zero-Trust Secrets Management in Multi-Cloud Environments: HashiCorp Vault vs Infisical vs AWS Secrets Manager (2026 Production Benchmark)

14 Nov 2026

Enterprise & Cloud

Self-Hosted AI Agents Comparison 2026: OpenClaw vs Goose vs Agent Zero Architecture and Security

15 Nov 2026

Enterprise & Cloud

Data-Eng-Bench Establishes Open-Source DBA and Data Engineering Evaluation Standard for AI Agents

14 Nov 2026

Enterprise & Cloud

Microsoft 365 21-Hour Outage Exposes Single-Provider Enterprise Risk

16 Nov 2026

Follow TechWhoKnows for real-time coverage

Stay updated with the latest developments in technology.

XBlueskyThreadsInstagramLinkedInTikTokYouTube

The TWK Newsletter

Pick your topics and we'll email you our stories on them, with links to the sources.

In this story

Related stories

Zero-Trust Secrets Management in Multi-Cloud Environments: HashiCorp Vault vs Infisical vs AWS Secrets Manager (2026 Production Benchmark)

14 Nov 2026

Self-Hosted AI Agents Comparison 2026: OpenClaw vs Goose vs Agent Zero Architecture and Security

15 Nov 2026

Data-Eng-Bench Establishes Open-Source DBA and Data Engineering Evaluation Standard for AI Agents

14 Nov 2026