Pega Robotic Process Automation Reviews

For banking customers, Pega Robotic Process Automation can fill in the process automation which cannot usually be done by process reengineering; we use it for activities such as process mining to identify business opportunities. That's a typical use case, but it encompasses a broad set of use cases; consolidating reports could be one such example.

Pulling data from various systems and providing a customer 360 view would be a good example or use case of intelligent automation.

Integration with other systems is important.

Centralized management is a notable feature. Some products have centralized management while others don't, and it depends on what the customer is looking for. Some customers prefer to have centralized management, while others already have it. Overall, the concept of centralized management is very useful in terms of integration, but not many products have that capability.

The number of human steps that have been eliminated is significant, and we try to maximize straight-through processing.

Pega Robotic Process Automation is a temporary solution to a bigger issue, and the cost of implementation especially with Pega really stops customers from proceeding.

The total cost of ownership could be improved.

From a technical perspective, the product performs adequately.

The installation can be quite complex as it's not standalone, and customers need to get the whole Pega platform up and running. The total cost of ownership is not very attractive.

RPA as a concept is outdated now, with agentic AI becoming more prominent. We don't see much interest from customers in going down the RPA route; Pega Robotic Process Automation is losing its prominence in the market.

I have been selling the product for about 30 years.

There are glitches whenever there are changes in the underlying main screens and logic, RPA tends to have issues.

On a scale from one to ten, stability would rate at three.

There are limitations in scaling as RPA is not a scalable solution. It's more of a stop-gap arrangement and isn't viable over the long term.

Scalability would also rate at three out of ten.

Technical support from Pega rates about seven out of ten.

The service still has room for improvement.

The speed and quality of response could be improved, though generally, they are performing adequately and we don't have major concerns.

Positive

We are not customers but implementers, selling a whole suite of SAP products. It's a large business for us with a separate business unit that handles selling SAP products. I'm not a customer of SAP but a reseller.

I sell all SAP products, including SAP Marketing Cloud and Commerce Cloud.

I am George from a system integrator and reseller background.

We are a system integrator, reseller, and implementer of SAP, Camunda, and others.

RPA hasn't been around for more than five to six years. We've been working with Pega for about the last 15 years, but Pega Robotic Process Automation is a new product from Pega which is not more than five to seven years old.

I am also selling and integrating the RPA solution from Pega. The closest comparable solutions are Camunda, Pega, Adobe, Snowflake, and Cloudera, which I am directly involved with. I also deal with UiPath, Automation Anywhere, and others in Robotic Process Automation.

All integrations are of concern as it's rarely seamless, which is why we as system integrators come in to solve the problem.

My overall rating for Pega Robotic Process Automation is 8 out of 10.

Regarding the best features of Pega Robotic Process Automation, it is easy to integrate with because it's built-in. We recommend using bots only when there's no immediate roadmap for service-based interactions to make them modularized or API-based. We implement Pega Robotic Process Automation bots for tactical approaches to gain immediate benefits, but over time, we transition to API-based integration instead of using Pega Robotic Process Automation.

We have not widely used Pega Robotic Process Automation in customer service operations for automating data entry processes. Most of the data entry in customer service involves identifying the customer and retrieving data from various systems using the Customer 360 format. When Customer 360 is accessed by the agent dashboard, all necessary data is already available. We do not employ RPA for this purpose; instead, we focus on MDM implementation or customer data management for interactions. I have not encountered many use cases for applying RPA in customer service data retrieval, nor do we recommend it.

We have some customers while we are helping them to implement RPA mainly on repetitive, rule-based tasks like data entry, system navigation, or report generation, auto login/log-off, start my day, close my day, automate data entry etc

With Pega Robotic Process Automation, after the acquisition of OpenSpan, they are using embedded OpenSpan as one of their RPA products, but Pega Robotic Process Automation using OpenSpan has a very low adoption because it does not provide the flexibility that UiPath or Automation Anywhere offers. Pega RPA is most powerful when integrated with Pega BPM; as a standalone RPA tool, it lacks some advanced features found in competitors like UiPath or Automation Anywhere. While low-code, Pega Robot Studio can be complex for beginners, especially those without .NET or Windows automation experience. Primarily designed for Windows desktop applications; limited support for cross-platform or web-based automation compared to other RPA tools. Managing large bot fleets and ensuring version control, exception handling, and orchestration can become complex without mature DevOps practices.

