Skip to content
Calcrivo

Terraform Cloud Cost Calculator

Estimate monthly Terraform Cloud/Enterprise cost from run volume, per-run pricing, state storage and team seats.

Inputs

runs

Total plan/apply runs executed per month.

$

Price per run under your plan (varies by tier/provider).

$/mo

Flat or usage-based monthly cost for state storage.

seats

Number of licensed users.

$/mo

Monthly price per team seat.

Estimated Monthly Cost

$395.00

Estimated Annual Cost

$4,740.00

Runs Cost

$150.00

Team Seats Cost

$240.00

Runs Share of Cost

38.0%

Seats Share of Cost

60.8%

Step by step

  1. Runs cost

    300 × $0.5

    = $150.00

  2. Seats cost

    12 × $20

    = $240.00

  3. Monthly total: runs + storage + seats

    $150.00 + $5 + $240.00

    = $395.00

How it works

Formula: monthly_cost = runs × cost_per_run + state_storage_cost + team_seats × cost_per_seat. This models the common structure of managed Terraform platforms, which typically combine usage-based run pricing with flat state storage and per-seat licensing. Actual pricing tiers, free-run allowances, and volume discounts vary by provider — check current published pricing tools for exact figures.

Formula

monthly_cost = runs_per_month × cost_per_run + state_storage_cost + team_seats × cost_per_seat

runs_per_month
Plan/apply runs executed per month
cost_per_run
Price per run ($)
state_storage_cost
Monthly state storage cost ($)
team_seats
Licensed user count
cost_per_seat
Monthly price per seat ($)

Frequently Asked Questions

Does this reflect actual Terraform Cloud pricing tiers?

This models the general cost structure (runs + storage + seats), but exact rates, free tiers and volume discounts change over time — check the current provider pricing page for precise figures before budgeting.

How can I reduce run-based costs?

Batch related changes into fewer, larger PRs to reduce plan/apply run frequency, use speculative plans sparingly for exploratory work, and avoid triggering runs on documentation-only or non-infrastructure changes.

Are team seats billed per active user or per license?

This varies by vendor and plan — some bill per active/logged-in user in a period, others per provisioned license regardless of activity. Check your specific plan's seat definition.

Is self-hosted Terraform (open source CLI + your own backend) always cheaper?

It avoids per-run and per-seat licensing but shifts cost to your own CI/CD compute, backend storage, and the engineering time to build equivalent policy enforcement, run history and collaboration features.

You might also need