Skip to main content
With env zero, you can use both self-hosted and SaaS agents within the same organization, allowing for flexibility and smooth transitions between agent types.

​
Hybrid Agent Setup

A hybrid setup lets you configure the most suitable agent type for each project, optimizing scalability, resource management, and overall workflow efficiency. A common use case is utilizing the env zero provider to provision all env zero resources. You can configure a single project with the env zero Cloud Agent to provision all other projects and resources through the env zero provider, while the remaining projects operate on a self-hosted agent to manage actual cloud infrastructure deployments.
You can also choose to keep working with the env zero Cloud Agent.However, please note that it does not support certain version control systems (GitHub Enterprise, GitLab Enterprise and Bitbucket Server) and secret variables for self hosted agents. Make sure to verify compatibility with your specific environment before selecting this option.

​
Use Cases for Multiple Agents

  • Environment isolation - Separate agents for production and non-production workloads.
  • Geographic distribution - Run agents in different regions or cloud providers.
  • Security boundaries - Isolate agents that handle sensitive resources.
  • Resource management - Dedicate agents to projects with different resource requirements.

​
Managing Agent Pools and Assignments

To create agent pools, manage secrets, and assign agents to projects, see Self-Hosted Agents Overview. Projects not assigned to a specific agent use the organization’s default self-hosted agent.