View
Apigee Edge documentation.
Apigee Adapter for Envoy is an Apigee-managed API gateway that uses Envoy to proxy API traffic. Envoy is a popular, open source edge and service proxy designed for cloud-native applications. You can run Apigee Adapter for Envoy on premises or in a multi-cloud environment.
With Apigee Adapter for Envoy, you get a relatively small footprint API gateway application running close to your backend applications. Apigee Adapter for Envoy relies on Apigee for:
You can use the Apigee Adapter for Envoy in the following context:
The following figure shows the high level architecture for Apigee Adapter for Envoy. This architecture consists of management plane components deployed on Google Cloud Platform (GCP) and data plane components running remotely on premises or in a cloud provider environment. The data plane includes the Envoy proxy and Apigee Remote Service. The role of each component is described following the figure.
Moving the API management component close to backend target applications can reduce network latency. While you can install Apigee on-premises in a private cloud, a full deployment of Apigee is necessarily large and complex to support its full feature-set and data-heavy features like key management, monetization, and analytics. This means that deploying Apigee on premises in each data-center is not always desirable.
Benefits of using Apigee Adapter for Envoy include:
Reduced latency of API traffic for services that run in close proximity.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-06-09 UTC.
