> ## Documentation Index
> Fetch the complete documentation index at: https://docs.envzero.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Running Multiple Self-Hosted Agents

> Run multiple self-hosted and SaaS agents in a single env zero organization with per-project assignment for isolation and security boundary separation.

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](https://search.opentofu.org/provider/env0/env0/latest) 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.

<Info>
  **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](/guides/admin-guide/variables/#secrets). Make sure to verify compatibility with your specific environment before selecting this option.
</Info>

## 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](/guides/admin-guide/self-hosted-kubernetes-agent/overview).

Projects not assigned to a specific agent use the organization’s default self-hosted agent.

## Next steps

* [Self-Hosted Agents Overview](/guides/admin-guide/self-hosted-kubernetes-agent/overview) - Create agent pools and assign them to projects.
* [Self-Hosted Kubernetes Agent](/guides/admin-guide/self-hosted-kubernetes-agent/self-hosted-kubernetes-agent) - Install an agent on your Kubernetes cluster.
* [Running a Standalone Docker Agent](/guides/admin-guide/self-hosted-kubernetes-agent/standalone-docker-agent) - Run an agent as a Docker container for simpler setups.