Regarding the best features of Pega Robotic Process Automation, Seamlessly integrates with Pega’s BPM platform, enabling end-to-end automation that combines bots with human workflows, Supports both attended bots (assist agents in real time) and unattended bots (run background tasks without human input), Easily automates tasks across mainframes, desktop apps, and web systems without requiring APIs, supports on-premise, hybrid, and cloud-native deployments, including integration with Pega Cloud.

1. Enhanced Cross-Platform Support

Currently optimized for Windows-based applications. Needs better support for web, cloud-native, and non-Windows environments (e.g., Linux, macOS).

2. Simplified Development Experience

Pega Robot Studio has a steep learning curve, especially for non-developers. Could benefit from a more intuitive, drag-and-drop interface and prebuilt automation templates.

3. Stronger AI/ML Integration

Bots rely heavily on rule-based logic. Native integration with AI/ML models (e.g., for document understanding, sentiment analysis) could make bots smarter and more adaptive.

4. Improved Debugging & Testing Tools

Debugging complex automations can be time-consuming. Needs better simulation, logging, and error tracing tools for faster troubleshooting.

5. More Scalable Bot Orchestration

While Pega Robot Manager is powerful, managing large bot fleets can become complex. Could improve auto-scaling, load balancing, and dynamic resource allocation.

6. Broader Integration Ecosystem

Limited out-of-the-box connectors compared to competitors like UiPath. Expanding the integration library (e.g., for SaaS apps, APIs, databases) would reduce custom development.

7. Licensing Flexibility

Licensing can be cost-prohibitive for smaller teams or departments. More modular or usage-based pricing could improve adoption.

I am using it for last 8 years

Concerning stability and scalability, Pega Robotic Process Automation is not that scalable.

Pega Robotic Process Automation is not very scalable.

Pega RPA is Windows-centric, and support for cross-platform automation is limited, which can be a challenge for diverse IT environments.

Neutral

Initial setup of Pega RPA can be complex and time-consuming, requiring skilled resources and sometimes additional support. Lack of a dedicated sandbox environment for training and testing, which can slow down onboarding.

We implement by our own RPA team

We have seen 28–42% reduction in labor costs by automating repetitive, rule-based tasks. Automation helped eliminate manual errors, saving up to $1.2 million annually in error-related expenses. Process cycle times were reduced by 50–65%, significantly improving customer response and service delivery. Automated workflows maintained 75–79% efficiency even at 20x transaction volumes, outperforming manual processes.

This review has a rating of 5 out of 10.

Mainly, we concentrate on RPA bots. However, we have a few demands where we needed RDA, their assisted bots. We need some assistance with the bot where some inputs are required from the business. 70% of the time, we concentrate on RPA bots. For the other 30%, there is also a requirement for RDA bots. 

Mainly, we interact with Windows web and sometimes with mainframes. Currently, we are targeting APIs as well. We are working on a few of the API-related stuff and Excel-related work, Outlook, sending email, and tracking email. 

In terms of third-party applications, we have multiple websites, which are web-based. Based on the client's requirement, we use it to interact with the applications.

As an RPA guy, every tool has its own advantage. That said, Pega has the best feature in terms of creating UIs. We can create the best UIs. Other tools, don't have a better UI for RDA. 

Some go for RDA bots in the banking sector, and they prefer Pega Robotics. 

We have centralized the monitoring. In Pega Robot Manager, we currently have multiple dashboards where we can track, schedule, and handle everything. That is the game changer in the last one-and-a-half years. It amended what the business expected. 

The initial setup is pretty easy and quite fast.

It's stable.

You can scale the solution if you need to. 

Excel connectors need to be improved as there are a few connectors in Excel areas. 

The recording is not at best in Pega Robotics. They could look into it.

The interactions with some applications, like Windows and web applications, are a little slow. They need to improve their speed. It should be normal, to open it with other tools. However, right now, it's a little hard. 

Users should feel they can develop easily. It will sometimes hang while interacting with third-party applications. 

Instead of adapters, if we had direct interaction of the applications with API and had scripts, that would be better. 

