Pega Platform Reviews

I use Pega BPM to automate business use cases and integrate third-party application data into applications designed on Pega Platform.

Previously, our HR onboarding application ran in silos, so everything was happening separately. Pega BPM allowed us to consolidate all the data in one place, from which we could define our business workflow. This means that we have the entire flow running in one application from start to end with the help of third-party application data.

Pega BPM's most valuable features are case management, integration, the convenience of using REST APIs, and the ease of changing things at the UI level.

Pega BPM could be improved by including token-based authentication and extending its integration options. In the next release, Pega should live up to their claim to be low-code/no-code and make their platform more simple and UI-based.

I've been using Pega BPM for almost two years.

Pega BPM is stable.

Pega BPM is scalable.

The initial setup wasn't complex, but you have to define your class structure and architecture properly. Deployment took around a month. Also, Pega says BPM is low-code/no-code, but that's not true - you need intervention as you can't design the application without some knowledge about it.

We used an in-house team.

Pega is expensive. If your company has a good amount of money to spend, go for Pega as it has many things readily available out of the box. But if you're looking to save money, you may be better going for an open-source platform.

I also evaluated WaveMaker, but Pega has features that aren't available on WaveMaker.

Pega BPM is a very good tool if you have the budget to spend on it and you need to automate any business process wherein you get the data from multiple sources. I would rate Pega BPM as six out of ten.

The rule engines work well.

It is a stable product.

The solution could be more scalable. 

It has some DevOps limitations.

The product could be more robust and faster compared to what they have right now.

Pega is also stable. It is also an old product. They have DevOps limitations if we compare it with Appian. That said, from the tool perspective, Pega is stable and reliable.

It is not as scalable, as, for example, Appian. However, I don't have extensive knowledge and therefore can't speak widely on the scaling process. 

I've never contacted technical support. I'm not sure if they are helpful and responsive. I've never talked directly with them. 

I've also used Appian.

I have limited experience with Pega. I don't have extensive knowledge about the Pega, however, there are a few things, which may be the reason to prefer Appian over the Pega. The engines, the rule engines, internally, on Appian or Pega work. However, in terms of how they process your request Appian is more scalable and more robust.

The setup is also good. It also provides the cloud, so it's not an issue from that perspective. I did not use it very extensively, however, they do have a cloud, so it's fine in terms of implementation.

I can't speak about the exact costs. I don't deal with that aspect of the solution. 

I don't have that much experience on the Pega, however, from what I have experienced, there's a little bit more that can be offered. I'd rate it a six out of ten.

We use the solution basically to run any custom process that the client wants to have, or needs to run their business on. For example, the approval process or any kind of business process that can be run using the Pega Platform.

It's low code. That is very useful. A business value architect will have zero coding to do, and he can create a business flow on top of that. The technical developer can handle further things. 

Apart from that, the kind of APIs that they support is also very nice. It also has a lot of APIs out of the box. It can directly connect to Fitbit, it can directly connect to Google Maps, et cetera. That API exposure is also a good thing. They are very easy and very reliable to use, the APIs.

The setup was simple. 

It's a stable solution.

The solution has very helpful technical support.

It can scale pretty well.

A few things I would like them to improve include, first of all, that they don't have any open-source learning platform. To learn Pega, you need to be a partner. If someone just wants to learn Pega for the sake of learning, they won't be able to do so as they don't give access to that.

I would like to have an integrated process mining capability inside Pega. It will be like an entire digital transformation thing then. You don't need two or three sources. Similar to Signavio. Signavio runs BPM, it does modeling, and it is having process mining as well. In Pega, we have modeling, we have RPA, and we have BPM, however, we don't have process mining right now.

I've been using the solution for three years.

It's quite stable. This means we haven't encountered any issues. And even if there are issues, their support is very responsive.

The product is quite scalable as it's a low-code platform. 

The solution adjusts well to different devices. They have this adaptation that if you open it on a tablet, then the screen will adjust accordingly. If you open it on a PC, the screen adjusts it accordingly in Pega. Android as well.

There are more than 25,000 people on the solution.

We've worked with technical support in the past. Whenever there's downtime or whenever something is not working, we need to get in touch with the Pega technical team.

Neutral

I'm also aware of Appian. Even if Pega says that it's a low-code platform, when I compare it to Appian, Appian is more low code when compared to Pega.

The initial setup is very simple and straightforward. 

You need to pay for licensing. It was quite expensive. I'd rate it four and a half out of five in terms of how expensive it is. 

My organization is a service provider for Pega. We're implementation partners. If we use it completely depends on what the client wants and needs.

If you are using it for the first time, you probably should have a consulted implementation partner as well. That said, it is easy to use. It shouldn't be a problem. It's very flexible.

