Manage your project

The Magento Commerce (Cloud) 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 may need to continue to use SSH and CLI commands for some aspects of Pro plan Staging and Production environments.

Updating your Pro project These sections include instructions for Pro projects updated to manage Staging and Production through the Project Web Interface. For more information adding this management to existing Pro projects (created before 10-23-2017), see Add Staging and Production to Pro projects UI.

If you do not request this update, you must use CLI commands or tickets to modify settings, variables, routes, and more for Pro plan Staging and Production 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 Magento, see:

Access the Project Web Interface

With your Magento Commerce (Cloud) account created, you can log into the Project Web Interface at

Log in to a project

Access the project and environments

When you first login, a list of projects you have access to displays. As a Project Owner, you may only see your company’s project. A Magento Solution 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

If you are an existing Pro merchant, and have not ticketed to add Staging and Production to your UI, you will see only Integration master and any created branches.

Pro branch hierarchy (original)

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 environment includes three nodes that you can access using the following links:

  • Load balancer URL: http[s]://<your domain>.c.<project ID>
  • Direct access to one of the three redundant servers: http[s]://<your domain>.{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

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).

configure project