We have only CSharp supported right now. We'd like to have Python supported. If it was, it would be easier for us and make the solution more flexible. 

Currently, we are adding three different configuration files, however, if I had the option, I'd prefer to make a single configuration file and then differentiate it in all three environments. 

It can be difficult to create logic in automation. It's hard than if we used other RPA tools.

If they could add more toolbox options, that would be ideal. 

They need to do what they can to help us reduce complexity in the automation and combine things under, for example, a single control.

I've been using the solution for five and a half years. 

Recently, when I compared all tools, looking at the preloaded applications and Windows-related applications, if you process end-to-end, and if you are releasing it to production without any bugs, it is running with 95% perfection with maybe some hiccups via network issues. Basically, it is stable.

Therefore, Windows is quite stable. However, Citrix gets 80%. It's still good, however, when choosing the tool, it's important to consider if Pega is a suitable tool to give the best results. 

100% it is scalable, however, if a person is not aware of everything the solution can do, they may see it is only 70% scalable, or a little less scalable in general. The more you understand about the tool, the more scalable it becomes. It becomes easier to scale too. It's just that Pega may be perceived as a bit more difficult, than Blue Prism, UiPath, or Automation Anywhere. It's not, though. You just need time to adapt. 

I'm working for a sizable company that has hundreds of clients. In my client area, almost 150 to 200 bots are running. The other areas where my colleagues are working also have bots running. 

We are new to the tool and RPA, in general, was so new at the time for every organization around 2015 or 2016. At the initial stage, we used to contact support frequently due to functionalities issues. We need to raise the ticket if we want to talk with them. Then they will connect with us and help with resolving the issues or the bugs, and patching also. 

They are helpful. If we communicate clearly what we need the process moves fast.

Positive

I use Pega Robotics and Blue Prism in my day-to-day life.

In the market, in India, other solutions are used as well. Some may use Blue Prism or UiPath. For example, if you have a 100% RPA area, maybe UiPath concentrates on 40%, Blue Prism 30%, Automation Anywhere is another 30%, and Pega is around 3%. 

It has a default platform from where Pega provides a PRPC. Inside that, we need to deploy Pega Robot Manager. From there, we can deploy to Pega Robot Manager. From there, we can assign it to multiple users for daily use.

It was easier to deploy before. In some newer versions of Windows, we used to face some of the update tree issues. Currently, we need to download the update tree separately, and we need to install it on our machines. Then, we need to install Pega. Normally, it is easier, however, with these newer versions in Windows - 10 and 11 - we are facing some issues. 

There are Office versions that are not working perfectly. We need to uninstall and reinstall it, and for some Windows 11 versions, the toolbox icons are not visible. We have tried multiple times, uninstalling and installing. 

Deployment times vary. Normally, it will take hardly less than half an hour. However, if the solution is ready and we have groups assigned, we can directly deploy it to our servers. From servers, we can directly deploy to the users as well from Robot Manager. In the user's machines are the VDAs that we are using. We need to configure all the settings, the run-time, the config files, and everything. That takes ten minutes to one hour at a maximum. Once the setup is done in every machine, we can easily deploy that that will be hardly five minutes. 

The costs vary. In a previous organization, we used to take care of everything. It's a yearly fee they used to take. Recently, what I'm seeing is they have to categorize licenses. Some of the bots, they will run for some time, so they can get licensing costs and can pay quarterly. Typically, it is yearly. 

I'm not sure of the exact costs. I haven't gone that deep into licensing. 

The company assessed three more tools and chose Blue Prism and Pega Robotics. They use Pega Robotics for doing RDA, and Blue Prism for scripting-related items as they are strong in their area. Out of the five tools they have evaluated, they have taken Blue Prism and Pega Robotics. 

We're a customer and end-user. 

If a person wants to use this product, they need to know what is happening and how it runs. If the person is new and needs to run the solution, they need to follow the use case that the developers are giving to understand how the bot will run. With so many people, what they do is when the bot is running, they disturb some of the applications, and the bot will close or give exceptions.

If a person intends to use coding, they really do need a good grasp of what it is they want to build. Only them should they move into actual development. It will make it easier in the end if there's a good understanding at the outset. 

In any case, after two or three months of using the solution, chances are you'll have enough knowledge to be able to help train others. 