I'd rate the solution eight out of ten. We generally don't encounter any issues as far as Pega is concerned. Whenever there's an issue, there's a quick resolution. 

PegaRULES is used more for business process management. Perhaps in a bank or any other organization. If you want to automate anything, you may require a tool, which is, simply building the same thing in Java. 

People choose Pega because it's a flow-oriented tool that is already predefined and you can plug and play.

I can say that less development effort is required for developers, allowing them to focus on business problems rather than technical issues. It corresponds to every BPM, so it serves the same function.

Pega also sells the same so that you can integrate with legacy applications or with different applications that may or may not have AP capability. You can use UiPath in between with PegaRULES integration.

There are a lot of features, which most people prefer.

Case Management is the most valuable feature of PegaRULES, which is not found in other BPM tools.

Containerization should be improved in relation to Pega because Camunda is deployable in the containerization deployment process. Pega is trying to move in that direction, but that will have to improve slightly.

I have been using PegaRULES for 15 years.

Pega has multiple models, and I believe a few teams are cloud-based. Our organization is mostly moving to the cloud, but not entirely. However, we use on-premises deployment.

PegaRULES is extremely stable. It is still dependent on developers. 

Initially, I believe we will require the services of architects to set up the cloud structure and design. Everything must be thoroughly reviewed. Developers will need to follow suit. In terms of stability, I would say it's a solid application. How you use it is determined by how you built it. You must exercise caution when developing the application. If teams attempt to build the Pega without the necessary experience, performance issues and other issues may arise. That design must be correct, and it must be reviewed and monitored. I believe it will be able to stabilize this application.

It can also be scaled up. It is determined by the scope of the data, but it can be scaled up to meet the requirements of the application. It's in hardware and adding hardware to an extra. It will follow the data availability features. Pega will support the ability of Java applications to scale up based on stability. I don't know much about that particular hardware side, but I can say that it can scale up to meet the needs of the user. It is dependent on the application or how large these applications are. It can be scaled to any size.

The number of users is dependent on the project. There are large projects that may involve 10,000 or more users. In a few applications, you may see only 1,000 or 500 users or something along those lines. It is dependent on the application and who is using it.

I have contacted technical support, and they are very good.

The technical support for Pega is excellent. They were able to assist us and even guide us if we had any issues. If you contact Pega technical support, we'll find a solution right away.

I would rate them a five out of five.

Positive

We mostly use Pega products.

Pega provides documentation. The same documentation can be followed during their own deployment process.

In my opinion, it's not complicated in terms of deployment; but it depends on how your applications will be deployed. It's the same method. 

Pega will also assist you in this regard. It simplifies the deployment process and makes it easier to set up others.

I would rate the initial setup a five out of five.

If everything works and is ready, the initial setup can be deployed in half a day.

In terms of the price, if I were to compare Pega to other tools, it would be more expensive, but it would also provide you with the same features.

If there are applications that scale up to the enterprise level, we would go with Pega, and if it's a smaller application with a smaller workflow, or if they can't afford to invest that much money, they'll go with less expensive tools such as Appian. Camunda is open source, we have people working on it.

The licensing fees are not that much.

I would rate PegaRULES an eight out of ten.

I use the product for process orchestration purposes.

There are a lot of frameworks in the product. I use Pega PRPC the most.

There are no job opportunities for users who have expertise in Pega. They are learning the certification program but need work. Pega should work on redefining their model and creating a demand for their skills. They need to reach a large number of business organizations.

I have been using Pega BPM for five years.

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

We have more than 500 Pega BPM users in our organization. We plan to increase the usage.

The initial setup process is straightforward.

We do not have to purchase any licenses for the product.

I recommend Pega BPM to others and rate it an eight out of ten.

We use the solution as a low-code development tool. The tool has pre-built rules. Hence, they can be reused and configured as per client requirements.

We can use the rules as per the class.

PegaRULES need to improve its JVM. It needs to enhance the operation speed and memory size.

I have been working with the solution for four years.

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

I would rate PegaRULES' scalability a nine out of ten.

The tool's support will take time to resolve issues if it's a product enhancement issue. Application-related issues will be resolved immediately.

Positive

PegaRULES' setup is easy.

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

PegaRULES is mainly for enterprise companies and I would rate it a nine out of ten.

If you search on Google, basically you will see a lot of use cases that you can implement. Wherever you have a kind of automation, a case management, a kind of logic, a kind of an exhaustive process flow where a particular task will flow from one group to another. In all those situations, Pega can be a very good fit. Nowadays, Pega provides machine learning, automation intelligence, DevOps, et cetera. Whatever is as per market standard, those are there in Pega.

