Robotiq
Robotiq

Deployment models

HomePlatformDeployment models

Deployment Models



There are multiple ways of deploying Robotiq.ai platform depending on the requirements and needs. Each model has some pros and cons and licensing is also connected to the deployment as not all licensing models are available in each deployment model (for more information see LICENSING).

Robotiq.ai platform offers three different deployment models:


On-premise​ - all components (HQ, robot and chatbot) are deployed on customer environment (on-prem)
Hybrid​ - HQ and chatbot are hosted on robotiq.ai infrastructure (cloud)​ and robots are installed on customer environment (on-prem)
Cloud​ - all components (HQ, robot and chatbot) are deployed on robotiq.ai infrastructure (cloud)

ON-PREMISE DEPLOYMENT



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

PROS


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

CONS


Requires additional hardware – HQ and robots
Requires additional non Robotiq.ai software licenses – i.e. Windows licenses
Installation and deployment take more time
Access to new features is prolonged

HYBRID DEPLOYMENT



Customer or partner installs only robots on customer infrastructure, and they are responsible for maintaining OS, software and hardware of the robot component. HQ and Chatbot components are hosted on robotiq.ai infrastructure and are maintained by Robotiq.ai.

This model is preferred deployment model as it provides good balance between simplicity and the need for security. Customers can automate processes with their LOB apps since robots are installed on their premises. Important thing to note here is that robots do not transmit any customer data or screenshots to the HQ. Robots only transmit technical log and general job metadata (process status, robot name, time of the execution). Data transfer is executed over secure protocol and the robot login credentials are encrypted in the database.

PROS


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

CONS


Requires additional hardware – robots
Requires additional non Robotiq.ai software licenses – i.e. Windows licenses
Dependency on Internet connection speed when working with HQ

CLOUD DEPLOYMENT



Robotiq.ai hosts all the components of the platform and is responsible for maintaining them. This model is de-facto RPA as a service in which the customer is delivered with a full service. But in most cases, this is not a feasible scenario especially in case of enterprise customers.

PROS


No installation or maintenance worries
SLA guaranteed by Robotiq.ai
Fast rollout

CONS


Customer line-of-business applications need to work in cloud environment – they need to be accessible from the Internet