env zero, formerly styled env0, is a commercial platform for Terraform, OpenTofu and other IaC with environment-based billing. Pages here cover replacing it with self-hosted Terrakube or Atlantis.
env zero's environment-based platform against self-hosted Terrakube: workspaces and templates, remote runs from the CLI, self-hosted runners against Terrakube executors, OPA and Infracost extensions, identity, and the trade between custom pricing and running it yourself.
For teams whose main use of env zero is plan and apply on pull requests: Atlantis in your own infrastructure, its locking and pull request comments, what it leaves out (environment lifecycle, cost governance, state hosting) and when that gap matters.
Moving environments from env zero to Terrakube: migrating state out of the env zero remote backend, recreating workspaces, variables and VCS connections, replacing templates and approval policies, switching runners and marking env zero environments inactive without destroying resources.
Cost of ownership by component: env zero's free tier limits and custom pricing per successful apply or environment, against Terrakube's free software, hosting, database and executors, migration and operations, with the usage drivers that move each side.
The documented path out of env zero's remote backend: terraform login, an optional local backup, swapping the backend block and running init with -migrate-state, verifying a no-change plan, and marking environments inactive so resources stay in place.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.