Guide

Terraform vs Pulumi 2026: HCP Terraform vs Pulumi Cloud Cost

Terraform vs Pulumi in 2026: HCP Terraform per-resource rates against Pulumi Cloud edition fees, free tiers compared, and costs at 300 to 4,750 resources.

Terraform vs Pulumi 2026: HCP Terraform vs Pulumi Cloud Cost

Choose Terraform if your team writes HCL and runs under 500 resources, because HCP Terraform's Free plan covers that with unlimited team members and SAML SSO. Choose Pulumi if your engineers want TypeScript, Python, Go, .NET or Java, or if you need enforced policies at around 2,000 resources: Pulumi Pro costs $400 a month there, against $940 on HCP Terraform Standard at its starting rate.

Both command-line tools are free to run with your own state backend, so the bill only starts when you buy the managed service. HCP Terraform charges per managed resource, from $0.10 a month on Essentials to $0.99 on Premium, on HashiCorp's pricing page. Pulumi Cloud charges a monthly fee per edition that buys credits, from $40 on Essentials to $2,000 on Enterprise, on Pulumi's pricing page. Both pages were read on 19 October 2026.

Toolradar data: Terraform is listed as an alternative to 36 other tools and Pulumi to 31, the top two among the 55 infrastructure-as-code tools on Toolradar, as of October 2026, per the Terraform and Pulumi profiles. Toolradar is the software directory we run. No other IaC tool is cross-shopped as often, which is why this pair decides so many platform budgets.

Terraform vs Pulumi at a glance

HCP Terraform Pulumi Cloud
Language HCL TypeScript and JavaScript, Python, Go, .NET, Java, YAML
CLI license Business Source License 1.1 Apache 2.0
Free plan Up to 500 managed resources, unlimited members 1 user, no managed-resource limit
Entry paid plan Essentials, $0.10 per resource a month Essentials, $40 a month for up to 500 resources
Governance plan Standard, from $0.47 per resource a month Pro, $400 a month for up to 2,000 resources
Top self-serve plan Premium, from $0.99 per resource a month Enterprise, $2,000 a month for up to 4,750 resources
Enforced policy as code Standard and Premium Pro and Enterprise (Essentials is advisory only)
SAML SSO Every plan, Free included Pro and Enterprise
New-customer credit $500 HCP trial credit Startups can apply for $10,000 in credits

The license line matters more than it looks. Terraform 1.6.0 and later ship under the Business Source License, which allows production use except offering Terraform to third parties as a competing hosted product, per the license file. Pulumi's engine is Apache 2.0. For most companies neither restriction bites, but a platform vendor building a hosted IaC product should read both.

How each service bills

HCP Terraform bills managed resources by the hour. A managed resource is any resource in state with mode = "managed", counted from its first plan or apply. Data sources, null_resource, terraform_data, locals and variables are free, per HashiCorp's plans documentation. Partial hours bill as full hours, and the peak count in each hour sets that hour's charge.

The rates on the pricing page are Essentials at $0.10 per resource a month ($0.00013 an hour), Standard starting at $0.47 and Premium starting at $0.99. The word "starting" matters: HashiCorp's docs send Standard and Premium buyers to sales, and Flex contracts give larger discounts at scale. Use the list rates as a ceiling.

Pulumi Cloud bills credits. One Pulumi Credit costs $1, and each paid edition's monthly fee buys a pool of credits that expires at the end of the month. Usage beyond the pool is billed in arrears. On Essentials, IaC resources cost $0.1825 a month each; on Pro the rate starts at $0.365 and falls with volume; on Enterprise it starts at $0.5475.

Ask Pulumi one question before you budget above the included count. Essentials includes 40 credits and "up to 500 managed resources", yet 40 credits at the Essentials resource rate would cover about 219 resource-months, by our arithmetic. Pulumi prints no worked Essentials bill above 500 resources, so confirm how the included 500 is counted if you expect to pass it.

Annual commitments are available only on Pulumi Pro and Enterprise. Every Pulumi paid edition is also available month to month on a card.

What each costs at the same resource count

These scenarios use list prices only. HCP Terraform figures are per-resource rates times the resource count, by our arithmetic; Pulumi figures are the edition fees with the resource coverage Pulumi prints.

Scenario HCP Terraform Pulumi Cloud Cheaper
1 engineer, 300 resources $0 on Free $0 on Free Tie
5 engineers, 300 resources $0 on Free (1 concurrent run, no teams) $40 on Essentials Terraform
Team with RBAC, 400 resources $40 on Essentials $40 on Essentials Tie
Enforced policies, 2,000 resources $940 on Standard $400 on Pro Pulumi, by $540
Audit logs and top tier, 4,750 resources $4,702.50 on Premium $2,000 on Enterprise Pulumi, by $2,702.50

The pattern is clear. Terraform is cheaper when you need little governance: its Free plan carries any number of members, and HCP Terraform Essentials has the lowest per-resource rate on either page. A team managing 2,000 resources without policy enforcement would pay $200 a month on HCP Terraform Essentials.

Pulumi is cheaper once governance is the requirement. HCP Terraform keeps policy enforcement and cost estimation for Standard and up, and audit logging for Premium, and its per-resource rates on those plans are steep. Pulumi bundles enforced policies, audit logs, drift detection and SAML SSO into Pro's flat fee for up to 2,000 resources.

Two caveats keep the comparison honest. HashiCorp's Standard and Premium rates are starting prices that sales can lower, and Pulumi adds separate meters for secrets ($0.50 a secret a month on Essentials), workflow minutes ($0.01 a minute) and Neo AI tokens ($3 per million).

Free plans: who each one suits

