Welcome to Magento Commerce (Cloud)

Magento Commerce (Cloud), formerly Enterprise Cloud Edition, is a managed and automated hosting platform for Magento specifically created for Cloud infrastructures. This version combines Magento Commerce, Cloud infrastructure hosting, with a few differences and added features including Git integration and key environments for development, staging, and live production.

Code, test, and deploy across Integration, Staging, and finally Production environment for continuous integration of your store.

For full release notes, see Release Information and Magento Commerce (Cloud) third-party licenses.

Magento Commerce (Cloud) plans and subscriptions

Magento Commerce (Cloud) provides plan options based on the size of your business. Each plan includes Magento Commerce (Cloud), support, and Cloud-based hosting and infrastructure on a subscription basis. Want to sign up? We encourage starting with a free 30-day trial to begin working with Magento.

For a list of our plans and breakdown of features, see Subscriptions and plans.

To start your free 30-day trial, see our Plan Comparison. You can select a plan that fits your business and start a trial with a newly provisioned project and code-base with the latest version of Magento Commerce (Cloud).

Details about the cloud

  • Each plan includes Integration environment for development, testing, and integrating services. Additional active environments are available at additional cost.
  • All environments run with active Git branches of code.
  • You have an unlimited number of inactive Git branches.
  • You can add fully managed services like MySQL, Elasticsearch, Redis, RabbitMQ, and so on, without requiring external add-ons.
  • We use a robust Composer build process.
  • You can increase the amount of memory and CPU as needed.

Technologies and requirements

You should become familiar with the following technologies:

See Technologies and requirements, Pro architecture, and Starter architecture for details and additional technologies.

Where do I get started?

If you have experience with Magento Commerce 2 or our cloud implementation, we recommend reviewing content in these DevDocs to understand the differences between Magento Commerce and Magento Commerce (Cloud). If you are new to Magento and the Cloud, this guide introduces all aspects from building a project, setting up your local, continuous deployment across environments, and going live.

If you create your account with the 30-day trial, we set you up quickly to get started. When you sign-up for the trial, we auto-provision your project with the latest version of Magento Commerce as a base template.

To get started, see:

To better understand Magento Commerce, your plan, architecture, and workflows, see the following starting points:

* [Starter architecture](/devdocs-archive/2.0/guides/v2.0/cloud/basic-information/starter-architecture.html)
*    [Starter develop and deploy workflow](/devdocs-archive/2.0/guides/v2.0/cloud/basic-information/starter-develop-deploy-workflow.html) *    Pro information:

* [Pro architecture](/devdocs-archive/2.0/guides/v2.0/cloud/architecture/pro-architecture.html)
*    [Pro develop and deploy workflow](/devdocs-archive/2.0/guides/v2.0/cloud/architecture/pro-develop-deploy-workflow.html) *    [Deployment process](/devdocs-archive/2.0/guides/v2.0/cloud/reference/discover-deploy.html) * [Local environment setup](/devdocs-archive/2.0/guides/v2.0/cloud/access-acct/first-time-setup.html)

Learn more about Magento 2

If you would like to learn more about Magento 2, see the following resources:

*    [Magento 2.0.x](http://docs.magento.com/m2/2.0/ee/user_guide/getting-started.html){:target="_blank"}
*    [Magento 2.1.x](http://docs.magento.com/m2/2.1/ee/user_guide/getting-started.html){:target="_blank"}   *    [Magento 2.2.x](http://docs.magento.com/m2/ee/user_guide/getting-started.html){:target="_blank"} *    Developer documentation

*    [Magento 2 Architecture guide](/devdocs-archive/2.0/guides/v2.0/architecture/bk-architecture.html){:target="_blank"}   *    [Front end development](/devdocs-archive/2.0/guides/v2.0/frontend-dev-guide/bk-frontend-dev-guide.html){:target="_blank"}
*    [Customizing the Magento software](/devdocs-archive/2.0/guides/v2.0/extension-dev-guide/bk-extension-dev-guide.html){:target="_blank"}
*    [Installation](/devdocs-archive/2.0/guides/v2.0/install-gde/bk-install-guide.html), though we recommend following [Prepare for local environment setup](/devdocs-archive/2.0/guides/v2.0/cloud/before/before-workspace.html){:target="_blank"}
*    [Configuration](/devdocs-archive/2.0/guides/v2.0/config-guide/bk-config-guide.html){:target="_blank"}   *    [B2B user guide](http://docs.magento.com/m2/b2b/user_guide/getting-started.html){:target="_blank"}

Helpful terms

  • Project: The project contains all of your code branches, environments from development to Production, and allows you to manage access and configurations. Initially only the Project Owner has access to the project. To gain access to the project, you must receive a user account, with permissions, and a Magento authentication key from the Project Owner.
  • Project Owner: Typically a “business user” in your business or finance organization, they are the point of contact with Magento regarding the account overall. They purchased the subscription plan, create the project, and add users to develop and deploy stores and sites.
  • Active Environment: An active environment is a fully accessible environment in the Integration enviornment. Each active environment provides a database, environment variables, routes, configurations, and one associated Git branch of code. You can access the Magento Admin and store to test as a merchant and customer for each of these environments, allowing you to develop custom code, add extensions, and integrate 3rd party systems in multiple environments for testing.
  • Inactive Environment: An inactive environment is a Git branch you either deleted from the Cloud Git repository or one that is not associated with the Cloud Git repository at all. For example, you might already have several Git branches with Magento code that you don’t need to use for Magento Commerce. As long as you don’t add those environments to the Cloud Git repo, they don’t count against your total of eight active environments.
  • Branch: Magento Commerce is a Git-driven code base and environment. All code is written in branches, with a parent and child structure. These branches allow you to develop new features and modifications in multiple independant branches concurrently with other work, merging up into a parent branch.
  • Local: Your local is a workspace for developing Magento code including added extensions and 3rd party integrations. The local is typically a Virtual Machine (VM) with an entire environment of software, packages, database, web server, and more prerequisites to support an installed Magento and cloned Git branches. We provide full details on how to set up your local for Magento development.
  • Module or Extension: Modules and extensions enhance Magento’s core functionality through custom code. Develop your own modules and extensions or purchase them directly from developers on the Magento Marketplace. We recommend developing custom code as a module to extend Magento functionality.

  • Project Web Interface: The Web Interface is a console for accessing your project, user accounts, and your project environments. You can modify environment settings, environment variables, routes, and manage environments. Access links (store URL, SSH, Git) are provided for active environments through the active Git branches. You use this interface for managing your project. The following environments are available through this interface:

    • Starter: Master and all environments branched from it

    • Pro: Integration and all environments branched from it. You may also have Staging and Production. For existing Pro merchants, you may need to have your interface updated to manage all environments.

      New projects provisioned starting October 23, 2017 will already have Staging and Production in their Project Web Interface. Any existing projects created before this date will need to enter a ticket to be converted.