I'd rate the solution eight out of ten. If it was faster and had less complexity I would rate it higher. 

It was for integrating the mainframe system with the data process system.

Our clients have utilized Pega RPA to streamline repetitive tasks. Earlier, business users in the organization used to work with two systems, manually copying and pasting information between them. 

One was a very old mainframe system with a text-based interface, and the other was a newer developer application. 

We developed this integration so that the user interface automatically gathers information from the mainframe system using RPA tool and fills out the information in the system they're using.

Pega been very effective in improving process efficiency for back-office operations.  It's a very smart tool for integrating legacy systems.

It offers great ease of integration with existing systems and databases.

Legacy system integration is the most valuable feature for me.   

Moreover, the solution's automation handling capability has positively impacted the overall automation process in my experience. 

It's a good tool, but I feel like it doesn't get updated frequently enough. There aren't a lot of new features or a clear roadmap for future improvements. 

While it's technically sound, it could be better adapted to handle newer technologies.

I have been using this solution for one year. 

I would rate the stability a seven out of ten. 

We mostly have medium-sized and enterprise businesses as our customers. 

I would rate the scalability an eight out of ten. 

I would rate my experience with the initial setup an eight out of ten, with ten being easy. 

It could be deployed both on-prem and cloud. The deployment takes around five days. 

I implemented this solution.

I would rate the pricing a six out of ten, with ten being expensive. 

Overall, I would rate the solution an eight out of ten.

We use it mostly in banking, telecom, and also in government. It will be useful for intelligent workflow management. It can be helpful for you to make adaptive decisions. So, it has got some kind of feature called adaptive buttons. Wherein it will understand the user's persona and recommend the next best action and the next desktop.

In Pega, the UI has to be improved because that is the most challenging area that most of our customers ask for because we have to depend on some other React JS or some other tool to bring that kind of UI experience. So, there is a lot of room for improvement in terms of UI and UX.

I have been using this solution for five years. I'm using Pega as a tool for our organization.

It is a scalable solution. We work for different customers, in my particular area there are around 200 customer. It is a B2B solution.  

The deployment process depends on which project we are working on and what kind of delivery we are doing. Also, it depends from customer to customer. 

So, maybe if it is a decisioning framework as it is in telecom, maybe it will take at least six months because it has to self-learn the models, and there is a continuous interaction between artificial intelligence and machine learning teams. But if it is a typical workflow, maybe it is easier, but it depends on how quality engineers are working on that particular workflow. It changes from customer to customer.

I am a system integrator. A solution architect or enterprise architect can help with the deployment. So, the work is shared between the deployment. So, there will be a technical team from the system integrator side, there will be a team who works on the support side, and there will be different team members on the customer side. So, typically, there are ten people involved in the process.

The licensing cost is too high. And the amount which the customers are spending; I don't know if they are getting that kind of value at this particular time when they are setting it up.

The solution has a pay-as-you-go type. So, the pricing depends on the customer and how Pega is dealing with them. 

It is a good start, but as long as you're learning the framework that has been developed by Pega, that will take them far. But in the next five years or ten years, I don't see much visibility because there is a lot of competition across the local vendors, as there are many new local vendors entering the marketplace. Microsoft is giving tough competition to many low-code vendors.

Overall, I would rate the solution a six out of ten.

The feature I like best in Pega Robotic Process Automation is that I'm able to add external DLL section codes. I can inject the JavaScript, and I can write VB.NET, C#.NET, and DLL codes, then inject those codes into the existing process. Mainly, from a development perspective, I like that feature a lot, so if anything is not supported by Pega Robotic Process Automation, then I can build that either in JavaScript or in .NET, then use those functions within the IP.

What I don't like that much in Pega Robotic Process Automation is its monitoring tool because that tool is tightly connected with the platform. If the Pega team can deploy the monitoring tool separately, so that it's a separate solution altogether, then that would be good because currently, if you have to use the monitoring tool, then that means you have to use the Pega Robotic Process Automation platform.

The initial setup for Pega Robotic Process Automation also needs improvement because it is complex.

The only additional feature I'd like to see in the solution is for the monitoring tool to be a stand-alone rather than being tightly coupled with the Pega platform. Looking at the current features of Pega Robotic Process Automation concerning application automation, it covers most of my needs currently.

