---
schema_version: "1"
id: 362dcf6fd8089a64b4f6c2b8c2f1547f1c6c3a920e2e94f5e9d0917720c45ac1
title: Deploy Agent Network Instances
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/agent-network/1.0/af-deploy-agent-network-targets.md
canonical_url: https://docs.mulesoft.com/agent-network/1.0/af-deploy-agent-network-targets
source_site: docs.mulesoft.com
content_type: documentation
content_hash: e16cbc9be18d6a36f8f2a559f17763fc8971d044db9456f057835e59c90c42d1
description: MuleSoft Documentation Site
release: "1.0"
latest: false
---
---
product: Building Agent Networks
version: 1.0
---

# Deploy Agent Network Instances

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Deploy your agent network instance to a deployment target. You can deploy to a CloudHub 2.0 shared
space, a CloudHub 2.0 private space, or to a Runtime Fabric. When you deploy, Omni Gateway secures
inbound traffic to your agent network and outbound traffic from your brokers, agents, and MCP
servers.

These Omni Gateway policies are applied automatically at deployment.

<table><colgroup><col> <col></colgroup><thead><tr><th>Agent Type</th><th>Policy</th></tr></thead><tbody><tr><td><p>Broker</p></td><td><div><div><ul><li><p>A2A Agent Card policy</p></li><li><p>Tracing policy</p></li><li><p>Agent Connection Telemetry policy</p></li></ul></div></div></td></tr><tr><td><p>Agent</p><p>(ingress and egress)</p></td><td><div><div><ul><li><p>A2A Agent Card policy</p></li><li><p>Tracing policy</p></li><li><p>Agent Connection Telemetry policy</p></li></ul></div></div></td></tr><tr><td><p>MCP Server</p><p>(ingress and egress)</p></td><td><div><div><ul><li><p>MCP Support policy</p></li><li><p>Tracing policy</p></li><li><p>Agent Connection Telemetry policy</p></li></ul></div></div></td></tr></tbody></table>

## Before You Begin

Make sure you review the [prerequisites](https://docs.mulesoft.com/agent-network/1.0/af-get-started#before-you-begin).

When you deploy your agent network, an instance is deployed for each connection defined in your
agent network. If your agent network contains brokers, an instance is deployed per broker.

> [!IMPORTANT] You can’t deploy existing agent network projects to a CloudHub shared space. If you
> want to deploy to a shared space, switch to an agent network 2.0 project.

## Deploy Your Network Using MuleSoft Vibes

MuleSoft Vibes can help you deploy your agent network instances. For more information, see
[Creating API Specs with MuleSoft Vibes](https://docs.mulesoft.com/anypoint-code-builder/vibes-api-ai-create-spec).

1.  In the Anypoint Code Builder activity bar, click the agent icon
    ![](/mulesoft/current/en-us/agent-network/1.0/_images/af-acb-dev-agent-icon.png).

2.  Tell the agent that you want to deploy your agent network. MuleSoft Vibes does the rest.

To get started, try one of these suggested messages.

- Deploy my agent network project to the production environment.

- Deploy the hello-world-network project to staging.

- Deploy agent network project at /path/to/project to dev environment with specific gateways.

- Deploy my agent network to CloudHub 2.0.

## Deploy Your Network Using Anypoint Code Builder

1.  If you’re not logged in already, log in to your Anypoint Platform account.

2.  In Anypoint Code Builder, choose one of the following:

3.  In Explorer, right-click a project file and select **Deploy Agent Network**.

4.  From the Command Palette, run this command: **MuleSoft: Deploy Agent Network**.

5.  In Deploy Agent Network, specify the environment, target space, gateways, and other deployment
    information. If you don’t see any deployment targets to select, then you need to set up your
    target deployment space and set up gateways. For instructions, see
    [Get Started with Agent Networks](https://docs.mulesoft.com/agent-network/1.0/af-get-started).

6.  Select **Deploy**.

7.  Your instances are deployed and ready to be tested. An instance is deployed for each connection
    defined in your agent network. If your agent network contains brokers, one instance is deployed
    per broker.

Next, discover your agent network assets in **Agents & Tools** in Exchange, view your agent network
in Agent Visualizer, apply a governance policy in API Manager, or monitor your agent network
activity in Anypoint Monitoring.

## Deploy a Network Using the Anypoint CLI

If you run operations within a CI/CD environment, you can use Anypoint CLI’s plugin to set up,
create, build, publish, and deploy agent networks. For more information, see
[Build Agent Networks in a CI/CD Environment](https://docs.mulesoft.com/agent-network/1.0/af-build-agent-networks-in-a-ci-cd-environment).