UiPath vs Blue Prism

I am trying to compare any technical differences between UiPath and Blue Prism.
What are some technical aspects, in which UiPath can perform but Blue Prism cannot?
Thank You.


How about this one.

1 Like

This definitely helps! But I was looking for specific examples such as “In BluePrism, there was a problem doing something. Nevertheless, I did not experience such problem using UiPath.” I found it difficult to catch such examples.

Generally, both are perfectly capable of achieving most requirements, however, from my (rather limited) experience I’ve noticed the following issues in Blue Prism:

  • Iterating through collections in excess of 2000 records caused System.OutOfMemoryExceptions and demanded 3+ hours to process.
    This resulted in us having to utilise a code block, achieving the same thing, but in a fraction of the time and with a minimal resource footprint.
  • RDP usage causes serious issues when using BP, though this is somewhat the case in UIPath I believe.
  • Selectors are more difficult to use and feel more limited.
    In addition, there have been numerous instances wherein the “spy” feature crashes.

Although I prefer UIPath, Blue Prism is far superior from a debugging perspective, allowing you to view all assigned data during runtime and step out of, into and over components flawlessly.
While these features exist in UIPath, I find they frequently fail/crash in medium/large projects.

With that said, this is entirely my opinion and my experience with Blue Prism is limited to one project.


Thanks a lot for the detailed examples. Are there any other examples or opinions?

Hi @joonhah

In blueprism we have application modeller to interact with application.
But in uipath we dont have.

Some of the differences between UiPath and Blue Prism


Visual Design - Faster Implementation
Build Modular Automation and Reuse at the workflow level. Extend UiPath functionality via custom activities or various integration can be used for various integration.
Can be used for various integration services with different workflow modules hence scoring high on re usability.

Blue Prism

Programming skills required. Ability to create business objects and manage them in the control center.
Once a library of Blue Prism business objects exits, those objects can be reused across multiple processes.