I've been working on Pega Robotic Process Automation for more than ten years now. I'm still using Pega Robotic Process Automation, but I'm also learning Blue Prism.

Pega Robotic Process Automation is a stable solution. It's stable now, but initially, in 2010, it wasn't stable. Now it's much more stable. My company does experience some issues if the host application isn't stable, but at the moment, Pega Robotic Process Automation is quite stable.

On a scale of one to ten, one being the worst and ten being the best, I would rate the stability of the solution as seven.

Pega Robotic Process Automation is scalable, but you need to integrate it with the Pega platform, so if you aren't using the platform, you have to write some custom code to make the solution scalable. Scaling up Pega Robotic Process Automation is possible, but not easy.

I've worked with the technical support team for Pega Robotic Process Automation and I find support quite good. As soon as I raise a ticket, within a day, I'll get an initial response. The tech will set up a meeting, analyze the issue, then provide a resolution. The support team also lets you know if additional information is needed, so the initial response from the technical support team is quite good.

Setting up Pega Robotic Process Automation is complex. It's not simple to set up.

In terms of Pega Robotic Process Automation pricing, I would rate it a five out of five because the solution has a good price. Pricing is not very high, though I'm unsure of the exact cost, based on my experience, the price for Pega Robotic Process Automation is less than Blue Prism because I worked with a few clients that have both solutions and my clients prefer Pega Robotic Process Automation over Blue Prism particularly because of the licensing costs.

I evaluated UiPath RPA and Blue Prism. 

I've worked on Pega Robotic Process Automation for a long time. I did learn UiPath RPA, but I haven't used it. Blue Prism, on the other hand, is a solution I've just started using, so I prefer Pega Robotic Process Automation because it's a solution I've implemented.

In terms of process automation though, I've discussed this with my colleagues and have concluded that Blue Prism is better.

My rating for Pega Robotic Process Automation is seven out of ten.

My work is focused on RPA solutions, so I know UiPath RPA and Pega Robotic Process Automation.

I'm using version 19.1 of Pega Robotic Process Automation.

In terms of the number of users of Pega Robotic Process Automation, that would depend on where you're using the solution. For example, I worked with one of the telecom providers that had fifty thousand users. I worked with a client in the banking sector and that organization had five thousand users of Pega Robotic Process Automation. Note that I've worked on the text automation or assisted automation only, not on the process automation.

In terms of maintenance, you only need two to three people to maintain Pega Robotic Process Automation.

My experience was predominantly Pega Robotic solutions. I worked as an individual contributor with the developers. And I worked with the team, I led a team of five members in the last organization.

We worked in insurance. My last couple of projects were in insurance. It is mostly back-end process automation, like manual tedious tasks. One of the latest use cases we worked on was for creating third-party cases for dubious claims. Every insurance agency has an investigative third-party company that investigates dubious claims. Every time we have to log a claim, it was a very tedious task. Previously, each day, users would log about 150 claims with the third party and each one would take five to six minutes. We have automated this process.

The data entry and the automation of data entry are the most valuable aspects of the product. It was very smooth and very seamless to create automations. There was no scope for any errors and it was really error-free. That really helped us.

The initial setup was pretty easy.

There aren’t many areas for improvement. The process itself was really fine. There was no unnecessary jargon and unnecessary steps.

In one of the past projects, however, I observed they made it unnecessarily complex by, let's just say, exporting a screenshot at the end of each step which was cumbersome - especially when you could just save it in a drive locally or a shared drive. Extra necessary steps just make the automation complex. You really need to think out the process and simplify as much as possible to avoid complexity.

I would like to see some features improved that are already in there. One thing is the ease of deployment. They have integrated the deployment. They have tied the deployment with the Pega BPM product, the robot manager. You need to have the BPM installed. On top of that, you need to install this robotic manager solution. I understand that they want to tie their products together and make customers use both or all of their products in one suite; however, it can be annoying. It makes things unnecessarily complex. It would have been great if they just provided a standalone deployment system.

Features-wise, I'd like to see the OCR Optical Character Recognition. Pega is way behind its competitors in terms of OCR implementation and OCR capabilities. I'd like to see that improve. I haven't personally tried out many OCR solutions, however, on a proof of concept level, we did a few things and there is significant room for improvement there.

