env0.com is a platform for managing cloud environments. It is meant to abstract away the resources (servers, databases, etc.) that constitute an environment, and allow you to manage environments the way they are used in your organization - by people, teams, and projects.
Nope!
An "active environment" is any environment managed through env0 that is currently running. Environments that have expired or been manually disabled don't count towards your active environments.
Environments on env0 are defined by Infrastructure-As-Code templates. env0 has first class support for Terraform as an IaC framework.
Environments will run on your own cloud account. env0 just handles the management 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 pipelines 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 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. env0 also supports custom flows, so you can use anything you can put into a bash script.
No. env0’s custom flows let you run anything you can script, when creating, updating and destroying you environments. You can run Ansible, kubectl, the AWS CLI, or even your own application code.
Before deploying your environment, env0 will inject custom tags into your Terraform code. 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.
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!
State files are stored separately per environment, in an encrypted S3 bucket. Each organization’s files are encrypted using a dedicated key. If you prefer saving your state files on your own infrastructure - we fully support any Terraform backend.
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.com is a SaaS offering. If you’d like to run env0 on your own infrastructure - get in touch with our enterprise team.
