---
schema_version: "1"
id: b8fb7ca58ed7f7eedec639dd3b16a95cc8709c2c5c41485aa869219df33beb4d
title: Deploying Agent Network Ingress and Egress Managed Omni Gateways
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/latest/gateway-managed-ingress-egress.md
canonical_url: https://docs.mulesoft.com/gateway/latest/gateway-managed-ingress-egress
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 521ab85f4a3d6ff06210649ccdb35b785551629693eb8777ff4a3d03fda2a472
description: MuleSoft Documentation Site
release: "1.14"
latest: true
---
---
product: Omni Gateway
version: 1.14
is-latest-version: true
---

# Deploying Agent Network Ingress and Egress Managed Omni Gateways

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

Agent Network deployments require both an ingress and egress Omni Gateway. The ingress Omni Gateway
sits in front of broker and API endpoints to manage and enforce policies on traffic entering the
network. The egress Omni Gateway sits on outbound paths from brokers and agents to external agents
and enforces policies, manages connections, and emits telemetry data.

The only functional difference between ingress and egress Omni Gateways, is that the egress Gateway
doesn’t have a public endpoint. Only clients inside the same private space as the egress gateway can
make requests to it. Traffic leaving the private space to external services passes through the
egress gateway.

![Agent Network showing agents and MCP servers defined in YAML and published to Exchange, with traffic through Omni Gateway, governed by API Manager, and observed in Monitoring and Visualizer](/mulesoft/current/en-us/gateway/latest/_images/agent-fabric-architecture.png)

> [!NOTE] For a more detailed description of this architecture diagram, see
> [Agent Network Architecture](https://docs.mulesoft.com/agent-network/latest/af-agent-networks#agent-network-architecture).

## Deploy Ingress and Egress Managed Omni Gateways

The easiest way to deploy your Agent Network ingress and egress Omni Gateways is by using Anypoint
Code Builder or Anypoint Command Line Interface (CLI):

- [Set Up Agent Network Gateways by Using Anypoint Code Builder](https://docs.mulesoft.com/agent-network/latest/af-get-started#setup-gateways)

- [Set Up Agent Network Gateways by Using Anypoint CLI](https://docs.mulesoft.com/anypoint-cli/latest/agent-fabric#agent-network-setup-gateways)

To manually deploy both ingress and egress managed Omni Gateways using the Runtime Manager UI, see
[Deploy a Managed Omni Gateway](https://docs.mulesoft.com/gateway/latest/gateway-managed-set-up).

For ingress gateways, configure a **Public endpoint** in the advanced options **Ingress** tab. For
egress gateways, verify that there’s no **Public endpoint** configured. To prevent confusion, give a
descriptive name defining the gateway as either ingress or egress.

## Apply Inbound and Outbound Policies

Inbound policies are policies that are enforced on all traffic accessing an instance’s endpoint.
Outbound policies are policies that are enforced on all traffic accessing a specific URL and are
only applied to that URL. For example, for an agent instance that has multiple upstreams, an inbound
client ID enforcement policy enforces client ID verification for all traffic accessing the agent
instance. However, an outbound policy might be applied to only one of the instance’s upstream.

## Next Steps

- [Requirements and Limits for Omni Gateway](https://docs.mulesoft.com/gateway/latest/review-prerequisites)

- [Setting Up Self-Managed Omni Gateway](https://docs.mulesoft.com/gateway/latest/gateway-set-up)