We performed a comparison between Pega BPM and vCenter Orchestrator based on real PeerSpot user reviews.
Find out in this report how the two Process Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
"The technical support of Pega BPM is very good."
"Application development is very rapid. A lot of code gets reused while building the applications, which is something we highly appreciate."
"Pega is a local platform that has evolved from a BPM perspective. This allows teams using this solution to address complexities without having deep knowledge in a specific development area."
"The initial setup is pretty straightforward."
"It is quite configurable, which is the most exciting feature. We can easily configure it as per our needs."
"It is a stable product."
"Can do a lot of things with minimum time and cost."
"The solution has very helpful technical support."
"The solution was easy to install."
"The most crucial feature of vCenter is its scalability. We can use it to expand our network, so we don't have to report our client devices. The network configuration features are also helpful because we can migrate entire networks."
"If I need to do DR, VMware can enable me to use vMotion, which requires use of vCenter. You cannot do vMotion without vCenter. We do a lot of automation, orchestration, and simplification for that purpose."
"It is very stable. I have been using vCenter Orchestrator from version three now to six plus."
"The product's integration is good, it works well with other programs and solutions."
"The solution is pretty stable and reliable."
"vCenter Orchestrator is very reliable and stable."
"We have excellent technical support. They have always been helpful when we have needed them."
"The main problem with Pega is that it is quite complex, so it is very difficult for the developer to learn."
"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."
"One of the areas of this solution that could be improved would be to advance the low code features of the application itself. We would also like to use the same platform to build any application, even if it is not necessarily defined as a functionality needed by a BPM."
"Reporting is not so clear and not so great. We really struggle to get the right reporting. When we need reporting based on the content of the tickets, we are not able to get it. The MIS reporting is not great. That's one of the reasons why we are switching to ServiceNow. Its compatibility with the higher versions of Internet Explorer should be improved. It really works well in Mozilla Firefox or any other browser, but when it comes to Microsoft Edge or Internet Explorer, sometimes, the layout gets disturbed. The positioning of the buttons changes, and there is some distortion in the layout. I am not sure whether it is our configuration problem or Pega's, but when it is working in Mozilla Firefox, it should also work in Microsoft Edge or Internet Explorer."
"Pega BPM could be improved by including token-based authentication and extending its integration options."
"They need to support the solution better, at this time the company does not have enough support."
"We have experienced a few technical challenges, particularly triggering the workflow through file drops and accessing files."
"I believe they simplify the application development. It is still complex. The learning is not easy, it takes time compared to other products on the market."
"I would like to have an interface that can manage both on-premises and cloud solutions from a single console, where we can easily manage the resources that are being used or at least applications. Whereby clicking here and there from on-premises to cloud, or cloud to on-premises, depending on the requirements. If that can be accomplished, it will be extremely beneficial."
"VMware tools would benefit from more automation. When installing our devices and servers, we often need to install the VMware tools manually. This process should be automated during the VM installation process."
"I believe a transparent view and better terms of condition between Oracle and vCenter Orchestrator would be helpful."
"There can be compatibility issues."
"I did not do the initial setup. However, it was complex at the beginning."
"Many times, customers' licenses are not used because the client is not aware of the features and the product benefits. When somebody is buying a product, they just do a default configuration."
"I would like to see better performance."
"The price of this product is high and could be improved."
Pega BPM is ranked 3rd in Process Automation with 29 reviews while vCenter Orchestrator is ranked 8th in Process Automation with 8 reviews. Pega BPM is rated 8.2, while vCenter Orchestrator is rated 9.2. The top reviewer of Pega BPM writes "Excellent machine learning, automation intelligence, DevOps for larger organizations". On the other hand, the top reviewer of vCenter Orchestrator writes "Enables us to do administration on a centralized layer when using multiple VMware ESX servers". Pega BPM is most compared with Camunda Platform, ServiceNow, Appian, Microsoft Power Apps and IBM BPM, whereas vCenter Orchestrator is most compared with VMware Aria Automation, VMware Aria Operations, vCloud Director, ServiceNow Orchestration and Microsoft System Center Orchestrator. See our Pega BPM vs. vCenter Orchestrator report.
See our list of best Process Automation vendors.
We monitor all Process Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
