UiPath Platform Reviews

We're using UiPath for healthcare use cases. It is primarily used for automating document-related tasks, such as moving documents around, classifying them, and extracting the information we need. 

UiPath has increased our accuracy to 99.99 percent and expanded our ability to process large volumes of data, making data processing more affordable and improving our profitability. It has helped reduce personnel time and enhanced productivity because we can run the bots 24 hours daily.

We can automatically scan documents and send the information through Twilio. Document scanning is tricky, but we can easily collect the data after finishing the process. The integration is smooth. 

The solution helps us share data between systems, which speeds things up. Previously, we were doing everything manually. Now, we can automate data tasks in Informatics with UiPath. 

UiPath enables us to pull patient information into a single dashboard with the help of a Power BI integration service. Power BI is our dashboard solution, and we integrate it via API. It's much easier to monitor the patients because we can see how many records were successfully processed and prepared. It's secure enough to comply with HIPAA because we can collect patient data and encrypt it. Automated scheduling helps the healthcare staff, particularly the doctors. 

I like the ability to extract emails and other data from scanned documents. The machine learning and AI features are helpful because we're processing tons of documents and warehousing the data. UiPath's Document Understanding makes that much easier. 

Document processing could be improved. It's challenging to build document automations. It would be helpful if UiPath provided some templates and prebuilt models. Citrix automation could be improved. It's static automation, and we cannot fully automate processes involving Citrix. Some elements aren't supported. 

I have used UiPath for around four years.

UiPath is generally stable, but the stability goes down when we do Citrix automation.

UiPath is scalable enough. We are using more than 20 licenses. 

I rate UiPath support 10 out of 10. I'm satisfied. When we raise a ticket, we get a response in a day or two. 

Positive

UiPath Studio is available in community and enterprise versions, but the UI doesn't work correctly in the community edition, so it's difficult to achieve 100 percent automation. I'm not responsible for the licensing, so I don't know how much it costs. 

I rate UiPath 10 out of 10. I recommend UiPath because it's better than other automation tools like Blue Prism. It's easy to use and has a large user community that you can rely on for support.

We use UiPath Studio, specifically the enterprise version, for developing projects per organizational requirements.

UiPath makes building automation processes easy and accurate. It allows us to create a wide variety of feasible automations. Even complex processes can be tackled using UiPath's features, such as object repositories and document understanding.

UiPath offers end-to-end automation, which is crucial for our work. This allows me to handle various tasks. I can efficiently open any web application required by the organization or our clients. I can download documents from web applications and fill in the necessary details within them. I can extract important metadata from documents or web portals. I can store the extracted data in a designated data queue. I would rate the process a ten out of ten.

By automating tasks through the use of robots, we can achieve significant time and manpower savings. This, in turn, leads to reduced costs for the company. Additionally, automation improves accuracy, as robots are less prone to errors compared to humans performing repetitive tasks daily.

I use the UiPath Academy courses in my free time to get some diploma-level certifications.

UiPath reduces the cost of digital transformation.

UiPath helps reduce human error.

UiPath helps to save staff 70 percent of their time through automation. 

The community version of UiPath has a limited feature set, which can make it challenging for users to fully explore its capabilities without purchasing the enterprise version. Offering a trial period for all features could provide a more comprehensive evaluation experience for potential users.

I have been using UiPath for four years.

While UiPath has disconnected on a few rare occasions, it has generally been stable.

UiPath is scalable 80 percent of the time.

The initial deployment is moderate. 

The implementation was completed in-house.

UiPath is expensive.

I would rate UiPath nine out of ten. There are many RPA tools and UiPath is at the top of the list.

UiPath requires maintenance for any changes that are made.

I recommend reviewing the documentation and completing the UiPath Academy courses before using the solution to automate processes.

We are using UiPath to automate many processes. In my first job, I worked on billing and ticketing. We were automating the process for ticketing and billing for audit. The robot was responsible for auditing the process of an application. It was responsible for calculating the difference between the amount deposited by the visitors and the amount calculated and predicted by the application. It would then decide if it was the correct currency or not.

Currently, I am working on many applications, but the classic ones are where we are reading data from Excel or databases and then clarifying the data or closing some billings. I am also working on the process of taking some reservations on some sites.

I also sometimes use it to automate something on my personal laptop.

UiPath enables us to implement end-to-end automation. It is not only about developing robots or putting the code. You must also monitor and implement the whole solution. It is not just a robot.

