New Apigee hybrid organizations can be provisioned with the ability to deploy more than 50 proxies per environment enabled. This feature is also available for Apigee X.
The maximum number of deployed API proxies and shared flows per organization is 6000.
The maximum number of proxy deployment units per Apigee instance is 6000.
The maximum number of API base paths per Apigee organization is 3000.
When more than 50 proxies are deployed in an environment, Apigee will automatically partition the environment into several distinct replica sets, each containing a subset of proxies deployed in the environment. These replica subsets are equivalent in behavior to a single environment in the way it loads and runs a set of proxies and other environment resources. This will be transparent to the user, and you can continue to use the environment as you would a single environment.
Provisioning
To provision a new org with the enhanced number of proxies per environment:
Provide your project ID and organization name to your Apigee representative to set up the enhanced proxy limit.
Check for the existence of runtime pods containing the substring auto:
kubectl get pods -n APIGEE_NAMESPACE | grep auto
Your output should look similar to the following:
kubectl get pods -n apigee | grep auto
apigee-runtime-hybr-test-env-auto-2ecde5a-bca5298-4gsrw 1/1 Running 0 98m
Limitations
Apigee offers enhanced per-environment proxy limits only on newly created orgs. Converting existing orgs to use enhanced proxy limits is not supported.
Backups of an organization that was created without enhanced proxy limits enabled cannot be restored to an organization created with the feature enabled.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[],[],null,["# Enhanced per-environment proxy limits\n\nOverview\n--------\n\n\nNew Apigee hybrid organizations can be provisioned with the ability to deploy more than 50 proxies per environment enabled. This feature is also available for [Apigee X](/apigee/docs/api-platform/reference/limits#api-proxies).\n\n- The maximum number of deployed API proxies and shared flows per organization is 6000.\n- The maximum number of proxy deployment units per Apigee instance is 6000.\n- The maximum number of API base paths per Apigee organization is 3000.\n\n\nWhen more than 50 proxies are deployed in an environment, Apigee will automatically partition the environment into several distinct replica sets, each containing a subset of proxies deployed in the environment. These replica subsets are equivalent in behavior to a single environment in the way it loads and runs a set of proxies and other environment resources. This will be transparent to the user, and you can continue to use the environment as you would a single environment.\n| **Note:** Enhanced proxy limits feature is only available for new hybrid organizations. This feature is available exclusively as part of the [2024 subscription plan](https://cloud.google.com/apigee/docs/api-platform/reference/subscription-entitlements#subscription-2024-entitlements), and is subject to the entitlements granted under that subscription. They cannot be enabled on existing organizations.\n\nProvisioning\n------------\n\n\nTo provision a new org with the enhanced number of proxies per environment:\n\n1. Provide your project ID and organization name to your Apigee representative to set up the enhanced proxy limit.\n2. Follow the Apigee hybrid [installation instructions](/apigee/docs/hybrid/v1.15/install-before-begin) to provision the hybrid org. In your overrides file, add the [`enhanceProxyLimits`](/apigee/docs/hybrid/v1.15/config-prop-ref#enhanceproxylimits) top-level property: \n\n ```\n enhanceProxyLimits: true\n ```\n\n Apply changes to `enhanceProxyLimits` by updating the `apigee-org` chart and the `apigee-virtualhost` chart for every environment group.\n | **Alert:** Do not change this value once set.\n3. Create and deploy a proxy.\n4. Verify that the enhanced proxy limits are enabled:\n 1. Get the name of the configmap for your Apigee namespace: \n\n ```\n kubectl get configmap -n APIGEE_NAMESPACE\n ```\n\n\n Your output should look similar to the following: \n\n ```\n NAME DATA AGE\n ...\n apigee-synchronizer-hybr-example-env-dggroupconfi-bc7726a 3 12m\n ...\n ```\n 2. Check the named configmap: \n\n ```\n kubectl get configmap -n APIGEE_NAMESPACE CONFIGMAP_NAME -o yaml\n ```\n\n\n Where \u003cvar translate=\"no\"\u003eCONFIGMAP_NAME\u003c/var\u003e is the name of the configmap from the previous step.\n\n\n Your output should look similar to the following: \n\n kubectl get configmap -n apigee apigee-synchronizer-hybr-example-env-dggroupconfi-bc7726a -o yaml\n apiVersion: v1\n data:\n contract.revid: \"2\"\n contract.uid: 4a792429-20fb-4b29-bed3-3f8ce7b3353e\n deploymentGroups: auto-2ecde5ae-04\n kind: ConfigMap\n metadata:\n creationTimestamp: \"2024-05-15T20:04:26Z\"\n labels:\n apigee.cloud.google.com/platform: apigee\n name: apigee-synchronizer-hybr-test-env-dggroupconfi-bc7726a\n namespace: apigee\n ownerReferences:\n - apiVersion: apigee.cloud.google.com/v1alpha2\n blockOwnerDeletion: true\n controller: true\n kind: ApigeeEnvironment\n name: hybrid-dev--test-env-4f37f70\n uid: 696e84ec-5c54-4858-a2e0-e36db5ff3506\n resourceVersion: \"2520100\"\n uid: b297bd33-300a-48cf-bf85-6c7cd0ff288f\n\n5. Check for the existence of runtime pods containing the substring `auto`: \n\n ```\n kubectl get pods -n APIGEE_NAMESPACE | grep auto\n ```\n\n\n Your output should look similar to the following: \n\n kubectl get pods -n apigee | grep auto\n apigee-runtime-hybr-test-env-auto-2ecde5a-bca5298-4gsrw 1/1 Running 0 98m\n\nLimitations\n-----------\n\n\nApigee offers enhanced per-environment proxy limits only on newly created orgs. Converting existing orgs to use enhanced proxy limits is not supported.\n\n\nBackups of an organization that was created without enhanced proxy limits enabled cannot be restored to an organization created with the feature enabled.\n\nKnown issues\n------------\n\n- Proxy chaining:\n - Proxy chaining with mTLS is not supported. See [known issue 392135466](/apigee/docs/release/known-issues#392135466)."]]