Pega Platform Reviews

Pega BPM can be deployed on-premise and in the cloud.

All the scalability issues are addressed with Pega BPM because you can create enterprise-grade solutions with the architecture it has.

Pega BPM has a use case in every sector and area, such as manufacturing, insurance, vendor suppliers, and vendor collaboration hubs.

The most valuable feature of Pega BPM is its architecture.

Pega BPM could improve the UI, it is poorly designed to have a good UX experience.

I have been using Pega BPM for approximately six years.

Pega BPM is stable.

Pega BPM is enterprise-grade and scalable.

The support from Pega BPM is very good.

Using Pega BPM on the cloud is simple. Within five minutes you can have your own Pega BPM instance.

The licensing model from Pega BPM is too complex and is more expensive than other solutions, such as SAP. The overall price of the solution depends on the use case.

My advice to those before purchasing is the UI capability is not good and the cost of the implementation generally is higher in the implementation.

I rate Pega BPM

They use it for marketing and case management. It is also used for workflow process automation and market intelligence, using the solution’s AI capabilities.

The case management functionality of this solution has been most valuable.

There is a scarcity of resources who have worked with this solution before.

I have been using this solution for eight years.

This is a stable solution.

This is a scalable solution.

I would rate the customer service for this solution a four out of five.

Positive

The initial setup for this solution is not that complex.

The enterprise product has the best features as a cloud product. It is the market leader in the BPM space.

I would rate this solution a nine out of ten.

We are a strategy consultancy for someone who is looking for a Low-code No-code platform for the utilization of digitized service processes. We can determine if Pega BPM is the right fit for them because it can be deployed on the Cloud,on-premise, Kubernetes, and Dockers. We are in discussions with customers with many other solutions, such as OutSystems and Mendix. From a strategic point of view. We're not going to implement only one service tomorrow.

We mostly use European providers. We do not use hyper scalers because of privacy concerns, such as Google, Microsoft, and Amazon.

We use Pega BPM for simple service management processes. We are a consultancy that works for the government. We look at public services and how public services can be supported. These new types of workflow technologies where you to have end-to-end case management. They can be used for public services processes that are created on these platforms.

Pega BPM could improve the artificial intelligence capabilities because they are always valuable and case management for all types of industries is important. Additionally, the reporting performance management capabilities could be better because you want to have insights into how your processes are working, such as Cloud protection. The whole range can be better. However, the platforms are improving every year, they are on the right track.

In the next release of Pega BPM, they should add more ways to do the customer interaction fields in the portals.

I have been using Pega BPM for more than one year.

Pega BPM is scalable. If you have larger data models, for example, thousands and millions of transactions, they have their limits. Larger data models need to be improved. It's not only technically scalable, for instance, if one organization develops a solution built on ServiceNow or Pega BPM, how can you transfer the solution to the next organization that has the same platform. They have a marketplace on most of the platforms where third-party vendors can show their services. For a public organization, if you develop a small application, the next town could use it the same way. How to transfer easily from one to another one. It might not be a relevant case for private companies because you are in competition. There's no need to give away knowledge. However, in the public domain, it's a different case but it's very special, nothing in general.

The technical support of Pega BPM is very good.

If you work with any of those platforms such as Pega BPM, Mendix, OutSystems, or ServiceNow, they have different sweet spots. You should always think about what you really want to accomplish. What do you want to do with those platforms, you have to choose between Pega BPM or ServiceNow. You have to decide what is the right provider, and it is not one-fits-all. 

The platforms are used to be faster. You have citizen developers who can build faster solutions but in the end, if you have no governance, no strict rules on how to use it there can be problems. For example, to put out a fire somewhere, you can do it in 10,000 different ways. If you don't have strict rules, how to do it, you might end up with a crazy solution that you can't manage over time, such as the maintainability of those solutions or of the platform ecosystem in general.  You need strict governance or rules of what to do and how to do it. Otherwise, it will be like a crazy zoo of different solutions and you don't know what it is, how they work, or why they work. If everyone is able to use a solution but they are not using it in the same way it can be improper and this is why governance and rules need to be applied.

I rate Pega BPM a seven out of ten.

Pega BPM is good, it is not the worst solution you can find on the market. However, it depends on what you're looking for. It has to meet the use case that you are looking to solve. Other solutions, such as OutSystems and Mendix, they're more open-minded, you can do whatever you want to do, but they don't have strong case management. In my industry, it's more or less, very simple service processes.

I've been using Pega BPM for insurance underwriting, claims management, and pricing.

What we like about Pega BPM is their case management feature which we find powerful. We also like its workflow capability.

The licensing model of Pega BPM is tricky, especially for first-time customers, so it's something that they could improve.

The technical support team for this solution could be faster in resolving tickets.

I've been using Pega BPM for five years.

We are satisfied with the stability of this solution.

We have been able to use Pega BPM in different lines of businesses for the past few years, so we find it scalable.

We faced some issues so we had to contact technical support. We raised the ticket and it was resolved. It took a week, but it was resolved.

We implemented Pega BPM with the help of a consultant.

This solution's licensing model needs to be improved.

It's a yearly subscription, but there are no extra costs apart from the standard licensing fee.

I'm using one of the latest versions of Pega BPM: version 8.

It was the IT side, with the help of a consultant, who handled the installation of this solution, so I didn't have much visibility into whether it was easy or complex. It was done over a period of seven to 15 days.

The number of end users using Pega BPM in our organization is 35 to 40.

Deployment of this solution did not take many people: just two people, but for maintenance, we have three people, so deployment and maintenance requires a total of five people. All of them are engineers.

We use Pega BPM almost on a daily basis. We currently don't have any plans of increasing its usage.