UiPath provides more flexibility because you can use other languages such as C#. This opportunity is not there with Power Automate or Blue Prism because you are working with graphical tools. For me, it was an opportunity to learn C# and how to code.

UiPath provides the opportunity to work with the conceptual aspects. There are flow charts to help you design the workflow.

UiPath has helped to automate many manual processes. We can see the difference with automation.

UiPath reduces human error. It is one of the main benefits. UiPath also optimizes the time. It is helpful. For one of the processes, the time taken was reduced from seven minutes to one minute.

UiPath saves human resources. For example, we had a process that was done by four to five people, and we automated that process. The robot could do one day's work in 10 to 15 minutes. We have automated almost 15 processes so far, so there have been a lot of savings on human resources. These resources can now be utilized for other tasks. The manual and repetitive tasks were annoying for them, and now, they can work on other things that are more interesting and require human decisions, not just copying and pasting.

It is the most suitable tool for big beginners in RPA. It is simple to manipulate. I found it comfortable because it has ML, AI, and OCR. It is great.

It is easy for me to build automation using UiPath. I would rate it an eight out of ten in terms of ease of use. It is easy, and I enjoy making robots. It is not just for the sake of working. I enjoy it when I finish making a robot. I feel I did something.

I did not work much on it, but I like the OCR part. I found OCR interesting because we can work with unstructured data from a paper or handwritten text. It is something new for automation.

The Community edition and UiPath Academy are two powerful features of UiPath. The Community edition of UiPath gives hands-on experience. People who want to learn about UiPath can download it for free and use it. It is a solution for everyone. Anyone can use it to learn about UiPath and practice it.

It should have better integration with Microsoft applications such as Excel, SharePoint, Outlook, etc. Power Automate is better for communicating with Microsoft Office applications. With UiPath, we have some difficulty communicating with the Microsoft Office applications. This is the only weakness that I have come across.

I have been working with UiPath for about two years. I also worked with it during my internship.

It is stable. I would rate it a seven out of ten in terms of stability. 

For scalability, I would rate it an eight out of ten because it gives you methods to be scalable. You can scale many processes.

I have not interacted with their support, but the UiPath Community is there. It is a very big community now. When we have some questions or want some clarification, we can find resources on their site or in their community. When I started working with it initially, it was not easy to find solutions related to UiPath. Compared to Automation Anywhere, it was a bit harder to find solutions.

I have also used UiPath Academy for certifications. It helps to learn from scratch. UiPath Academy makes it easy to learn for someone who has not worked with UiPath. There are different levels. You can find your level and begin from there.

We have our private setup. We have our own Orchestrator. We have a platform that communicates with the Orchestrator. We put the robots on Orchestrator and we monitor them using Orchestrator and some VMs. 

The deployment complexity depends on each project. Some projects are easy. You just need to put the robots. In terms of maintenance, robots do require maintenance. You need to monitor them to ensure that they are meeting the business requirements. If the code is good, one person can maintain the robots.

We are working in a team, and we have our own resources. We have experienced team members who know how to do the deployment.

We have teams working in multiple locations such as Tunisia, Morocco, Romania, and France.

There is a significant ROI with process automation.

It is reasonable considering the benefits of automating the processes.

I would recommend starting with some simple or classic processes, such as reading data from an Excel sheet and a database. You will find it easy. My advice is to not start with something difficult.

I would rate UiPath an eight out of ten.

I developed several use cases using UiPath. One involved website scraping, where I extracted data like temperature, humidity, and pressure for various cities from a specific website and displayed it in an Excel sheet. This was a small project, but my main focus was a prototype for a client: digital marketing automation. Using UiPath, I created an automation to automatically post articles on different social media platforms.

UiPath has certainly improved our operational efficiency. My prototype adheres to its principles.  UiPath has a sheer number of functionalities and features in UiPath. While these are beneficial, considering operational efficiency, UiPath excels thanks to its modularity. It's comprised of distinct components like Orchestrate, robots, and studios. This breakdown allows each component to function independently, increasing work flexibility and ease of use.

I would rate the ease of building automation using UiPath an eight out of ten with ten being the easiest.

I would rate the UiPath User Community ten out of ten. It is the best community I have used.

I'm taking advantage of the UiPath Academy courses and find them helpful.

UiPath helps to speed up our digital transformation and reduce costs.

Automation through UiPath helps reduce 80 to 90 percent of human errors.

The UiPath User Community is the best feature. We can find a solution to all of our issues there.

UiPath's interface element identification is arguably more reliable than Automation Anywhere's. This is because it utilizes an element descriptor method, which essentially locates "anchors" within the target element, not just relying on its absolute position. In simpler terms, it seeks a stable reference point within the element itself, even if its overall position on the screen shifts. As a result, changes to the website's UI are less likely to break our automation, as the code doesn't depend solely on the element's position. Additionally, UiPath offers a wider range of app integrations and features compared to Automation Anywhere or Blue Prism, making it more versatile for different automation needs.

Logging is also valuable. We can see any system, business, or technical errors.

One area that could be improved is how we access the UiPath Academy courses. While it's fantastic that each course provides an assignment, it would be more convenient if we could view the solutions directly within the platform rather than downloading them each time and opening them in our individual UiPath Studio applications. Ideally, there would be an interface integrated into the course platform itself where we could access and review the solutions directly within the browser. This would save time and streamline the learning process.

In Automation Anywhere, each line of code is displayed in a list view, offering clearer visibility. In contrast, UiPath condenses everything into a boxed view or flowchart, which can become cumbersome when dealing with numerous intricate conditions. Pinpointing specific segments for modification within such a condensed format proves challenging. Therefore, UiPath's UI design could benefit from an overhaul to enhance clarity and ease of navigation, especially for managing complex workflows.

I have been using UiPath for one year.

I rate the stability of UiPath an eight out of ten.

I rate the scalability of UiPath a nine out of ten.

I find Automation Anywhere to be more user-friendly for newcomers.

While I have more experience with Automation Anywhere, and it's where I've worked more extensively, UiPath is currently the market leader in the field. This prompts me to explore what's behind its success and delve deeper into learning UiPath. There must be compelling reasons why it holds the top position.

UiPath is more expensive than Automation Anywhere.

I would rate UiPath nine out of ten.

I recommend UiPath as the leading RPA technology, considering the current market trends.

Our company is considering UiPath and Automation Anywhere for automating a mainframe application. I have explored UiPath, evaluated its capabilities, and completed a use case.

Building automation with UiPath is exceptionally straightforward. However, clients need to exercise caution by ensuring that the automation doesn't require intricate human logic. If they seek simple automation without incorporating human elements, UiPath facilitates an easy and automatic implementation, excluding the need for advanced AI features.

We leverage UiPath to automate processes aligned with the good cause our company supports. This includes tasks related to warehouse management and maintaining a clean architecture. For instance, activities like clearing out mailboxes, collecting bills, and optimizing server data storage contribute to reducing running costs for the machines involved.

We employ UiPath for comprehensive end-to-end automation in the client's operations. They have successfully automated around two hundred use cases, forming a critical backbone for their extensive operations. The dependency on automation results is notably high, especially in areas like warehouse management, where the efficiency gains are substantial. Enabling automation to handle these tasks daily liberates the workforce from repetitive manual efforts, allowing them to redirect their focus to other crucial aspects of their operations. This strategic use of automation enhances productivity and expedites the completion of automated tasks.

We have a robust user community within UiPath, and I have actively participated in it. Although I wasn't as engaged this year due to a significant impact on the client caused by a cyber attack on their network, the community support has been exceptional. Despite my increased workload in addressing the aftermath of the incident, the UiPath user community has proven to be like a supportive family. Whenever I've raised queries or sought assistance, the responses have been prompt and helpful.

The advantages of using UiPath are evident in the efficiency gains achieved by minimizing human efforts. For instance, when uploading a report to SAP or executing a job in Insight SAP, these processes can often take several hours. Without automation, users may be tied up in monitoring these tasks, risking potential human errors due to prolonged attention. However, implementing UiPath effectively liberates users from this prolonged monitoring. Automation ensures that tasks run seamlessly according to protocol, allowing users to easily obtain results and simultaneously engage in other important activities. The goal is not to overcomplicate processes but rather to streamline and optimize them for enhanced productivity throughout the day.

UiPath has played a crucial role in reducing our on-premises footprint and enhancing the solution's capacity. The company we're currently assisting primarily focuses on order management, dealing with a significant influx of orders. By leveraging UiPath, we've effectively streamlined the order management process, optimizing the solution's capacity to handle a large volume of orders.

Our team actively engages with the academy courses provided by UiPath. As UiPath continuously expands and introduces new features, the courses serve as an invaluable resource. We find that the admin courses are particularly beneficial for us. When we come across new elements or features, we go through the courses to understand them thoroughly. This allows us to assess their compatibility with our solutions and implement them at our own pace. Additionally, if there are issues with older automation, the admin courses assist us in applying updated solutions to enhance performance. It not only helps with incorporating new automation but also in maintaining and improving existing ones, making it an excellent resource for managed support.

