Choose deployment model

The Automation 360 platform is developed on a cloud-native architecture with a single codebase that supports both Cloud and On-Premises deployments. The experience of all the components is the same whether the platform is deployed on Cloud or On-Premises on your own infrastructure, which can be physical servers, your private Cloud, or a public Cloud.

Note: Migration is available in Automation 360 starting from Build 2079 for On-Premises and from Build 7554 for Cloud deployments.

Deployment models

Automation 360 deployment models provide solution and flexibility to meet customers' requirements on how they want to use Automation 360.

Automation 360 Pure Cloud
In this deployment model, the Control Room is fully hosted and managed by Automation Anywhere in our Cloud. This deployment model provides the customer with a full SaaS experience with instant access to up-to-date software updates. In this deployment model, the operational data (users, roles, schedules, bots, and so on) is stored on the Automation 360 Cloud Control Room. With this deployment type, the Bot Agent runs on the customer premises.
On-Premises
In this deployment model, the Control Room and the Bot Agent reside on the customer-owned and managed infrastructure. In this deployment model, the customers control the adoption of software and package updates. In this deployment model, customer data stays on the customer premises. The following are the customer options for this deployment model.
  • Customer's managed bare metal server: In this deployment type, the customers can set up or purchase a bare metal server, and the Control Room is fully hosted and managed by the customers on their server in the physical data centers.
  • Customer's subscription on Public Cloud: In this deployment model, the Control Room is fully hosted and managed on the customer subscription of the Public Cloud (for example, AWS, GCP, or Microsoft Azure) and the data is stored on the customer subscription of the Public Cloud.​
​
Important:
  • Irrespective of the deployment model you choose, we recommend that you set up your first Automation 360 instance as a development (Dev) environment.
  • We recommend that you have three separate environments for Bot Lifecycle Management: development (Dev), testing (Test or UAT), and production (Prod).
  • Setting up a Dev environment during the migration process provides two advantages:
    • A platform to test the migrated Enterprise 11 or Enterprise 10 bots to ensure that they run successfully and provides expected outcomes.
    • Access for your developers to the new Automation 360 environment to build new automation simultaneously when migrated bots are being tested.

Getting ready for Cloud

When you choose an Automation Anywhere Cloud deployment, there is no additional physical server infrastructure to set up for the Control Room. After you have completed your upgrade, you will benefit from automatic updates across your organization and scale easily in the Cloud. As you get started with Automation 360 on Automation Anywhere Cloud, ensure the system and compatibility requirements for running Automation 360:

Getting ready for On-Premises (customer's infrastructure)

Install and maintain Automation 360 on your own infrastructure. After you have completed your upgrade, you will benefit from regular updates for packages with new release builds made available to download and install. Ensure you meet the system and setup requirements for Automation 360 On-Premises: