Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.envzero.com/llms.txt

Use this file to discover all available pages before exploring further.

env zero is a cloud infrastructure governance platform. It gives platform teams a control plane to define how infrastructure should be delivered and ensures those standards are applied consistently across every team, tool, and cloud. env zero platform overview showing three pillars: Speed (to market, of innovation, of collaboration), Scale (millions of resources across every cloud, team, and tool), and Standards (security, cost, compliance). Integrations shown include Helm, GitHub, GitLab, Kubernetes, Terraform, and AWS.

​
What env zero does

​
Templates

Reusable IaC configurations that teams deploy from without writing infrastructure code directly. Templates support Terraform, OpenTofu, Terragrunt, Pulumi, Helm, CloudFormation, and Kubernetes. Learn more

​
Environments

Each deployment of a template is an environment. env zero manages the full lifecycle: plan, apply, destroy, scheduling, and drift detection. Learn more

​
Approval policies

OPA-based policies that run after the plan step. Deployments pause for human review or are denied automatically based on cost, resource type, or other criteria. Learn more

​
Drift detection

Alerts when live infrastructure diverges from the code that describes it. Remediation can be triggered directly from the drift notification. Learn more

​
Cost estimation

Projected costs appear in every plan output before anything deploys, so teams see the financial impact of a change before approving it. Learn more

​
Access control

Permissions scoped by organization, project, or environment using role-based access control and credential isolation. Teams access only what they need. Learn more

​
Automation

Deploy on git push, schedule environments to spin up and down on a cadence, run custom pre- and post-deploy scripts with Custom Flows, and trigger deployments from the API.

​
How env zero fits into your workflow

env zero connects to your VCS, cloud credentials, and IaC code. It sits between your code and your cloud, running plans, enforcing policies, managing state, and recording every change. Teams keep their existing tools and workflows; env zero adds the governance layer on top.

​
Next steps