It accelerates digital transformation and significantly lowers IT costs. This is achieved without the need for expensive or complex application upgrades or extensive IT support. Currently, we are reducing the number of active machines and servers in operation. Although there might be an initial investment in bringing up users, the efficiency gains result in substantial savings. As we streamline processes through automation, we not only reduce the number of calls and machines but also realize long-term ROI by saving on infrastructure costs. In essence, the more automation implemented, the greater the cost savings and efficiency improvements over time.

UiPath has been instrumental in minimizing human errors, particularly in the process of uploading orders into the system. With automation, validation, and auditing integrated into our workflows, potential errors are identified at the initial stage. This allows us to promptly notify users of any issues, providing details based on the preset parameters. Through these efforts, we have observed a substantial reduction, estimated at around twenty to thirty percent, in errors that could potentially lead to future problems.

It has effectively liberated employee time by automating around two hundred processes within our sizable company. Based on my estimates, we have saved approximately three to four months' worth of workdays. This translates into significant time savings for our team and contributes to improved efficiency and productivity for our client.

The most valuable aspect is its simplicity in coding. All that's required is a fundamental grasp of coding principles and a bit of logical thinking. Once you've acquired these skills, you can effortlessly write a substantial amount of code and easily upgrade it as needed.

The integration is seamless and streamlines our workload.

It would be beneficial to enhance application insights, and I've shared this suggestion with the UiPath committee as well. Occasionally, clients expect a process to run at a specific time, but due to various factors, it might get delayed by half an hour or more. Currently, we only become aware of such delays by actively checking within the application. It would be beneficial if the system could proactively generate alerts, notifying the client about any delays in the process execution. This would provide transparency and enable clients, as well as our team, to be informed and take necessary actions, such as considering a migration if needed.

I have been working with it for approximately six years.

It exhibits high stability. With a robust security department in place, we conduct thorough code reviews, contributing to a secure and stable process. On a scale from one to ten, I would rate it at nine.

Our clients are a massive enterprise with approximately two hundred automations in place. Scalability is dependent on the process level. If you have independent processes that can be executed, scaling up is straightforward.

Technical support is readily accessible to us always. I would rate it ten out of ten.

Positive

When comparing Automation Anywhere to UiPath, it's important to mention that Automation Anywhere has undergone numerous updates in recent years. In my assessment around 2020, it lacked features such as the concept of attended and unattended bots, as well as multi-bot automation. However, I believe they have since introduced these features, though I haven't personally explored them. In terms of features, Automation Anywhere lagged behind UiPath.

The deployment process took approximately three months for us due to various IT issues. This involved obtaining clearance from the IT, firewall, and security teams. In the current client setting, which has about five to six internal auditors, securing approvals was a meticulous process. Once all the necessary clearances were obtained, the actual implementation only took around fifteen days. Additionally, we received direct support from the UiPath team during the integration process. From our side, only three individuals were involved in the implementation process.

It has been deployed across multiple departments and various regions, including APAC, Europe, and Australia.

Maintenance is not a major concern. System-level maintenance is required, but if your automation is rigid and doesn't necessitate frequent changes, it's easy for us to manage and monitor. For maintenance, our current approach involves regular database cleanups and similar tasks since we are on-premises. However, once we migrate to the cloud, I believe such procedures won't be necessary anymore.

I believe that the price is on the higher side. From an ROI perspective, I would give it a rating of five out of ten. However, if we exclude the ROI considerations from the overall assessment, I would rate it at seven.

From my perspective, it's a strongly recommended tool. However, from the client's viewpoint, especially since they are venturing into RPA implementation for the first time, they prefer a proof of concept before proceeding. Overall, I would rate it ten out of ten.

I am working for a client. I am using on-premises UiPath Orchestrator. I have installed UiPath Studio and deployed some processes for automation. 

I have used it for SAP automation, Excel automation, and web automation. I have not yet used the AI functionality. I might use it in the future.

Manual tasks are reduced, and in less time, I can complete a task. 

UiPath has sped up our digital transformation by 20%.

UiPath has reduced human error. With automation, correct values get entered, and there is a reduction in human error. There is a 10% reduction.

UiPath has saved us money because there is a reduction in manpower. It has saved about 20% on costs.

In terms of time savings, for Excel automation, the backend activities are much faster, whereas web automation takes time because it requires loading the screen and capturing the elements. For Excel automation, the backend activities take 30% to 40% less time.

