Subscription entitlements

This page applies to Apigeeand Apigee hybrid.

View Apigee Edge documentation.

Apigee Subscription 2024 entitlements

The following table compares Subscription entitlements for the Apigee offerings for Subscription 2024 plans. For older plans, see the Subscription 2021 entitlements. For information on evaluation plans, see Compare evaluation and paid organizations in Apigee .

All offerings and add-ons are subject to Apigee product limits .

^{(1) Additional call volume available for purchase. Standard API proxy calls are metered 1/5 of an Extensible API proxy call. See API proxy types for information on Standard and Extensible proxy types. A customer can use API calls in Apigee, Apigee hybrid, and Apigee Adapter for Envoy use cases.
(2) An Apigee Environment can be provisioned in one or more Google Cloud regions by attaching them to one or more Apigee instances . Each region association is counted as an "active" environment. Customers have the flexibility to leverage their Env entitlements to attach the environment to a single instance or to multiple instances.
(3) hybrid orgs do not differentiate Standard and Extensible proxies at this time. Proxy deployment units are tracked for hybrid orgs.
(4) Enhanced per environment proxy limit feature for hybrid implementations is exclusively available as part of the 2024 subscription plan. Contact sales . See also Enhanced limits .
(5) No restriction on hybrid org creation.
(6) Restricted for Anthos only to run/operate Apigee hybrid components listed here. Additional Anthos entitlements require an Anthos subscription.}

Apigee Subscription 2021 entitlements

The following table compares Subscription entitlements for the Apigee offerings for Subscription 2021 subscription plans. For newer plans, see Subscription 2024 entitlements.

All offerings and add-ons are subject to Apigee product limits .

^{(1) Additional call volume available for purchase. A customer can use API calls in Apigee, Apigee hybrid, and Apigee Adapter for Envoy use cases.
(2) For information about pricing for Google Cloud networking products, see All networking pricing .
(3) Restricted for Anthos only to run/operate Apigee hybrid components listed here. Additional Anthos entitlements require an Anthos subscription.
(4) Org Pack, Environment Pack, and Network Data Packs are only available for Apigee.
(5) A successful integration call is the completion of an integration workflow without errors due to the incorrect functioning of the Application Integration platform. Call failures not attributable to the platform, such as failures to connect to targets (including other Cloud services) due to customer configuration errors or target server downtimes, do not count against the SLA. Integration UI and Management service requests are not included in this SLA.
(6) Concurrent integrations are the number of integrations that are executing concurrently (at the same time). Total concurrency packs not to exceed a total of 10,000 concurrent integrations. Please contact sales for higher limits.
(7) Class G covers 1st party Google Services (for example, BigQuery), and does not cover hosted/managed services (eg: CloudSQL MySQL). Class 1 covers some basic connectors (for example, REST and SOAP).
(8) Technical limit of 250 Connections per region. Additional connections can be entitled upon request. Connection Units are an abstraction of Connection purchases, which can be used flexibly to consume various combinations of Connections, Connector Types, Classes, or All Classes. Purchased units may be allocated towards the connection options you choose. For example, with one Connection Unit Pack (50 units), you can use 15 units for three MySQL Connections (Class 2 Connectors are five units per connection) for the dev, test and prod instances of your database. In addition, you can use 20 units for the All Class G Connectors to configure as many connections for Google services as you need (up to any technical limits).
(9) An Apigee Organization can be configured to span across one or more Google Cloud regions . Customers have the flexibility to leverage their Org entitlements to provision in a single region or expand the same Org to multiple regions . When they are configured in a single region, it is counted as a single "Org unit". To expand their Org to more than one region, customers need entitlements to Org units. For example, with the Enterprise Plus tier, customers can provision a total of 6 Org units. It could be used to provision a single Org expanded across 6 regions or create 6 Apigee Orgs (or any combination in between). Additional Org units can be purchased via Org Packs.
(10) An Apigee Environment can be provisioned in one or more Google Cloud regions by attaching them to one or more Apigee instances . Customers have the flexibility to leverage their Env entitlements to attach the environment to a single instance or to multiple instances. When they are attached to one Apigee Instance, it is counted as a single "Env unit". To expand their Env to more than one instance, customers need entitlements to Env units. For example, with the Enterprise Plus tier, customers can attach 30 environments to a single Apigee instance or 15 environments to two Apigee instances and so on. Customers can purchase additional entitlements through Env packs.
(11) Each additional Apigee Environment added through purchase of an Org or Environment pack includes 50 additional API proxy and shared flow deployments. This entitlement does not impact the calculation of proxy deployment units .}

For support plan options, see Cloud Customer Care .

For entitlements information on Edge products, see Edge entitlements .