UiPath has a visually appealing user interface and some minor features that are not available in OpenRPA, such as the ability to override defaults per project and create collections of selectors. Both OpenRPA and UiPath support a wide range of RPA technologies, including Windows, Java, Internet Explorer, SAP, mainframe, and Chrome/Firefox/Edge. However, OpenRPA has a few key differences that set it apart from UiPath.
One of these differences is that OpenRPA allows users to load and work with multiple projects at the same time, making navigation and execution faster. On the other hand, UiPath runs workflows in a separate process, which can help to mitigate memory leaks in third-party DLLs and allow for easier recovery if something goes wrong in the execution of a workflow.
Another difference is that UiPath supports selectors that span technologies, while OpenRPA does not. Additionally, UiPath has its own “JavaBridge” for Java automation, while OpenRPA uses Java’s built-in JavaBridge. UiPath also supports a wider range of mainframe protocols than OpenRPA.
When it comes to integration with other systems, OpenRPA offers more options through the use of NodeRed and OpenFlow, which currently support over 4000 it systems and protocols. On the other hand, UiPath relies on either UiPath or the community to create activities for API access to systems like Jira, ServiceNow, and Salesforce, currently less than 100 systems are supported.
Finally, OpenRPA is designed with security and scalability in mind, featuring access control lists, multiple layers of encryption, support for offline deployments, and mesh topologies. It also encourages users to take advantage of microservice architectures to achieve scalability.