Environments on env0 are defined by Infrastructure-as-Code templates. env0 has native support for Terraform and Terragrunt as an IaC framework, so this means that each environment is equivalent to one Terraform workspace.
An "active environment" is any environment that is managed through env0 that is currently running. Environments that have been destroyed or been manually marked as “Inactive” don't count towards your active environments.
A deployment is counted whenever a Terraform Apply or Destroy occurs.
env0 is not a cloud provider. Deployed environments will run on your own cloud account that you specify via the Terraform code, and whatever credentials you supply during deployment. env0 simply manages the lifecycle of the underlying resources.
Yes, env0 can be used to manage production environments. We recommend that you use env0 to manage both your development environments AND your production environments, keeping your deployment process as identical as possible. env0 provides advanced RBAC and configuration management capabilities, allowing you to use a single IaC codebase, to deploy to both development and production - just like you do with your application code.
No. env0’s custom flows let you run anything you can script, at any point in the process. This includes when you are creating, updating, and destroying your environments. You can run Ansible, kubectl, the AWS CLI, or even your own application code. The extensibility possibilities are almost endless.
No, env0 is not limited to AWS, GCP, and Azure. Because env0 relies on Terraform to provision infrastructure, you can use any provider supported by Terraform, as well as 3rd party providers. These include other cloud providers such as IBM Cloud, VMWare, Oracle, and even specific managed solutions such as Auth0, Github and Netlify.
Before deploying your environment, env0 will inject custom tags into your Terraform code using Terratag. After the environment has been deployed, env0 queries the cloud provider’s API, using those custom tags, to get the actual costs of your running environments. This is not an estimation.
Yes. You can use OPA in your custom flow (env0.yml) file. Here is an example of validating the Terraform plan using Open Policy Agent. Native OPA support will be added soon!
The best practice is to save your state files on your own infrastructure - we fully support any Terraform backend. This way you keep your sensitive information (which is stored in your state files) in your cloud account. But if you prefer, env0 also supports its own mechanism in which state files are stored separately per environment, in an encrypted S3 bucket. Each organization’s files are encrypted using a dedicated key.
Yes! Our most recent SOC 2 Type II report was completed in October 2020 and a copy is available upon request from your account manager.
env0 can be delivered in 2 ways - Full SaaS offering and a Hybrid SaaS + Self-Hosted Agent offering. Self-Hosted Agent is supported on our Business and Enterprise tiers.