I've been working with RPA solutions for about five years now. I’ve used Pega from the beginning. My entire RPA experience was predominantly with Pega Robotics and also WinAutomation. It’s been around four years now.

The solution was stable. There were no bugs or glitches and it didn’t crash or freeze. It was reliable.

Just in the UK, there were about seven to eight people using the solution. It is not done 24 hours a day. There are no dedicated resources. Manually, we may work on it for one to two hours a day. Once it’s deployed, just one or two machines are needed to run the solution.

I have found the solution to be scalable.

Pega Robotics itself makes solutions really scalable. If you want to integrate it into this process with existing automation, you could just plug in this project to the existing ones. The scalability is really good.

I personally have dealt with multiple issues and have gotten support from them. The response time is definitely quick. The turnaround time is good. However, when solutions get tricky, where the answer is not straightforward, and there is research that needs to be done, they take time. That is quite understandable. However, it would've been great if solutions were provided quicker. You don't reach out to them unless it is absolutely essential. First, you try to fix it internally. Once you reach out to them, it’s vital to get a quick resolution. Therefore, that turnaround time is imperative.

Neutral

I also have experience with WinAutomation.

This use case itself is not that complex, which meant the setup was easy. It is pretty much a straightforward solution. It is A to B to C. There were no exceptions. On paper, it was a very good solution with a good process and a very stable process at that, which made things easy. Some are relatively easy to implement. They vary. I’ve had others that were harder in the past.

The last project was entirely an individual project. For the deployment, we tested along with the user. We did user acceptance testing. Once it was approved by everyone, we did a pilot run, and then we handed this over to the deployment team. They deployed it. They were a team of six or seven members. They handled setups individually as well. Typically there are not more than three hands on an entire solution. Once the solution was handed over to the client, it took them a day or two to set everything up.

Maintenance is handled via tickets. If there are any improvements to be made, we get tickets and resolve the issue. The engineers typically work on the solution and fix anything. Upgrades depend on the ticket's priority. It’s allocated to whoever has time to pick it up and action the maintenance.

The ROI is good. RPA, in general, provides a good return on investment. Pega Robotics is not an exception. They’re exceptionally good

Licensing is based on the number of machines that you deploy it on. Usually, it is based on the other products you buy per anum or per machine. In Pega Robotics, it is based on the number of solutions you deploy and the number of times you run. The cost is variable. My previous client worked based on this hourly model, the number of robots and the number of solutions that are run. They also provided per machine.

Pega doesn't just provide these robotic solutions. It comes with their BPM products as well. It depends on what the client uses. If the client uses this along with the BPM products, They might get added discounts, et cetera. Every contract is unique.

I’m a customer and end-user.

We started with the eighth version. The last one I used was 19.1. Until the latest build from February, we used the 19 version, the 19.1s. We stopped using the solution in February.

I’d rate the solution seven out of ten.

If a person is familiar with the .NET framework, it will be a great visual studio in general. Plus, picking up Pega Robotics will be very easy for them. It’s good in general to brush up on programming skills, along with Pega Robotics. If you need to add capabilities out of the scope or out of the realm of abilities of the tool, programming is essential to customize your solution.

The tool is for OGC processes. 

We have asked our team to identify manual areas and automate them. 

I am impressed with the tool's recording feature.

I would like to improve the tool's integration features and stability. 

I have been using the product for the past two and a half years. 

I would rate the tool's stability a seven out of ten.

I would rate the tool's scalability a seven out of ten. My organization has around 350 users for the product. 

My organization used UiPath earlier. 

The tool's setup is easy and gets completed in minutes. I would rate it an eight out of ten. We have a platform team who can take care of the deployment process. 

I would rate the product's pricing a nine out of ten. 

I would rate the product a seven out of ten. Pega has RPA and DPA. Pega is fantastic when it comes to DPA. The same is not the case with RPA. Pega's RPA is not on par with other tools and needs a lot of improvement. 

Our use cases are for the RD and the RDP processes. I'm the technical project manager. 

This solution is a kind of visual studio base. You can do a lot of things with it including adding custom DOLs. The most valuable feature is the logs. The solution is user-friendly, easy to understand and has many features including the ability to track. Pega has a very quick loading time which makes for great performance and provides good data transcripts. 