HCP Terraform Free suits a small team. It allows up to 500 managed resources, unlimited workspaces and projects, unlimited members, remote runs, VCS integration, the private module registry, run tasks and SAML SSO. The limits are one concurrent remote run and one agent run, no teams, no custom roles and no policy enforcement.

Pulumi Free suits one engineer. It allows a single user, with no limit on managed resources, unlimited projects and stacks, Pulumi Deployments, basic Pulumi ESC and 500 workflow minutes. The second teammate is what moves a Pulumi user to Essentials.

The practical split: a startup with three engineers and a few hundred resources can stay on HCP Terraform Free, while a solo developer with a large personal fleet fits Pulumi Free better. Both projects also run without any hosted service at all. Pulumi's FAQ notes you can manage state yourself offline, and Terraform runs against any supported backend.

If you track infrastructure tooling, Devshot covers price changes like these as they ship. Subscribe at devshot.co.

Language and team fit

The language choice usually decides this before the price does. HCL is declarative and narrow by design, which keeps modules readable for operators who are not full-time developers. Pulumi lets a team write infrastructure in the language its services already use, with loops, functions, tests and package managers from that ecosystem.

That flexibility cuts both ways. A Pulumi program can hide complex logic that a reviewer has to run in their head, where an HCL plan is easier to scan. Teams with a platform group writing modules for many app teams often prefer HCL; teams where application engineers own their own infrastructure often prefer Pulumi.

Concurrency is the other operational difference. HCP Terraform allows 3 concurrent remote runs on Essentials and 10 on Standard, with extra concurrency for purchase only from Standard. Pulumi allows 5 concurrent stack updates on Essentials and unlimited on Pro. A monorepo with many stacks updating at once will feel the HCP Terraform Essentials cap first.

What about OpenTofu?

OpenTofu is the open-source fork of Terraform, licensed MPL 2.0 on its GitHub repository. It reads HCL and most Terraform modules, so a team that wants Terraform's language without the Business Source License can switch the CLI and keep its code. It has no first-party hosted plan to compare here, so the cost becomes whatever you pay for state storage and a CI runner. Our best Terraform and IaC tools guide ranks OpenTofu, Spacelift, Terragrunt and AWS CDK alongside this pair.

Which should you choose?

Pick HCP Terraform if your team already writes HCL, stays under 500 resources, or needs SSO without paying for it. Its Essentials rate is also the cheapest way to add teams and RBAC at a few thousand resources when policy enforcement is not required.

Pick Pulumi if your engineers want general-purpose languages, if one person runs the infrastructure on the free tier, or if you need mandatory policies and audit logs at 2,000 to 4,750 resources, where Pulumi's flat fees undercut HCP Terraform's per-resource governance plans.

For related tooling, see our best AI tools for DevOps, the GitHub vs GitLab comparison for the repo that triggers your runs, our best internal developer portals list, the best Kubernetes tools guide, the best CI/CD tools ranking and our CI/CD pricing compared page. For hosting the infrastructure itself, read DigitalOcean vs Hetzner or AWS Lambda pricing. Toolradar also has a side-by-side Terraform vs Pulumi comparison.

How we compared

Louis Corneloup, founder of Dupple and Toolradar, prepared this comparison for engineering teams choosing an IaC platform. We read HCP Terraform's plan rates on HashiCorp's pricing page, plan limits and resource counting rules in HashiCorp's plan documentation, Pulumi Cloud's editions, meters and FAQ on its pricing page, and the license files on GitHub, all on 19 October 2026. Scenario totals are our arithmetic from list prices, before taxes, support plans and negotiated discounts.

FAQ

Terraform vs Pulumi: which should I choose in 2026?

Choose Terraform if your team writes HCL, needs SSO on a free plan, or runs under 500 resources. Choose Pulumi if your engineers prefer TypeScript, Python, Go, .NET or Java, or if you need enforced policies at around 2,000 resources, where Pulumi Pro's flat fee costs less than HCP Terraform Standard.

Is Pulumi cheaper than Terraform?

It depends on the plan you need. Without governance, HCP Terraform is cheaper: its Free plan covers 500 resources for any number of users and Essentials is $0.10 per resource a month. With enforced policies and audit logs, Pulumi's Pro and Enterprise fees cost less than HCP Terraform's Standard and Premium at the same resource counts, by our arithmetic from list prices in October 2026.

Is HCP Terraform free?

Yes, up to 500 managed resources. The Free plan includes unlimited members, remote runs, VCS integration, the private registry and SAML SSO, with one concurrent run and no policy enforcement. New customers also get a $500 HCP trial credit.

How does HCP Terraform count resources?

It bills each resource in state with mode "managed", by the hour, from its first plan or apply until it is destroyed. Data sources, null_resource, terraform_data, locals and variables are not counted. Partial hours count as full hours.

Is Terraform still open source?

Terraform 1.6.0 and later use the Business Source License 1.1, which permits production use except offering it as a competing hosted product. OpenTofu, the community fork, is MPL 2.0, and Pulumi's engine is Apache 2.0.

What does Pulumi Essentials include?

Pulumi Essentials is the entry paid edition, billed monthly; its fee buys 40 credits, and it includes up to 500 managed resources, unlimited users, CI/CD integration, resource search, webhooks and advisory-only policies. Enforced policies, SAML SSO and audit logs need Pro at $400 a month.

Cite this: Devshot, "Terraform vs Pulumi 2026: HCP Terraform vs Pulumi Cloud Cost", November 2026.

Some offers on this page may be paid placements or contain affiliate links.

Devshot: the daily dev & AI brief

Free daily newsletter, read in 5 minutes.

Subscribe free