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.
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).
Direct access to your environments
Fully access your Magento development and deployment through the Project Web Interface (a UI console) and CLI commands via SSH access. Your servers are within reach from development to production in the Amazon Web Services (AWS) cloud.
We deploy databases, web server, and caching servers across three environments for end-to-end testing while supporting continuous integration.
For Starter plan subscriptions, you receive four environments including the following:
- Integration: The ultimate developer environments, Integration provides three testable environments. Each environment includes an active Git branch, database, web server, caching, services, environment variables, and configurations.
- Staging: We highly recommend you create an active
stagingbranch as one of the three Integration environments. Create this branch directly from
master. As code and extensions pass your tests, you can merge your Integration branches to
staging. This Staging environment becomes your pre-Production testing environment. It includes the
stagingactive branch, database, web server, caching, services, environment variables, configurations, and Production services like Fastly and New Relic.
- Production: When code is ready and tested, all code merges to
masterfor deployment to the Production live site. This environment includes your active
masterGit branch, database, web server, caching, services, environment variables, and configurations. This environment includes additional services like Fastly.
For Pro subscriptions, you receive the following environments:
- Integration: The ultimate developer environment, Integration provides eight testable environments including a
master. Each environment includes an active Git branch, database, web server, caching, services, environment variables, and configurations. Actively develop, deploy, and test your code before merging to
masterto push to Staging.
- Staging: As code and extensions pass your tests, deploy the Integration
masterGit branch to Staging for pre-Production testing. This environment includes a database, web server, caching, services, environment variables, configurations, and Production services like Fastly and New Relic.
- Production: When code is ready and testing complete, deploy the Integration
masterGit branch into Production for your live store. The container includes a three node high-availability architecture for your data, services, caching, and store. This is your live, public store environment with environment variables, configurations, and Fastly.
Details about the cloud
- Each plan includes Integration active environments 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:
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, settng 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:
- Onboarding tasks of first things to do right after signing up.
- Onboarding Portal management for new trials to get started.
- Sign up for status updates for components and services.
- For new non-trial projects, see prepare your project environments to give your technical staff and solution experts access, create your project, and get started.
To better understand Magento Commerce, your plan, architecture, and workflows, see the following starting points:
- Technologies and requirements
- Deployment process
- Local environment setup
Learn more about Magento 2
If you would like to learn more about Magento 2, see the following resources:
- All documentation home page
User guides (how to use options in the Magento Admin)
- Magento 2.2.x
- Front end development
- B2B user guide
- 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: Custom code and features developed as a module to install and integrate into your Magento implementation. You can purchase these modules from Magento Marketplace, directly from developers, or create your own. We recommend developing custom code as a module to extend Magento functionality.
- Onboarding Portal: A web interface for the Project Owner to get started with a free 30-day trial Starter or Pro account.
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.
You can enter a support ticket through the Project Web Interface:
- Log in to your Magento Cloud account.
Click Support > Submit ticket from the top menu.
The following figure shows an example.
- Follow the prompts to open an issue with Support. Support will respond to your ticket in a timely manner.