Pega Platform Reviews

Application development is very rapid. A lot of code gets reused while building the applications, which is something we highly appreciate. 

People are also very happy with the robotic process automation and the dashboards. They are very good.

Its implementation in the public sector was a bit complex. 

In terms of features, I have not come across any limitations in the last four or five years. I'm on the sales side. I work with customers, and my role involves reading a customer's mind and providing the best solution so that all pain areas are addressed. Pega has got very good features and tools. I didn't come across any limitation where a customer wanted something, and we were not able to provide that. Generally, whatever a customer demands, we are able to meet that demand. 

We have been using Pega since 2017 or 2018. It has been about four or five years.

Its stability is good.

I have not come across any scalability issues. The government customer has perpetual licenses. We are very populous in nature, and people come from the web as well from the mobile. They are able to process all those requests. I've not come across any issues.

Their support has been excellent because the person who heads the Pega practice is very senior. He was the sixth employee of Pega in the UK. He has an excellent relationship with the CEO, Mark Allison. Mark has been to our development centers because we have been expanding in the last three or four years. Our focus is banks. So, he has been visiting us. 

As an organization also, there has been tremendous support from Pega. We are a small but growing organization. We are not very big, but we are competing with the big brothers in the industry who have been there for over decades.

The finance part that people were doing was not too difficult. It was straightforward. However, when we implemented it in the public sector, it was a bit complex because of the disparities in the data structures and the maturity of the customer. They had different ERPs. So, it was a bit tough, but they appreciated it. We are a Commonwealth country. So, whatever works in India would work in any Commonwealth country. We have an education department here, and there are two categories: higher education and technical education. Based on merit and a lot of other parameters, such as caste, people have to be given subsidies, grants, and aid, which change with the political system. A new leader can announce that he wants to give laptops to all standard 12 students who have scored 90% marks. So, all such rules can be built very quickly. The SLA is for about five working days. We have to complete a new request in five working days. Most of the customers here want parallel development. Normally, we have six to eight teams working. Generally, we give a new Pega solution in about 100 days. After a solution is rolled out, we have a separate team with about 10 people, and they cater to 10 and 15 customers.

There is a team that looks into its cost. When it comes to licenses, we don't get involved with selling the licenses. We insist that Pega sells the licenses directly to the customer. This is the model we work with. We make money only through our implementation.

The licensing is on a yearly basis. Because of our special relationship, all the training certifications are free of cost. All our employees can do Pega certifications at zero cost. It is all on Pega.

We have a small team based out of London, UK. We have Pega and Appian. We don't have anything else. It is a very small team, and we only cater to financial institutions. We are trying to acquire a few Pega customers in the Middle East from the UK.

I am based out of India, Bangalore, and in India, Pega is just coming in. There are not many installations in the government as well as enterprise sectors. There is a private sector bank that is trying to move to BPM. They have not yet made a decision about what they want to procure, but they have been talking to Appian and Pega teams.

I would rate it a 10 out of 10. We have had a beautiful experience with them.

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.

We had an audit team for order management, primarily focused on mobile communications. This encompassed tasks such as SIM card dispatch and user configurations.

The most notable feature is the dynamic workflow changes, allowing adjustments without completing the entire cycle. Transitioning from test to build to production was seamless and on the fly, which is something truly remarkable about Pega. Additionally, the workflow creation doesn't require users with extensive technical skills, thanks to its low-code platform, making it accessible and efficient.

The pricing could be flexible and have multiple options. It is mainly suitable for large enterprises. They could have subscription plans to cater SMEs.

I have been using Pega BPM for four to five years.

I rate the solution’s stability a seven out of ten.

The product might not have been developed, possibly due to the absence of a dedicated product owner overseeing its development. Those who did the coding might not have performed up to standard. Improvements could be made in that area, as the code quality was lacking, affecting the scalability of the product.

300-400 users are using this solution. I rate the solution’s scalability as a five point five because we have lot of performance issues.

The setup process is fairly complex, and we always need an integrator for implementing it. It requires expertise in the platform. It's essential to have someone with Pega expertise rather than relying solely on regular users.

Pega is expensive than Versace. I rate the solution’s pricing a six on ten.

When it comes to Pega, I haven't come across any particularly outstanding out-of-the-box functionalities. However, I appreciate their local, no-code approach, which makes it easy for users to quickly grasp how to create work solutions. Although case management is included, it doesn't seem as flashy compared to other VPNs.

Pega was coming with lot of out of the box integration options with APIs and others but, we did not drive the AI part.

Based on the specific use case, I would recommend it to companies prioritizing user functionality over scalability in their portfolio. However, it's crucial to collaborate with a skilled integrator to ensure smooth implementation.

Overall, I rate the solution a seven out of ten.

Regarding the primary use cases of Pega BPM, I can say that my company deals with multiple domains, like the government sector, banking, financial institutions, telecom, health care, and multiple domains that require Pega BPM.

The most valuable feature of the solution, I believe, is case management, which sets it apart from the rest of the solutions in the market.

I believe that Pega's strategy when it comes to the UX part is not that great currently as compared to the other emerging BPM tools in the market. I look forward to seeing the UX part of the solution improved in a much better manner.

I have been using Pega BPM for nine and a half years. My company's customers use the solution. My company has a partnership with Pega.

It is a stable solution.

It is a scalable solution.

The solution's technical support is good. My company is able to acquire the required assistance from the solution's technical support team, and they also provide consultancy services. I rate the technical support a nine out of ten.

Positive

I wouldn't say that I have used any other solutions previously, but I was trained to use TIBCO, a low-code platform.

The initial setup of Pega BPM is neither easy nor complex, so it falls somewhere in the middle. Pega has provided options for automation for the setup phase, but still, its setup phase is not as direct as some of the other tools in the market.