Pega has lots of industry solutions as well which are targeted for specific industries such as financial, healthcare, or insurance. The product helps you to build faster. 

Pega is a niche product and any workflow management kind of use case, or maybe automation kind of use case can be implemented using Pega. The only thing that you need, is the right skillset. Pega is a very customizable product. You need to know the product very well to implement it to a proper standard. 

Pega has been on the market for quite a long time. I'm working with Pega for the last 15 years and they always have a lot of new features.

The way it is adapting to new changes is quite useful. The way it is changing itself to survive in the industry with other BPM tools and being competitive every time. 

With Pega you can deliver some things pretty quickly. You can deliver a prototype for what Pega calls a Minimum Viable Product or Minimum Lovable Project, MLP, very, very fast. 

The solution is stable.

You can scale the solution if you size it right at the outset.

It's very customizable.

You can use it for many industries.

There are lots of very useful features. They're constantly adding more items to the product.

There are lots of great automation and machine learning aspects.

The initial setup can take a while. You need to have the right people in place to handle it effectively. 

It can be pretty expensive and is better for larger enterprises. 

I've been working with Pega probably for the last 15 years.

It's a stable solution. 

The scalability is pretty good. Whenever we work in Pega, we propose this product to any customer based on their needs, how many tech resources they have, how many concurrent resources there will be, what their daily inbound volume is, et cetera. Based on that, we get the hardware sizing from Pega. If you do the right kind of estimation and start with the proper infrastructure, you will be able to basically ensure robustness, high availability, almost zero downtime, and everything can be shipped. 

Pega tech support is there technically and they do help us a lot. In the recent past, we have seen a little bit of trouble here and there, where tech support is taking a long time to fix some issues. Usually, if we route Pega with proper channels, then we can manage good support. 

They have a good tech support process and they also provide a good academy resource. Someone new to Pega can get a lot of documentation and material to learn the product.

I am from a Pega background and I do not know much about other competitive products in the market, so my feedback or whatever I'm giving, that is maybe a bit biased as I have been working with Pega only.

The initial setup takes time. You have to gather people with the right skills. If you have that then it won't take that much time at all. Basically, the main selling point of Pega is it can reduce your entire timeline drastically. The constraint is you need to have the right kind of people. 

Pega is a huge tool, and honestly speaking, nowadays, there are a lot of sections in Pega where there is no single user who knows the entire feature set. It's a big and complicated product. You need to have the right blend of team members to set up, to have an easy initial setup. In those instances, it might take six to eight weeks. After that, I have seen people delivering some base prototypes and a walking model in a few weeks.

We help our clients set up the solution.

Nowadays, standard open affairs configuration is there. If you ask me how much time it'll take to build it, it's maybe a few hours or maybe two to three days. When we talk about the entire project, we need to take care of a lot of things, not just the build part. Usually, there are integrations necessary and we have to have a lot of testing in place to manage different combinations, load testing, performance testing, and security testing. Most of the time clients ask for all these things. That adds to the setup timeline, however, the build is not included in that constantly changing time.

This is something every enterprise has to handle separately with Pega. As a vendor, we are not supposed to comment on pricing.

We use both cloud and on-premises deployments. In earlier days, Pega used to support only on-premises. Nowadays, it's supporting the cloud as well.

I definitely do recommend the product. Pega is a competitive product if it's not a small enterprise. Small companies usually avoid this product as there are a lot of open source products that are less costly there in the market. 

Based on the features I can recommend it. 

I'd rate the solution nine out of ten.

There is a feature to accelerate the development so that business analysts can directly create their user stories and assign the task to the developers. It's called DCO.

Pega is claiming they're into low code but as per Gartner Magic Quadrant, Pega is not there now. Appian, OutSystems, Mendix, Salesforce, and Microsoft Power Platform are the major leaders in the market as low-code platforms as per Gartner Magic Quadrant. Pega has to improve if they would like to gain their position in the low-code space. They would have to improve major functionalities that these low-code vendors and low-code platforms have like their mobile compatibility. A citizen developer can easily make B2C mobile apps.

Pega has to come up with a lot of improvements in these low-code areas for the citizen developers who can easily create mobile apps with minimal coding or no coding. With other competitors like Appian, OutSystems, and Mendix, you can do it using visual modeling.

The price could also be improved.

I have been working with Pega for about six years as a solution architect.

Pega is a stable product. If you're solving a business problem for case management, Pega is the best for case management solution, but the product architecture is entirely different. It's rule based. It's not popular for UI or UX management.

Pega's technical support is not as friendly as Appian. 

I would rate Appian higher than Pega. The price of Pega is a bit higher than Appian and the software isn't as friendly.

The price could be lower.

I would rate this solution 8 out of 10.