I'm recommending this solution to other people, particularly if it is a good use case for them.

Pega BPM is the first business process management software we were able to try. We had an old tool we were using, but it was not a BPM software. 

My rating for Pega BPM is eight out of ten.

Pega BPM is a business process management tool that can be used to build enterprise applications.

The solution is operating well overall.

I have been using Pega BPM for approximately two years.

They need to support the solution better, at this time the company does not have enough support.

The implementation is not complex.

I need people who understand this tool and they can implement it. I cannot rely on someone that implements it and leaves. They do not have enough people qualified in the market. If you are not able to operate it, improve it, or do enhancements changes yourself, it will be an issue.

The price is a bit expensive.

I rate Pega BPM a seven out of ten.

The most valuable feature is the ease of deployment.

We would like to have a better ability to customize PegaRULES.

In Pega, it is very important to have good overall system performance. As such, the performance should be improved.

Better automation would be helpful because I would like to see all of the manual intervention removed.

I have about five years of experience giving applications support for PegaRULES.

We cannot say that any application is fully stable, as it depends on the particular requirements. For example, if we have application automation then we need to make it scalable, but nothing is 100% perfect.

This is a scalable product. We have perhaps 50,000 users across our clients who use it.

I do not generally contact technical support. Instead, our core idea is to determine the issues and resolve them ourselves.

It is easy to install PegaRULES. There are no major issues because we have the proper guidelines for release and configuration. The length of time needed for deployment depends on the requirements for each client.

We have a complete in-house team that performs the implementation and deployment for our customers. This includes creating new rules and definitions, determining which policies are required, managing the system, giving support, and release management. 

We are planning to move our system to the cloud within the next six months, so this is something that we are preparing for.

The suitability of this solution depends on the organization, but in general, I definitely recommend PegaRULES. When assessing the appropriateness of this product for a client, I would first study their requirements.

I would rate this solution an eight out of ten.

We are using Pega for developing our workflow applications.

It's a good tool for workflow automation.

It's stable and secure.

In regards to the integration, more APIs may be required.

It needs more integration with other platforms.

I have been using Pega BPM for six months.

It is stable, and it is a distributed architecture.

We have approximately 1,000 users, but it can scale up to approximately 15,000.

It's a scalable product.

We have not contacted technical support.

Previously, we did not use another solution. It was all manually done.

The initial setup is straightforward, nothing complex.

It took two or three days to deploy. We are still new to the system.

We completed the implementation ourselves.

We have a complete team of administrators and application administrators who maintain this solution.

It's a user-based license where, as you scale the numbers of users, the price increases.

They also price base on the number of cases you have. 

They have varieties of pricing models.

Currently, we are working on the deployment models. 

We have not yet started on how to do automation of deployment. I think it's there, but we have not explored it yet.

We have in-house applications that we want to implement automation for. We will be using this software to automate those products.

I would recommend Pega BPM.

I would rate this solution a nine out of ten.

We use it for some insurance companies for underwriting.

The workflow designing and integration are the most valuable features. Also, the UI design was pretty easy. 

All the features that are related to case management are pretty outstanding.

It's called a local platform but on the other hand, it needs a lot of experience. It's not all that easy to click and plug and play. If you really want to use all the features out of this platform, you definitely need a lot of experience and a lot of training to get there.

Because the platform offers a lot of different features, it's rather complex and makes it very valuable for many different use cases, but what I would improve is that you can't tell all the people that it's a local platform, which suggests that it's for everybody, even for those people that do not have any clue about IT. They are using a lot of functionalities that try to help those developers and usually they make good jobs, but there are some situations where this automation will cause a lot of stress and trouble. This is something that creates more work at the end than if you just started from scratch. 

It depends on the use case but in general, it's stable. We have two use cases where we use a lot of different tasks and if you have more than 1,000 use cases then there seems to be some problems with the stability. It may depend on other features like load balancing and those kinds of things. 

It is definitely scalable.

Technical support is quite good if you don't have very special requests or defects. It depends mostly on your own code. But if it's on the general code that is provided by Pega, it's quite easy to set up a question to the Pega team and it's usually answered within a couple of hours, sometimes even faster. 

There's a lot of information that can be found in the Pega community which is quite helpful.

The initial setup is quite easy. If you use the cloud options, you get the full stack delivered and you do not have any hassle with setting up certain features or certain information. If you just install it on your local machine, it is also going to work pretty well. 

It's more complex if you set it up in a local environment on the local server, then you have to check a lot of different things and especially all the things that are related to securities.

I think the pricing reasonable. On the other hand, Pega has a clear focus on future companies. So, they say, "Okay, this is for our main customer focus," and this is, in my eyes, a bit of a pity because I think the technique and the software are really mature and could be very helpful for other companies as well that are not a main focus of them. 

My advice would be to have a focus on what the main purpose of the VPN platform is. Are you really looking for a VPN platform, something that is gathering all the VPN processes in the whole company, or is it just for reporting some processes like a customer process and connecting it to an SAP process? 

If you are planning to use Pega as your main platform, then it's a really good choice. On the other hand, if you have different software in your company like microservices or other big platforms like SAP, then you really should think if adding Pega as another big solid piece of software is really a good idea or if you just look if you can find other ways to integrate the other pieces of software for the purpose.

I would rate Pega BPM a nine out of ten.

I would like to have a lightweight version of it; something like Appian. In the very beginning, you just had Word and Excel, and you were fine with that. Now, you have a complete suite starting from SharePoint and Teams, etc, but you don't need all the features because you have a specific purpose and for this purpose, you need the best software. But nevertheless, you don't need, for example, all these RPA stuff, which is heavily promoted. These are all things that you just buy-in and are reflected in the price. It would be helpful if they offered a lighter version.