Manage your project

The Adobe Commerce on cloud infrastructure project includes all code in Git branches, associated environments, and applications. Applications have environments and services that run on them including a database, web server, and caching server.

We provide a Project Web Interface and CLI commands to fully manage all aspects of your project. You have full access to all environments for Starter and Pro environments. You can also use SSH and CLI commands to manage your environments.

To manage your project, environment, and branches, see:

Project and environment variables

The following sections detail more about project and environment variables:

Upgrade and patch

To upgrade and patch Adobe Commerce on cloud infrastructure projects, see:

Access the Project Web Interface

The Project Web Interface provides features to create, manage, and deploy code in Integration, Staging, and Production environments for Starter and Pro plans.

To access your projects and environments:

  1. Log in to your account at
  2. Click Projects (Cloud).
  3. Locate your project and click View Project Page.

The View Project Page link displays for Account Owners only. If you are not an Account Owner, go to instead.

If you do not see any projects, you must contact the Account Owner or Super User associated with the project and request access.

Fastly and New Relic credentials

Your project includes Fastly and New Relic. The project details display information for your project plan and important licenses and tokens for these integrations. Only the License Owner has initial access to the credentials and services. You should provide these credentials to technical and developer resources as needed.

  • Fastly provides content delivery (CDN), image optimization, and security services (DDoS and WAF) for your Adobe Commerce on cloud infrastructure projects. See Get Fastly credentials.

  • New Relic provides application metrics and performance information for Staging and Production environments.

To review your integration tokens, IDs, and more:

  1. As the Adobe Commerce on cloud infrastructure Account Owner, log in to your project.

  2. In the upper right corner, click <your name> > Account Settings.

    Go to account settings

  3. On your account page, click View Details for your project to open general settings and plan details.

    View your project details

  4. On your project details page, scroll to and expand the New Relic and Fastly sections to review service credentials.

    Your New Relic credentials

Access the project and environments

When you first login, a list of projects you have access to displays. As an Account Owner, you can only see your company’s project. An Adobe Solutions Partner may see multiple projects for all of the clients they support.

Click on a project to access branches and more. On the page, you will see a hierarchy of environments named by the Git branch.

For Starter, you will see a hierarchy of branches starting from Master (Production). Any branches you create display as children from Master. We recommend creating a Staging branch, then branching from that for your Integration development. For more information, see Starter architecture.

Starter branch hierarchy

For Pro, you will see a hierarchy of branches starting from Production to Staging to Integration. The Enterprise icon icon indicates these branches deploy to a dedicated server, used by Staging and Production. Any branches you create display as children from Integration. For more information, see Pro architecture.

Pro branch hierarchy

The following table details the branches for Pro:

Branch Environment Description
(no branch) Global Master This “branch” captures global project changes including adding user accounts and variables. Important: Do not create branches from or merge to Global Master.
production Production This is a child branch from master with a deployment target. You cannot branch from this branch. You merge code from master to this branch to launch your site with updated configurations and code.
staging Staging This is a child branch from master with a deployment target. You cannot branch from this branch. You merge code from master to this branch to test in a pre-production environment.
master Integration master The master branch of the single repository. In the Project Web Interface, this is called Integration. You branch from master for your development on your local, generating an environment when you push code. When this code is complete, you merge to staging and production.

To access an environment store and admin, select a branch and click Access Site. A list of store URLs and SSH command display. Select the URL to view the store in that environment.

Access your project

The Pro plan Production and Staging environments include three nodes that you can access using the following links:

  • Load balancer URLs:

    • http[s]://<your domain>.c.<project ID>
    • http[s]://<your staging domain name>.c.<project ID>
  • Direct access to one of the three redundant servers:

    • http[s]://<your domain>.{1|2|3}.<project ID>
    • http[s]://<your staging domain name>.{1|2|3}.<project ID>

    The production URL is used by the content delivery network (CDN).

If you have inactive Git branches of code, you can toggle displaying the branches in the hierarchy.

Show or hide inactive branches

Configure environments

You can manage variables and settings for Production, Staging, and Integration environments through this interface, or with CLI commands. Click Configure environment to create and manage environments, each of which corresponds to a Git branch.

Access your project

This displays the following page, which enables you to configure settings, variables, routes, and users.

configure environments

Environment configuration variables

On the Variables tab, you can view, create, and manage environment variables for your project. For example, after we add your project to the Adobe Commerce on cloud infrastructure Fastly service account, you can view the Fastly API token and service ID credentials as shown in the following example:

Environment variables fastly credentials

You can also list and review environment variables using the following magento-cloud CLI command.

magento-cloud variable:get -e <environment ID>

Configure the project

Click edit project (edit) to display users and deploy keys associated with the project. You can modify access and permissions across the entire project and per environment (or branch). See Manage user access.

configure project