UiPath Orchestrator is very user-friendly and easy to understand.

The interface is very good. In the latest one, they have added many more activities, which has made it even easier to do automation.

While doing web automation, I am facing a selector issue. In the web portal, we need to capture a screen element. For capturing the screen element, when I run the job the next time, it fails because the limit is not recognized. It is very difficult to make the selector stable. It is not easy.

I have been using UiPath for more than two years.

At times, when I restart the system, the deployed robots take time to connect to the UiPath Orchestrator. Overall, I would rate UiPath a nine out of ten in terms of stability.

It is scalable. We can use it in different companies or industries, such as hospitality or finance. I would rate UiPath a nine out of ten in terms of scalability.

It is deployed at one location, and we have four to five users of UiPath.

I am satisfied with their support. Whenever I raise a ticket, they provide the required support. 

UiPath has a user community, but I did not use it much. I used the UiPath documentation.

I have also used UiPath Academy and completed three courses. I have done the foundation course, the advanced course, and the continuous learning course. I am satisfied with the UiPath Academy courses.

Positive

I have also used Automation Anywhere. Compared to Automation Anywhere, UiPath is more user-friendly. In Automation Anywhere, we have to do lots of things, whereas in UiPath, we have to do fewer things, which makes it easier to do automation. Also, capturing the screen is much harder in Automation Anywhere. It is easier in UiPath.

The deployment of UiPath Orchestrator only takes one day. 

In terms of maintenance, it only requires yearly license renewal and making sure it is up to date.

We have two people who are involved in the UiPath deployment. 

Overall, I would rate UiPath a nine out of ten.

We are an insurance company. We mainly deal with all types of insurance from casualty and specialty to even aviation and medical stop loss.

I have had use cases where we have been taking information from emails and phone calls to put them into a mainframe. We have done claims intake for insurance, and then we have notifications. For the policy system, we have done a lot of back-office accounting work.

By implementing UiPath, we were trying to seek a way to free hours up at critical times. It is not just about hours saved. It is also the quality of the hours that we save and freeing people up for more value-added work.

UiPath has definitely helped with scalability. The number one reason to use something like UiPath is to increase scalability so that we are less susceptible to changes in the market. We can grow our business without growing our staff hours.

UiPath has changed the way we perceive our processes because even outside of processes that we automate, we look at our processes in a new way in terms of process improvement. Not everything needs to be automated. Some things just need to have the process changed. It has helped us to be very critical of our processes and be more forward-thinking and not just sticking in the same ruts.

UiPath has helped with the accuracy. There is less fat fingering of things. When the robot is entering things into a system, it will put in exactly what was input into it. There is also a chance for transposing things, so there is a lot more accuracy in that respect.

UiPath has freed up time and resources for other tasks. That has been our main focus in terms of the ROI we look for. With the accounting back office practices, our close cycles are shorter, but people are not working more. With automation, we now have things that are on more of a 24-hour cycle. We are able to do a higher volume in less time.

We have saved thousands of hours not just in the back office accounting side for close cycles but also in insurance. We have busy seasons. We sometimes had to hire temporary workers. With the automation of our claims intake and other processes in that area, we are no longer hiring those temporary workers. We do not need them anymore.

The ability to connect various systems that do not have any kind of API between and the areas where we need to mimic what a human does to a system in terms of input and output is valuable. We primarily use UI automation where we simulate what a human does within an application. By using the right selectors, we try to find where on the screen we need to click. We take in information from input files. We use all the logic flowcharts and logic trees to determine where the information needs to go in a system.

Some of the areas around the administration aspect of UiPath, which is what I have been mostly working with over the past few years, can be better. From an organizational standpoint, some of the guidance there could use some work in terms of helping COEs know how to grow and how to take control of their organizations as they spread.

I have been using UiPath for about five years. 

There are still some stability issues. There are sometimes issues related to bots acting up. It can be hard to tell whether that is something related to how we developed it or whether the bots are having an issue. We are not sure why, but there are some stability issues.

Its scalability is fine. It has definitely gotten better over the past few years with all the improvements there. I know there have also been new offerings for serverless robots, which we have looked into, but they do not fit our needs. The UiPath Orchestrator makes it easy to maintain its governability as we scale, which is one of the main differentiators of this solution.

They can sometimes be hard to get a hold of. There have been a few times we have had to go to the UiPath Pro support. While we have eventually gotten to the solution, it has sometimes taken us a while to get in contact with someone who has the right knowledge to help us with our problem. I would rate their support an eight out of ten.

