Should You Renew Terraform Cloud? A 2026 Decision Guide

This post is part of our series on Terraform Cloud.

If you run Terraform through HashiCorp's HCP Terraform (formerly Terraform Cloud), your renewal date is the one moment each year when staying and leaving cost roughly the same effort — both require a decision. Most teams let it pass and click renew, because switching feels like the riskier move. This guide lays out the four paths open to you in 2026, what each costs, and how to tell which one fits, so the renewal becomes a choice you make rather than a default you accept.

What changes at a Terraform Cloud renewal in 2026?

A few things are different this year. HCP Terraform is now part of IBM, which completed its acquisition of HashiCorp in February 2025; the pricing pages are branded "IBM HCP Terraform." Billing is per managed resource — the resources-under-management (RUM) model — at Essentials $0.10, Standard $0.47, and Premium $0.99 per resource per month as of June 2026. The legacy self-serve free plan reached end of life on March 31, 2026, and remaining organizations moved to an enhanced free tier (up to 500 managed resources, one concurrent run, SSO, Sentinel and OPA, and cloud agents).

The practical effect at renewal: your quote tracks your resource count. If your infrastructure grew over the past year, the renewal figure grew with it, even if your team's deploy cadence stayed flat. For the full tier-by-tier breakdown, see our Terraform Cloud pricing review.

Why are teams rethinking Terraform Cloud in 2026?

Three reasons come up repeatedly in practitioner discussion. They do not apply to everyone, so read them against your own setup:

1. RUM bills scale with infrastructure, not usage. A workspace that runs twice a month costs the same as one that runs fifty times, because you pay for the resources it manages. Teams whose resource counts have grown see the renewal quote climb without any change in how they work.
2. Concurrency caps create queues. The free tier allows one concurrent run, and lower paid tiers raise the limit only modestly. For a team pushing changes across many workspaces, runs stack up behind the cap, and that bites hardest during incidents.
3. License and ownership changes. HashiCorp's 2023 switch to the Business Source License, followed by the IBM acquisition, moved some teams toward OpenTofu, the Linux Foundation fork, for long-term independence.

When does renewing Terraform Cloud still make sense?

Renewing is a legitimate outcome, and for some teams it is the right one. Stay if:

• You are deep in the HashiCorp ecosystem — Vault, Consul, and a Sentinel policy library you would rather not rewrite.
• Your resource count sits under the 500-resource free tier, so your real cost is already zero.
• Your team has no appetite for any platform change this cycle and the current bill is acceptable.

The goal is to choose renewal on the numbers, not to back into it because the alternatives went unexamined.

What are your four options at renewal?

Option	What it is	Best when	Main cost or risk
Renew as-is	Keep HCP Terraform on your current or a higher tier	You fit the HashiCorp ecosystem or sit under the free tier	RUM bill keeps growing with your resource count
Renegotiate	Use the renewal plus a costed alternative as negotiating room	You have meaningful spend and are willing to push	Time; the vendor may not move far
Migrate to a managed alternative	Move to Scalr, Spacelift, or env0	RUM cost or concurrency caps are hurting and you want a managed service	A one-time migration effort
Move to open source	OpenTofu with Atlantis or self-managed pipelines	You have the engineering capacity and want no platform fee	You own the operational burden

Options 3 and 4 are covered step by step in our platform engineer's guide to replacing Terraform Cloud and the migration guide.

How much does each path cost in 2026?

The pricing models differ enough that the cheapest path depends entirely on your shape — resource count, run frequency, and concurrency needs. As of June 2026:

• HCP Terraform: per managed resource — Essentials $0.10, Standard $0.47, Premium $0.99 per resource/month.
• Scalr: per run — free up to 50 runs/month, then $0.99/run with volume discounts. Cost tracks deployments, not resource count. See the Scalr vs Terraform Cloud pricing comparison.
• Spacelift: per worker (concurrency) — free tier of 2 users and 1 worker, entry paid tier Starter+ at $20,000/year.
• env0: per apply or environment — no free tier (trial only), entry Cloud Compass tier at $1,500/month.
• OpenTofu + Atlantis: no platform fee; you pay in engineering time to run and maintain it.

Because the models measure different things, the only reliable comparison uses your own numbers. Pull your run history from Terraform Cloud and put it through the Scalr pricing calculator to see how a per-run bill compares against your renewal quote.

Isn't migrating off Terraform Cloud risky?

This is the reason most teams renew by default, so it deserves a direct answer. The risk is real but smaller than it feels, and it varies by destination.

Scalr is the lowest-friction case because both Scalr and Terraform Cloud are remote operations backends — your terraform plan and terraform apply workflow stays the same, and state moves across rather than being re-architected. An automated migration tool maps organizations to environments and moves workspaces, variables, and state. A typical migration moves about 100 workspaces in roughly 20 minutes, and it reverses with standard terraform state pull and terraform state push if you decide to go back. Free migration periods avoid paying both platforms at once.

Moving to open source carries more weight, because you take on state storage, locking, policy enforcement, and concurrency yourself. That is a fair trade for teams with the engineering capacity, and a poor one for teams without it.

How do you decide before your renewal date?

A short timeline keeps the decision off the critical path:

1. About 8 weeks out: pull your Terraform Cloud run history and resource count, and get your renewal quote in writing.
2. About 6 weeks out: estimate each path's annual cost. Use your run history in the Scalr pricing calculator and compare against the RUM quote.
3. About 4 weeks out: if a migration looks worthwhile, run a proof of concept on a few non-critical workspaces.
4. About 2 weeks out: decide. If you stay, bring the estimate into the renewal conversation; a credible alternative gives you room to negotiate.

For the wider set of options and a feature-by-feature comparison, start from our pillar guide on selecting a Terraform Cloud alternative.