- No underlying infrastructure setup and management - env zero takes care of the setup as opposed to other approaches, where you need to do all the setup and management yourself (for example, S3 Backend requires you to create an S3 Bucket and an optional DynamoDB Table for locking beforehand)
- Security - env zero stores the state securely for you and assures only you can access it
- State consistency - Remote Backends assure that users won’t overwrite each other’s state with a locking mechanism and that they receive the most recent state on every Terraform operation
- Local runs - By providing the Remote Backend configuration and a successful login, users can run Terraform operations locally while still working on a shared state.
- No Terraform Backend configuration when running inside env zero - you don’t have to provide any type of configuration; you just deploy your code as is, and env zero will automatically configure it to use the Remote Backend
- States UI - view the current version of your state as well as all of the previous versions
- Correlation of Deployment to State - easily figure out which deployment is responsible for a specific change to your state (Coming soon)