Pega BPM has set a path for its setup phase, wherein you need to go ahead with Helm chart automation since Pega is a very wide solution, and infrastructures can differ for different companies. Pega doesn't offer something specific, like Terraform. In other technologies, the product gets installed with one click or just a few clicks, but with Pega, a person has to work a lot on the infrastructure part as well.

The solution is deployed on the cloud and on-premises. My company provides the solution on Pega Cloud, technology-specific clouds, client-specific clouds, or on-premises.

The complete implementation process for Pega BPM would take a minimum of two to three days, prioritizing the infrastructure first and then the product.

Two people, one from the infrastructure end and one from the product end, which is the technical support person from Pega, would be needed to complete the deployment of the product. There is also the need to have Pega's partner who does the installation, making him or her the third person involved in the deployment.

The price of Pega BPM falls on the higher side of the spectrum if I were to compare it with other solutions in the market. What sets Pega BPM apart from other solutions in the market is that it has many features, including the use of AI and modern gen AI, which currently is not something you can experience in any other tools in the market. The aforementioned details contribute to making Pega BPM a leader in the market.

I would say the people who have realistic business process management kinds of use cases can go ahead and purchase Pega BPM blindfolded since it serves as a great case management tool, better than any other tool in the market. Pega BPM provides great visibility to its users, especially when you are involved in designing, where it will show you the number of stages, steps, processes, data, and even the people or parties who were involved, making it a great tool for case management. Presently, Pega BPM is heading towards the inclusion of more AI, owing to which it can be considered as one of the leaders in the market. The CRM part of the solution is one of its key selling features.

Though the solution's UX is good for developers, when you have to deliver the product to the customer, you don't get too many options for customization that can help you create an appealing view.

I rate the overall solution an eight and a half to nine out of ten.

We use Pega BPM for one of the finance applications and the different order and demand management.

Pega BPM offers a lot of out-of-the-box functionalities.

Pega BPM's documentation should be improved, especially for freshers or new trainees.

Pega BPM's pricing could be improved because it is expensive. People are not choosing Pega BPM because of its price and are moving to open-source or cost-effective solutions like Camunda.

I have been using Pega BPM for around two years.

Pega BPM is a very stable solution.

Pega BPM is a scalable solution. Around 10,000 users are using Pega BPM.

Pega BPM's initial setup is easy.

Users have to pay a yearly license cost for Pega BPM, which is expensive.

I am using the latest version of Pega BPM.

When we started, it was a team of 10, and now 23 employees are involved in the solution's deployment and maintenance. The solution has nine to ten developers and testers.

Overall, I rate Pega BPM a seven out of ten.

The solution is used in banking, telecoms, and in insurance.

In certain circumstances, it can be fairly straightforward to execute and deploy new modifications.

The usability of the solution for developers is sometimes difficult to work with because instead of fixing the existing bugs in the previous version, there is always a rush to push out a new version leaving the bugs in the old versions unresolved. I would like the bugs to be fixed before moving on to a new version.

Upgrading versions is a challenge and expensive. PegaRULES should try to spend more time on developing the newest versions in such a way the upgrade could be easier, or in a way that clients don't need to upgrade every year to a new version or every couple of years in order to plan expenses and complicated upgrades.

The UI needs reworking. PegaRULES has added new features to the UI, but I'm not sure it's the right direction.

I have been using the solution for over ten years.                                                                                        

I give the stability a five out of ten. The solution is not the most stable solution available.

I rate the scalability of the solution a five out of ten, taking into account the requirements, user base, licensing, and hardware constraints that could potentially limit scalability.

The technical support is responsive, but sometimes negotiation is necessary to get the materials needed to address simple bugs. When working on a complex project sometimes patches can be found and the response is usually helpful. Often they'll come back with a fix and point to where the problem lies, however, there have been occasions where upgrading to the next version is the only solution, regardless of whether it is feasible for the client or even possible.

Neutral

The initial setup is challenging. I give the initial setup a three out of ten.

Some clients work with older versions and eventually choose to upgrade, which can take anywhere from five to ten years. This upgrade process is very expensive; although I haven't been on the sales team responsible for the pricing, I know it costs millions of dollars.

I give the price a five out of ten.

I give the solution a five out of ten.

We have around 20 people using the solution in our organization.

PegaRULES approach is unique; its own hierarchy and structure of applications are distinct from most other similar tools; which are more object-oriented and adhere to traditional methods.

We are using Pega BPM for all the major domains, insurance, banking, FMCG, and telecom.

The most valuable features of Pega BPM are low code, no code, functionality, and easy development.

Pega BPM can improve product management, case management, omnichannel, CDH, and the customer data hub. All the major domains can improve. Additionally, more AI functionality and proper integrations with Pega RPA would be helpful.

I have been using Pega BPM for approximately four years.

I rate the stability of Pega BPM a nine out of ten.

We have approximately 2,000 users using this solution.

I rate the scalability of Pega BPM a nine out of ten.

I have contacted the support from Pega BPM.

I rate Pega BPM an eight out of ten.

Positive

I have previously used OutSystems.

Both OutSystems and Pega BPM are Java-based applications with similar implementation methods. However, Pega BPM has a more integrated digital transformation solution and includes tools for RPA, while OutSystems does not have a specific focus on RPA. Pega BPM has more solutions geared toward digital transformations.

The initial setup of Pega BPM can be complex if the implementer does not have Java knowledge.

The price of Pega BPM is in the middle range compared to other solutions.

I rate the price of Pega BPM a five out of ten.

We have 30 people for the maintenance of the solution.

I rate Pega BPM n eight out of ten.