Supported versions:
Unsupported versions:
You can now try out the hybrid UI and add a new environment. Without an environment, you have nowhere to deploy your API proxies. Additionally, if you don’t create an environment as described in this section, then several steps in the hybrid runtime installation process will fail.
The hybrid UI includes functionality that lets you do the following in a hybrid-enabled organization:
To access the hybrid UI and add an environment:
If this is the first time you are logging in, hybrid displays a consent dialog box:

Your browser navigates to the hybrid UI main landing page:


Note that when you select a hybrid-enabled organization from the drop-down list, the hybrid UI displays the Apigee organization name and the GCP project name in the header. In many cases, the Apigee organization name and GCP project name are the same.
The Environments view is displayed, with no environments (yet):

The Define a new environment dialog box is displayed:

For example, "my-environment" or "test".
You will also use this name in the overrides.yaml file when you
install the hybrid runtime.
The Display name and the Environment name can be different.
Apigee creates the new environment and indicates that it is "Pending Provisioning":

In a few moments, it will be "provisioned":

However, you’re not quite done. You also need to add your new environment to the runtime’s overrides.yaml file—but first you've got to install the runtime, so let's not get ahead of ourselves.
To continue with the installation, see Runtime installation: Before you begin.
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-07-23 UTC.