Operations | Monitoring | ITSM | DevOps | Cloud

How env zero turns Infrastructure as Code into true self-service—developers deploy pre-approved infrastructure in a few clicks, and multi-step workflows handle the complex stuff automatically. This walkthrough shows what happens once discovery, codification, and governance are in place: developers pull from a catalog of approved resources without filing tickets or writing Terraform, and platform teams keep their guardrails intact. We also cover workflows, which chain multiple deployments into a single run.

How env zero keeps Infrastructure as Code under control at scale — custom roles and permissions, Policy as Code guardrails, and automated drift detection with remediation. This walkthrough covers env zero's governance features: building granular custom roles for your teams, enforcing policy guardrails that stop bad configurations before they deploy, and catching infrastructure drift the moment someone changes something outside the platform.

Turn manually-created cloud resources into Infrastructure as Code, then package that code into reusable templates your whole team can deploy. This walkthrough covers two env zero capabilities that work well together: using Cloud Compass to codify click ops resources into Terraform or OpenTofu, and building reusable templates so other users can deploy proven infrastructure without writing code or configuring integrations themselves.

See how env zero discovers and manages every cloud resource across AWS, Azure, and GCP—including resources deployed outside of Infrastructure as Code. In this overview, we walk through env zero's cloud resource discovery and environment migration capabilities. You'll see how the Cloud Compass dashboard maps your entire resource estate, how to tell whether a resource was created by IaC, click ops, or an API call, and how to bring existing Terraform workspaces and VCS repositories into env0 in bulk.

"Show me all EC2 instances that are public." One question. About 10 minutes. Manually, the same answer is a 10-day job. In this clip, the CloudQuery AI assistant works it out live: it finds the EC2 instances table, reads the schema, identifies public_ip_address as the field that signals public exposure, and queries for every instance that has one. It comes back with 2 running public EC2 instances — instance type, public IP and DNS, private IP, VPC, subnet and tags for each — and flags that both are reachable from the internet, subject to security group rules.

How many resources do you actually have across every cloud provider? Manually, that's a ~2 hour job. With CloudQuery, it's one question. In this clip we ask the CloudQuery AI assistant a single question —"Show count of all resources across all cloud providers" — and get a full multi-cloud asset inventory back in about a minute: Wiz 9,225 · GCP 6,485 · AWS 2,297 · Azure 1,153 · Entra ID 1,109 · Kubernetes 1,066 · Backstage 75 → 21,410 total resources.