Deployment models

HomePlatformDeployment models

Deployment Models platform offers three different deployment models:

All components (HQ, robot, and chatbot) are deployed on the customer environment (on-prem)
HQ and chatbot are hosted on infrastructure (cloud)​ and robots are installed on customer environment (on-prem)
All components (HQ, robot, and chatbot) are deployed on infrastructure (cloud).

And three different licensing models. However, not all licensing models are available for every deployment model.


Customer or partner installs all components on customer infrastructure, and they are responsible for maintaining OS, software, and hardware (PC). This model is often chosen by customers where there are regulatory or security requirements that data needs to reside within the company or country.


No dependency on Internet connection speed when working with HQ
All data is contained within the customer's IT environment

However, this model requires additional hardware (PC) and license (i.e. for Windows). Furthermore, the installation and deployment require more time, as well as access to new features.


Customers install only our robots on its infrastructure, and they are responsible for maintaining the OS, software, and hardware (PC) of the robot component. HQ and Chatbot components are hosted on infrastructure and are maintained by

This is the most preferred deployment model for customers, as it provides a good balance between simplicity and the level of security. Customers can automate processes with their LOB apps since robots are installed on their premises. The important thing to note is that robots do not share any customer data or screenshots with the HQ. They only send technical logs and general job metadata (process status, robot name, and time of the execution). Data transfer is performed over secure protocol and the robot login credentials are encrypted in the database.


Frequent releases of features
Hardware and software not needed for HQ server
No maintenance on the HQ side
Faster rollout
Access to HQ from anywhere

However, this model requires additional hardware (PC), software licenses (i.e. for Windows), and a fast Internet connection when working with HQ.

CLOUD DEPLOYMENT hosts all the components of the platform and is responsible for maintaining them. This model is de-facto RPA as a full service. In most cases, this is not a suitable model, especially in the case of enterprise customers.


No installation or maintenance worries
SLA guaranteed by
Fast rollout

However, customer's line-of-business applications need to work in a cloud environment, as they need to be accessible from the Internet.