What Is an OpenTofu Management Platform?

An OpenTofu management platform runs your plans and applies as a service and adds what the CLI leaves to you: shared state with locking, RBAC, policy checks, drift detection, and an audit log. HCP Terraform isn't one; as of July 2026 it only runs the Terraform binary. The platforms that do run OpenTofu are Scalr, Spacelift, and env0 as SaaS, and Terrakube and Atlantis if you'd rather host it yourself. The real difference between them is how they bill, so that's where this post spends most of its time.

What is an OpenTofu management platform?

The distinction matters because the CLI is single-player by design. It assumes one operator, one working directory, and a backend you configured yourself. The moment a second engineer needs to run a plan against the same state, you need locking. The moment an auditor asks who changed the database tier, you need a log. That's what the platform does, and it's the same job whether the engine is Terraform or OpenTofu.

Does HCP Terraform support OpenTofu?

No. As of July 2026, HCP Terraform's managed runs execute the Terraform binary only, and there is no setting to run OpenTofu instead. OpenTofu can use HCP Terraform's remote backend purely for state storage, but the managed run engine, Sentinel policies, and no-code modules are all Terraform-only.

So a team that has committed to OpenTofu can keep HCP Terraform as a state store, but not as the thing that runs their plans and applies. For most people that defeats the point of a managed platform. Many teams moved to OpenTofu after HashiCorp changed Terraform's license in August 2023 and were reconsidering where their runs execute at the same time, and this is the wall they hit: the most obvious managed option doesn't run the engine they're standardizing on.

Which platforms run OpenTofu?

Five come up most often. Three are SaaS control planes, and two are open-source tools you host yourself.

Scalr is a founding member of the OpenTofu project, which is why OpenTofu is a first-class engine there rather than a setting.

For the self-hosted comparison specifically, the OpenTofu plus Atlantis versus a managed platform breakdown walks through where running your own stack costs less and where it costs more.

How much does an OpenTofu management platform cost?

The headline numbers matter less than the counting model, because that's what decides whether the bill tracks your team or fights it. Scalr counts runs (free to 50 a month, no per-user or per-resource charges, same price for either engine; current tiers on the pricing page). Spacelift counts concurrent private workers. env0 counts active environments by tier. Terrakube and Atlantis have no license fee, and the cost is the engineering time to run the server, wire up state and locking, handle secrets, and keep it patched.

Check each vendor's pricing page before you commit; worker counts, environment caps, and tier lines move. What doesn't move is the counting model. A team that runs 400 plans on a Tuesday and nothing on Friday wants per-run. A team that keeps 30 applies going all day wants per-worker. Figure out which one you are first. We argue per-run wins for most teams in how to evaluate IaC platform pricing models.

How do I choose an OpenTofu management platform?

Start with three questions. First, is running OpenTofu a hard requirement or a nice-to-have? If it's hard, HCP Terraform is out and you're choosing among the platforms above. Second, do you want to operate the control plane yourself? If yes, Terrakube or Atlantis; if no, a SaaS platform. Third, which pricing model fits your run pattern? Count your runs, concurrency, and environments for a month, then price that month on each model. One of them will usually be clearly cheaper.

If you're weighing this as part of a broader move off Terraform Cloud, the guide to selecting a Terraform Cloud alternative covers the migration side, and OpenTofu versus Terraform covers the engine decision itself.

Scalr runs OpenTofu natively on usage-based pricing that's free up to 50 runs a month, with state, locking, RBAC, policy, and drift detection included. If you want to keep OpenTofu without running the backend and workers yourself, it's a straightforward place to start.