API Gateways & Agents
The API Control Plane follows a hub-and-spoke architecture where the centralized Control Plane communicates with distributed Data Planes through agents. API Gateways represent your gateway platform instances, and agents are the lightweight connectors that translate Control Plane commands into gateway-specific operations.
The Control Plane supports a wide range of gateway platforms:
| Platform | Agent required |
|---|---|
| Boomi API Gateway | No (managed directly) |
| Amazon Web Services API Gateway | Yes |
| Apigee / Google Apigee | Yes |
| Azure API Gateway | Yes |
| Broadcom Layer7 | Yes |
| Gravitee.io | Yes |
| Kong Community | Yes |
| MuleSoft | Yes |
| WSO2 | Yes |
| Boomi Cloud API Management | Yes |
Key concepts
- API Gateway — A registered gateway platform instance. Multiple gateways of different types can be managed from a single Control Plane tenant
- Agent — A Docker-based component that runs alongside your gateway and handles bidirectional communication with the Control Plane. The agent transmits deployments, collects metrics, and enables API discovery. Minimum requirements: 512 MB RAM, 1 CPU, 5 GB disk space
- Agent Token — A secret token used to authenticate the agent with the Control Plane. Generated once and must be stored securely
- Environment type — Gateways can be
SINGLE(one environment per gateway) orMULTI(multiple environments sharing a gateway)
Related guides
- API Gateways — Register and manage gateway instances
- Agents — Manage gateway agents and their tokens