Positive

This is the first one we have been using. We have a group in the company that started using Power Automate. They ran into a problem and turned that back over to us. We are the UiPath team. They tried to automate something with Power Automate, and we ended up taking over that project.

Orchestration is the main differentiator between Power Automate and UiPath. UiPath has orchestration whereas Power Automate does not. Without that orchestration, you lose a lot of the value for these robots, especially at the organizational control level.

I was brought on specifically to do the deployment at my current company. It was fairly easy. I did an on-prem deployment about five years ago, and now, I am doing the cloud deployment. We are using the automation cloud. Having the automation cloud made it much easier to do the deployment this time than trying to set up the on-prem Orchestrator the first time.

In terms of the implementation strategy, we essentially looked at how many processes we had as candidates and what we thought the bot load would be. We stood up that many VMs. We deployed unattended robots to those. In terms of Orchestrator, we just did some basic tenant separation, and as we have grown, we have seen where to increase the bots.

We used one called Accelerate to start with. Our experience was fine. Our goal was always to transition to our own, so after the proof of concept was done, we hired our own developers. We hired our own team and went from there.

We have definitely seen ROI coming from it. For any project we take on, we look at both quantitative and qualitative aspects. Quantitative is usually just the hours saved. If a process is automated, how many hours are saved as compared to the last one? Qualitative would be things like whether we have increased accuracy, whether we have increased any time to the next process in the chain, or whether we have gained redundancy and reduced the fragility of our processes.

If it can be lower, we will always take lower.

Blue Prism was what we looked at pretty heavily. We looked at Pega. We also looked at Power Automate, and some groups within the company decided to try and use that. 

When comparing UiPath and Blue Prism, there is clearly a difference in power and capabilities between the two. We also had a solution partner who could work with us better with UiPath at the time.

We are currently setting up the AI Center. We have not used UiPath Process Mining and Task Mining. We tried to use the task binder where you record something and create a workflow from it, but it was not very useful for us. The output was not very useful for us. The documentation from it was also not useful for us.

If you are evaluating UiPath and other products, I would advise looking at what kind of model you are looking for. Are you looking for a more federated model or a centralized model?  You should look at what kind of governance you need in place for the solution you are looking for. One type of solution is that you put it in someone's hands and leave it and forget it. If you want to empower people and maintain central control, UiPath would be for you.

In terms of deployment, I would go for the automation cloud every time. There is the ease of use of not having to worry about standing up your own servers to monitor that. The US cloud especially has been very stable.

Overall, I would rate UiPath a nine out of ten.

We use UiPath to automate the repetitive tasks typically performed by knowledge workers, with a primary focus on areas such as finance, HR, and supply chain.

Starting with UI automation is valuable as it mirrors users' existing workflows, building their confidence before expanding into more powerful automation methods.

There are instances when the introduction of new features or concepts can be a bit overwhelming for users.

I have been using UiPath for five years now.

I would rate its stability capabilities nine out of ten as there is always room for improvement.

It offers excellent scalability. I would rate it ten out of ten.

When we were initially planning our move to the cloud, we reached out to the support team for guidance. Our account executive connected us with the UiPath professional service team, who were incredibly helpful in addressing all our inquiries and concerns. Even our cybersecurity team had many security questions, and they provided comprehensive answers to ensure our transition was well-informed and secure. I would rate it ten out of ten.

Positive

The initial setup was complex due to the various components involved, such as Orchestration, Kibana, document storage, and databases. Each of these had its own installation and maintenance requirements, which was a constant task.

We needed to streamline the installation to focus more on building automation rather than dealing with upgrades and maintenance, so we migrated the deployment to the cloud. This transition reduced the complexity associated with interfaces and orchestration.

The pricing is quite reasonable.

Our company evaluated multiple leading tools and ultimately chose UiPath. One important factor was its open approach, offering a community edition for users to learn and explore the platform without an initial purchase. This approach fosters community development and creates a vast knowledge pool, making UiPath stand out. It encourages individuals to learn and explore the tool before transitioning to the enterprise version, while also providing a valuable talent pool for support and assistance.

My advice is to encourage exploring the platform, although it might be overwhelming due to its rapidly expanding features. While there may be initial confusion regarding UiPath's focus on AI, recent events have clarified its core message. It empowers users to deliver the models they create, integrating smoothly with enterprise systems. It enhances automation capabilities while incorporating AI elements, ultimately putting you in control of the AI within the platform. 

I would rate UiPath ten out of ten.