Apigee hybrid is a platform that consists of a runtime plane, management plane, and a set of GCP services that let you manage APIs across multi-cloud environments.


The different components of Apigee Hybrid are currently in different stages of the release cycle:

  • Hybrid Alpha refers to the management plane and GCP services that you use to manage Hybrid deployments.
    • The management plane includes the following:
      • Apigee APIs: A set of endpoints that you use to manage your API proxies. For more information, see Apigee APIs.
      • Hybrid UI: The web-based interface with which you create, manage, and deploy API proxies and related entities. The Hybrid UI is similar to the Edge UI, with differences that are described in Administration).
      • Unified Analytics Platform (UAP): Processes incoming analytics and deployment status data. For more information, see Analytics and deployment status data collection.
    • GCP services used by Hybrid include:
      • Projects: GCP projects are bound to Hybrid-enabled organizations for resource management and configuration
      • IAM and Google Accounts: User and role management
      • Stackdriver: Logging and metrics collection and analysis
  • Hybrid Beta 2 refers to the runtime that you deploy on your Kubernetes cluster.

    The Hybrid Beta 2 runtime is a set of containerized applications including:

    • Cassandra (runtime datastore)
    • Istio Ingress
    • MART
    • Message Processors
    • Synchronizer
    • UDCA (logs and metrics)

    For information on how to install Hybrid Beta 2 runtime, see Runtime installation overview.

For more information:


The Apigee documentation refers to the following different flavors of Apigee APIs:

  • Apigee APIs (Alpha):
    • Purpose: Configure and manage your Hybrid-enabled Apigee organization
    • Base URL: “apigee.googleapis.com”
    • Notes: See the Apigee API documentation
  • Apigee Edge APIs:
    • Purpose: Configure and manage Apigee Edge (and Edge for Private Cloud)
    • Base URL: “api.enterprise.apigee.com”
    • Notes: Not for use with a Hybrid-enabled Apigee organization


To install and use Hybrid, you must have an Apigee organization that is bound to a GCP project. This is done for you by Apigee in a process known as provisioning.

An Apigee organization is a container for all the entities in an Apigee account, including API proxies, API products, API packages, apps, and developers. This document uses the terms Apigee organization or Hybrid-enabled organization interchangeably.

Note that an Apigee organization is not the same as a GCP organization. Where the possibility of ambiguity exists, this document should specify that the “organization” is an Apigee organization.

Additional terminology

For additional definitions of Hybrid-related terminology, see the Glossary.