Pega Platform Reviews

We are developing campaigns and business solutions on top of Pega. It is a part of the campaign management solution that we have. We are also using it for the core business. We are offering personalized content, personalized product, and personalized information for each of our customers. Pega is one of the main products for us for pricing, catalog, and content. It is being used for everything.

I have a lot of experience in this kind of industry, and Pega is one of the best solutions in terms of performance, capabilities, and the way we develop. 

It should have integration with non-relational databases. A lot of databases are non-relational, and as a company, we are planning to move to NoSQL or open-source databases. It would be good if we are able to install and use Pega on a NoSQL database. 

They can also try to tailor or organize the company a bit differently and go more towards the microservice concept.

I would like Pega to develop machine learning and intelligent AI algorithms. They have a good foundation in terms of the model and the stuff that we are using for some customers, and it will be good to onboard as many machine learning algorithms as possible.

I have been using this solution for a couple of years.

It is one of the most stable solutions, but you need professional expertise. If you are working in a professional way, you won't have issues. If you install it on top of any provider as a database and you are not able to tune the database, you will have issues. Every product has bugs, but it is a more stable one.

We have 25 to 30 customers who use this solution.

Their technical support is fine. There is always room for improvement, but overall, it is fine.

I have used different products and shifted to Pega. In the past ten years, I developed an in-house solution, and I also hired a company to develop it for me, but that was not enough. Now I am relying on Pega in Google Cloud, and it is running my business strategy and everything else. It is one of the best solutions in this category. I can't even compare it with other products. Based on Gartner's ratings, Pega is one of the top ones.

Its installation is straightforward. I don't see any big issue. We are using it on Google Cloud VMs. We are not using Pega container, but I know another company that is using it fully in a container.

For its deployment and maintenance, you need highly skilled people.

We mostly have a yearly license. 

I would recommend this solution. I have been recommending it to different customers across Europe. It is a professional product, but you should know what you are doing. If you don't know what you are doing, you might think it does nothing, but if you are mature enough to understand the power and potential of Pega, you can do magic with it. You should have the know-how, and you should know a customer's expectations. 

One of the reasons why some customers are getting a lot of success is because we have Pega and Data Lake or big data platforms close to each other. Data Science runs the algorithm on the Data Lake, and we propagate the data and the segment to Pega. This way the customer gets a high value. They are doing a great business because they have the potential data, and they can combine and build campaigns and segment customers on an individual basis. After that, your big data is in real-time, and you have real-time notifications. You are doing everything in real-time.

I would rate Pega BPM a nine out of ten.

We primarily use the solution anywhere we have to manage processes. I have a large portfolio of clients in financial, health care, life sciences, etc., and I use the solution for all of them.

Pega is currently number one in BPM and case management solutions, according to Gartner and Forrester. I like that it’s mostly a no-code platform. It’s also more of an enterprise-level solution. It looks like a front end stack. There are dozens of applications that are just moored to each other. However, Pega feels like one solution.

The interface is quite simple and easy to use, even for beginners.

Pega currently is trying to add chatbots to their systems, and it's still quite immature. This part definitely needs to be improved. The RPA also needs improvement. Pega has its own RPA, via an acquisition a couple of years ago. They bought OpenSpan and tried to rewrite it to Pega's platform. It still has some gaps. For example, they have no machine learning. If they want to be more mature in the market, they probably need to consider working on improving that.

The solution is stable across all deployment models.

It's very simple to scale the solution, especially if it is on the cloud. It's your own environment. You can just make your own limitations as to how fast you want to create your own new environments. Right now, we are handling 20,000 users.

The initial setup is quite simple. How long deployment takes depends on what you want to implement. It can be as little as 50 minutes if it's something very easy. It's like moving bricks. You are not typing any code, rather you are creating processes. When you're developing it, the length of time needed depends on how many bricks or processes you have to move, or create, so to speak.

In terms of how many people you need to maintain the solution, It depends on what type of support was chosen. It can be your own maintenance, or it can be maintenance from other suppliers or the vendor. It also depends on the number of applications you have as well.

We are using both public and private cloud and on-premises deployment solutions. We're using product versions seven and eight and have previously used product version six.

We’re a Pega partner.

I would rate the solution ten out of ten.

Fast prototyping.

Nothing compares with custom development.

• UX
• Business specific functionality

Three years.

Yes. Product failed to start periodically. No tolerance to DB outages.

We did not have significant load, but one physical server instance was able to serve around 100 concurrent users.

Four out of 10. They try to push all issues to the implementation team.

Customer decision.

Straightforward.

Licensing is expensive. You need to wisely select between per user and per case.

Appian BPM and Activiti BPM.

Have a strong skilled architect.

Our primary use case for this solution is for case management systems.

This product makes it easier to connect to multiple applications because integration through API or web services is very easy. That is one thing that has helped. The development time is very quick.

The most valuable features are case management and integration services.

The unit testing needs to improve, as well as the user interface.

In coming releases, I would like to see something in Artificial Intelligence (AI) and Machine Learning (ML).

This solution is quite stable. We deploy applications every month, generally to production, so we see that the product is quite stable, with no complexities. Overall, we're happy with the stability.

The scalability is good. In some areas, we had some trouble, but I think it was the way it was designed and not the product itself. So, we feel that it is good.

The technical support is quite good. They come back very soon, so we're happy with the support.

We did not use another solution prior to this one, so we started with Pega.

The initial setup for this solution is straightforward and not very complex.

The time for deployment depends on the complexity of the application.

