Co-founder and CEO at a tech services company with 11-50 employees
User
2022-02-02T19:40:32Z
Feb 2, 2022
Cloud vs On-premise RPA: several components should be considered and each can be executed in either environment.
Orchestrator and scheduling server and the actual agent that executes the process.
If the agent is in the cloud, probably you would need a VPN connection to your central systems to execute the commands. All data would travel through the VPN which could slow the execution of the WF.
An On-Premise agent would be the preferred implementation if capable HW is available. For the server part, if data can not leave the office, On-Premise would be the only option.
Otherwise, the cloud would be preferred as the provider will have the implementation to be able to scale accordingly and have security measures in place for multi-tenancy.
Search for a product comparison in Robotic Process Automation (RPA)
Find out what your peers are saying about UiPath, Microsoft, Automation Anywhere and others in Robotic Process Automation (RPA). Updated: December 2024.
What is RPA? Robotic process automation (RPA) is a software technology that enables enterprises to build, deploy, and manage a virtual workforce made up of software robots (“bots”) that emulate the actions of humans in interactions with software and digital systems.
Cloud vs On-premise RPA: several components should be considered and each can be executed in either environment.
Orchestrator and scheduling server and the actual agent that executes the process.
If the agent is in the cloud, probably you would need a VPN connection to your central systems to execute the commands. All data would travel through the VPN which could slow the execution of the WF.
An On-Premise agent would be the preferred implementation if capable HW is available. For the server part, if data can not leave the office, On-Premise would be the only option.
Otherwise, the cloud would be preferred as the provider will have the implementation to be able to scale accordingly and have security measures in place for multi-tenancy.
Hi @Celestine @Nilesh Pawar, @Venkateswarlu Paturu, @Biswajit Mohanty, @Ram Chenna,
Will the below point help in attributing which option to be used?
1. Ease of Implementation
2. Ease of use
3. Speed
4. Technical Features
5. Ownership Cost
6. Scalability
7. Architecture
8. Exception handling
9. Vendor support
10. Governance
Please add your points and advice to help the community get more understanding.