env0 is a commercial SaaS (with a self-hosted option) for running Infrastructure-as-Code pipelines — Terraform, OpenTofu, Terragrunt, Pulumi, CloudFormation, and Ansible — against cloud accounts, with policy, cost, and RBAC wrapped around them. It sits in roughly the same slot as Terraform Cloud/HCP Terraform, Spacelift, and Scalr.
The core primitive is an “environment”: a Git-backed IaC workspace tied to a deployment target, a set of variables, and a run history. env0 clones the repo, runs terraform plan/apply (or the equivalent for other tools) inside an ephemeral agent, captures state and plan output, and gates applies behind approvals, OPA policies, drift detection, and cost estimates from Infracost. Self-hosted agents let the actual IaC runs happen inside a customer VPC so cloud credentials never leave the network.
Distinguishing features versus Terraform Cloud include first-class OpenTofu support, multi-IaC-tool support in one product, PR-based ephemeral environments with automatic TTL destruction, and native Kubernetes manifest/Helm/Argo workflows in addition to Terraform. For teams doing platform engineering, the “self-service environment” model — developers hit a form, env0 spins up a full stack from a template — is the part people actually buy it for.