We handled the implementation in-house and have people with experience in Pega.

I cannot share the financial details, but what I can see is that the users are happy because they get the solutions faster. That, for me, is a big benefit because I can show my product to the customer quicker than with any other solution. It makes me more efficient.

The licensing fees are based on the number of users.

I don't think that we evaluated other solutions. We were happy with what the tool was offering and chose it.

This product is pretty easy to work with. Sometimes you need experts, and it can be difficult to find Pega experts. Otherwise, it's a good tool to work with.

I would rate this solution an eight out of ten.

The workflows are the most valuable features, particularly for us, because we were attempting to automate processes by utilizing workflows to provide a hands-off comparison between the bot and the human.

Also, the out-of-the-box reporting, visibility, and dashboards are extremely useful. 

There was a lot of room for improvement on the RPA front because the product was still in its journey for more than one year. The product was still in its early stages of development. We spoke with the Pega team and provided our feedback.

On the BPM front, I believe it is pretty standard and an industry leader. 

We have experienced a few technical challenges, particularly triggering the workflow through file drops and accessing files. Those difficulties are more of a cloud versus on-premises issue because everything was on the cloud, and they were unable to retrieve files from on-premises folders. As a result, we had to resort to workarounds.

I believe they could work on more integration of their RPA and BPM so that it becomes seamless for anyone, and then it becomes easier for a human versus machine interaction using the same BPM. They said at the time that it's on their roadmap and should be coming soon if it hasn't already. But those are the things that, in my opinion, would make a better BPM, where it would function as an enterprise orchestration layer, collaborating with humans and bots in the same way and delivering the business process.

We completed a couple of BPM projects using Pega BPM.

I have been working with Pega BPM on and off for the last two years, and I have completed two BPM implementations in the last three.

It's a scalable product. There are no challenges with the scalability of Pega BPM.

Technical support was good. Especially for us, their product team was with us, as was their support team, and all of these workarounds were only possible with their assistance.

I worked on Newgen BPM two years ago.

We work mostly with BPM but we did a PoC on RPA. The RPA was unable to work.

The initial setup is simple because it is in the cloud. We haven't spent much time setting it up, it was up and running for a few weeks.

In terms of business flows, our implementations were not overly complex. We were able to launch it in an Agile mode, and we were able to deliver, in two or three sprints spanning four months. Every four to five weeks, we were able to release small flows to enable certain business functionality.

Pricing is a little on the high side. One of the challenges where a certain lower level of cases was unable to justify the cost. If your process is not that complex, and it is very simple, then the implementation timeline is obviously short, but licensing becomes a little costly, and it sometimes does not cross the business use case. 

The benefits you receive are not worth the price. 

They should have a solid foundation of business processes in place before embarking on this journey. If the case is small or the process is not complex, they should use a smaller and simpler BPMS. The primary reason is the cost. However, if they are considering it at the enterprise level or for a more complicated process, Pega is, in my opinion, the best option.

I would rate Pega BPM an eight out of ten.

It is a multi-tenant offering for developing applications. We have its latest version.

Generically, at the moment, it can take things that were non-functioning processes and crossing stovepipes and make them function.

I have found a lot of features valuable. The ability to define processes, build reports, and get insights or analytics on data is most valuable. It is a powerful platform.

The way the IDE works with the chatbox and the taxonomy imports could be a little smoother.

There should be quicker approvals for CDH. It is a bureaucratic approval process to be able to get those particular licenses.

I have been using this solution for two and a half years.

It is stable. Like everything, it depends on the quality of the knowledge of the people who are using it.

I like it. It allows for a lot of multi-tenancy.

In terms of usage, it is in its initial use areas, but it is rapidly being adopted.

I have interacted with them. Our overall experience is positive. They have some good folks there. Occasionally, their system doesn't realize the urgency of a problem if the problem isn't in production. If your problem isn't currently causing production failures, the turnaround time can be slower than expected.

We don't use Pega exclusively. We've got other stuff in there. There are some things for which one solution is good, and for another set of things, another one fits very well.  It just depends on the application, the tendency, and the purpose.

We brought in experts. Our experience with them was positive.

The advice that I would give is that when spinning, think about if you're setting up a private one. You should also think about your tenant or your organizational control structure for multi-tenancy so that you can have a mix of licenses for tenants while not overly complicating and having to maintain tons of different work control layers. 

Before you start up an app, take a look, run the wizards, and see what you can reuse from the structure. Its wizards are very good to use when starting up. There are a lot of powerful data models and workflows that you can use as starting points. You can also simply reuse and rename them. 

Whenever you're building things, work with your team regularly on the data model supporting it so that you have a lot of reusable capability. So, you enhance it. It is worth the time to meet weekly with your team over your data architecture.

I would rate Pega BPM an eight out of 10. There is a bit of a learning curve, but it is extremely powerful. When you get into it, then you realize that it is far more powerful.

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.

The marketing automation is very good. The solution is very convenient to use.

The solution would benefit from more integration capabilities.

There are some tools within the solution that are difficult to use.

I've been using the solution for 1.5 years.

The stability has been good. We haven't had any issues.

The scalability of the solution is very good.

We've never contacted technical support.

I've previously worked with Bizagi, and I find this solution has more features in comparison.

The initial setup is straightforward. Deployment typically takes a few days.

We handled the implementation ourselves.

We use the cloud deployment model.

We've been using the solution for a long time and it's been very good.

I'd rate the solution eight out of ten. There are some technical tools that are hard to use.