One of the difficulties we have is not knowing when we will receive alerts.

I've been using this solution for about 10 years. 

The solution is very stable. 

The customer support is excellent. 

Positive

The initial process is very straightforward. 

We've definitely seen a return on the investment in this product. 

The solution is quite expensive.

Concept-wise, all robotics platforms are similar. The difference between them is in the technical aspects, the methods and properties. Once you start learning Pega, the additional skills can easily double up because sometimes you need to write your code in a visual studio, making it also a visual studio platform.

I rate this solution nine out of 10. 

We are using Pega for automation for a client that has huge hangars where all the planes and helicopters are stationed once they are back from the journey. There is a particular person called an aero inspector who goes to each and every helicopter or plane and collects and inspects all the elements of it whether it's a small plane or a large plane, such as the engine, windshield, air conditioning, etc. It's a 300-checkpoint document that he has to fill up. We have developed a mobile application for this particular individual or for his entire team, so instead of writing it down with a pen and paper, they can now just go and do it with a few clicks. The entire thing is transmitted to Pega, and then Pega feeds it into their SED system so that everything is recorded, everything is seen, and the management has the dashboards for what's happening on the ground for various businesses. This is only for their operations in Switzerland, Germany, and Sweden.

We are working with Pega's latest version.

Pega is very mature. It's very old. They have grown with time, and they have learned. Other robotic process automation solutions are basically focused on only doing the automation, whereas Pega also gives you a workflow system so that you can create a workflow.

A good thing about Pega is that the resource availability is pretty good. If you go out in the market looking for a Pega resource versus an ABBYY resource, it's most likely that you will get a Pega resource much earlier than an ABBYY resource.

The new players such as UiPath and ABBYY are moving very quickly, but Pega is not. I'd definitely like to see Pega doing a few more interesting things on the AI or machine learning front so that we can use the platform for multiple things.

I've been working with this solution for six years.

It's very stable.

On-premise, it's a bit tricky and time taking, but on the cloud, it's just a few clicks.

Their support is good. Pega has a global support team, and you can reach out to them at any time. They also provide support on non-working hours at the US time and UK time. So, you can get support on Saturdays and Sundays. If you have an outage at 01:00 UK time, they will provide support to you.

It's a bit more complex than ABBYY. It should take around three to four weeks to set it up to render all the files inside and do things over there. 

They offer both on-premises and cloud models. The deployment is pretty simple. One developer is enough to do the deployment. It's also very easy to maintain. You can reach out to their support team at any time. So, the maintenance part is pretty good.

For one of the clients, the profit went up by 7.5% in the last quarter.

Pega is as competitive as the basic players such as UiPath or Automation Anywhere. UiPath is the most expensive, but Pega is at par with Automation Anywhere.

I've only used the enterprise licenses so far. I've not used any standard licenses. The licenses are already secured and given to me, and then my team starts working on that, so I do not have a very good idea about it.

Pega is an LCNC platform, so learning Pega is very easy. It would not cost you even a single penny to start learning it. Everything is available on YouTube and the cloud. You should have at least a basic idea of Pega before doing any installations or using it. As a program manager and as the head of robotic process automation, I've seen people burning their hands with smaller companies. They didn't have any idea. They picked up the project just to make some money and then came to me. It would be ideal if someone from the IT team of the customer at least does a basic Pega course, which is totally free, before implementing it.

For workflows, Pega is the ideal tool. It's probably one of the best and one of the first ones in the world, but in terms of RPA, there are many other players, such as Automation Anywhere and UiPath, who are ahead of Pega. That's not because of the technology they have. That's because of the marketing and sales initiatives that they have. For example, currently, UiPath is the market leader in RPA, but UiPath's product is not as good as Automation Anywhere. UiPath is the leader because their sales team is very aggressive. So, it's not about the technology part. There are many aspects of how a particular product grows. Pega is not expanding its operations into Asia, Japan, Australia, New Zealand, etc. Until and unless you have a global presence, you will not be counted as number one even if you are the best in the market.

I'd rate Pega a seven out of ten. Its rating would be a bit lesser than UiPath and Automation Anywhere.