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
Magento Commerce (Cloud) includes the following plans with different infrastructures for smaller to larger stores and supported products. For a breakdown of the plans and to start your free 30-day trial, see our Plan Comparison.
|Core features||All Magento 2 core features||All Magento 2 core features|
|Infrastructure and deployment||
|24x7 email support||24x7 monitoring and email support for the core application and the cloud infrastructure||24x7 monitoring and email support for the core application and the cloud infrastructure|
|Business Intelligence||Magento Business Intelligence Essentials giving you full visibility into your data with 75 reports and 5 dashboards available out of the box|
|High availability infrastructure||High availability architecture with a three-server setup in the underlying Infrastructure-as-a-Service (IaaS) to provide enterprise grade reliability and availability|
|Dedicated hardware||Isolated and dedicated hardware setup in the underlying Infrastructure-as-a-Service (IaaS) to provide even higher levels of reliability and availability|
|Dedicated Launch Manager||Dedicated technical account management for the initial launch period, starting with your subscription until your initial site launch|
Direct access to your environments
Fully access your Magento development and deployment through a UI console or CLI. 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.
You should become familiar with the following technologies:
Where do I get started?
If you have experience with Magento Commerce 2, 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 are the Product Owner, you should complete these onboarding tasks to give your technical staff and solution experts access.
We recommend the following starting points:
- Technologies and requirements
- Deployment process
- Set up a project and dev workspace
Magento 2 resources
If you would like to learn more about Magento 2, see the following resources:
- Documentation home page
User guides (how to use options in the Magento Admin)
- Front end development
- 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.
- Project Web Interface: The Web Interface is a console for accessing your project, user accounts, and your Integration enviornment. You can modify environment settings, environment variables, routes, and manage environments. Links (store URL, SSH, Git) are provided for the eight active environments through the active Git branches.
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.