For a team standardizing infrastructure changes, choose the control plane around its execution boundary and governance requirements before comparing price. HCP Terraform fits an established Terraform organization; Pulumi Cloud fits teams managing Pulumi programs and related automation; Spacelift merits evaluation for a shared workflow across multiple infrastructure tools; env zero offers environment- or successful-apply-based commercial choices; Scalr offers a run-based Terraform/OpenTofu model. The lowest headline price can change once policy enforcement, private execution and review traffic enter the requirement.
This is the purchase of infrastructure change management: state, plans, approvals, execution and drift handling. It differs from selecting an application host or a general CI/CD platform. Your cloud provider still bills for the deployed infrastructure, and your team still owns the desired configuration.
Official sources checked October 24, 2026. Published USD amounts below concern the platform, not cloud compute. Resource, run, environment, credit and worker allowances measure different things.
Compare the governance package and execution boundary
| Product | Useful fit | Commercial basis | Purchase boundary |
|---|---|---|---|
| HCP Terraform | Terraform-specific remote workflow | Free up to 500 managed resources; paid resource-based plans | Policy enforcement and advanced controls depend on tier |
| Pulumi Cloud | Pulumi programs and managed automation | Essentials $40/month; Pro $400/month, with credits and usage | Mandatory governance differs from advisory policy results |
| Spacelift | Shared control across infrastructure tools | Quoted packages with private worker allowances | Private workers and a self-hosted control plane differ |
| env zero | Environment lifecycle and successful applies | Paid quote per successful apply or environment | Free has separate run, environment and concurrency limits |
| Scalr | Terraform/OpenTofu run-based administration | Free up to 50 runs/month; Business $0.99/run before volume discounts | Dry plans can count; scheduled drift runs are excluded |
HCP Terraform
HashiCorp’s subscription documentation defines Free, Essentials, Standard and Premium. Free is limited to 500 managed resources; Essentials adds collaboration on resource-based pay-as-you-go billing. The detailed matrix places policy enforcement and cost estimation in Standard and Premium, while audit logging appears in Premium. It lists one remote and one agent concurrent run on Free, with higher limits on paid tiers.
This is a natural candidate if the organization already structures its change workflow around Terraform and wants its dedicated remote service. The practical question is whether the required governance fits the selected organization plan. An inexpensive resource allowance is irrelevant if an audit requirement forces a different package.
The overview’s introductory Free description mentions policy enforcement, while its detailed feature and governance tables exclude it. Treat that as an entitlement question to resolve in the offer; do not promise mandatory policy on Free. HCP Europe also has specific contract arrangements. The marketing price page was unavailable to ordinary retrieval, so no paid per-resource rate is guessed.
Pulumi Cloud
Pulumi’s current matrix lists Essentials at $40/month with 40 credits and up to 500 managed resources, Pro at $400 with 400 credits and up to 2,000 resources, and Enterprise at $2,000 with 2,000 credits and up to 4,750 resources. Those cards sit alongside resource-hour, workflow-minute, secrets/API and other usage rates. They should not be read as fixed all-inclusive infrastructure subscriptions.
The governance distinction is concrete: Essentials has advisory policy results, while Pro adds organization-managed enforcement, preventative policies, drift handling, SAML/SSO and audit logs. Enterprise makes self-hosting available and adds further compliance administration. These differences can matter more than the first resource band.
Pulumi Deployments supplies managed deployment automation around the infrastructure workflow. Prefer it when Pulumi is already the team’s intended programming model and hosted automation removes work the team would otherwise operate. An existing Terraform estate needs a migration decision as well as a price comparison; do not assume a control-plane change leaves every program, provider and policy unchanged.
Spacelift
Spacelift’s packages list support across OpenTofu, Terraform, Terragrunt, Pulumi and Kubernetes. Starter Plus includes one private worker and policy tooling; Business adds more private workers, blueprints and advanced scheduling. Higher packages add governance and support scope, with self-hosted and air-gapped options listed in Enterprise Plus. Current paid cards request a quote rather than supplying a dependable public monthly amount.
The worker-pool documentation explains public and private execution. A private worker is an execution component, not proof that the whole control plane is inside your network. State, source credentials, logs and workflow metadata deserve their own boundary review.
Shortlist Spacelift when different infrastructure frameworks need common approvals and dependencies. If you use only a few Terraform workspaces, the broader orchestration surface may be less valuable. Quote the worker count, execution topology, SSO, audit and support requirements together instead of comparing a basic package with a competitor’s fully governed configuration.
env zero
The current env zero pricing page offers Cloud Navigator and Cloud Pilot as custom-priced per successful apply or environment. It defines an active environment around running infrastructure managed through the service, and a successful deployment as a successful Terraform apply, excluding PR plans, drift detection and destroy from that paid definition. These are meaningful differences for a review-heavy team.
Free is a different meter: 250 runs/month, 30 active environments and one self-hosted runner, with the detailed matrix limiting concurrency to one and run duration to 20 minutes. The page-wide unlimited-concurrency headline should not override that Free row. Its Free run definition includes applies, destroys and drift detections. Get the actual paid counting rules and environment lifecycle treatment in the quote.
The self-hosted agent guide describes execution in customer-managed infrastructure. Prefer this path when environment ownership, lifecycle automation and execution location are central requirements. Budget the runner infrastructure and its operation separately, and confirm what data remains in the hosted control plane.
Scalr
Scalr’s pricing offers Free up to 50 runs/month and Business at $0.99/run before volume discounts. It explicitly avoids separate user, resource and self-hosted-agent charges. Its current FAQ gives new accounts five concurrent managed runs by default, with increases available on request for a valid use case. Included concurrency is not unlimited simultaneous execution without quotas.
The billing FAQ counts both apply runs and dry plans, while excluding scheduled drift-detector runs and local execution. A team with many pull-request revisions should forecast review activity, not just production changes. An apply run includes its plan stage; that is different from a separate dry run.
Scalr is worth evaluating when a Terraform/OpenTofu organization wants this run-based contract without seat or resource surcharges. Private execution still requires an operated agent. The installation guide distinguishes shared agent pods from isolated jobs and warns that an older chart runs workloads as root by default. Select the execution model deliberately; a self-hosted label alone is insufficient.
Use the approval path as the purchasing specification
Execution location and control-plane location are separate decisions. Define who may plan, approve and apply; which policy failures block a change; how credentials are obtained; what logs leave the runner; and what happens when drift is detected. A warning is not a blocking policy, and drift detection is not permission to remediate automatically.
For a stable but large resource estate, run-based pricing deserves attention. For a small estate with constant review activity, the result may reverse. Neither observation establishes the cheapest provider without an actual workload and equivalent entitlements. Obtain one configured offer for the same engines, identity controls, private network, concurrency and support response before deciding.
By Toolverly Editorial, with AI-assisted research and drafting.
Photo by Kevin Ache on Unsplash. Read about our publication or send a correction.