No more typing reviews! Try our Samantha, our new voice AI agent.

IBM Cloud Pak for Automation vs Temporal comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

IBM Cloud Pak for Automation
Ranking in Process Automation
38th
Average Rating
8.0
Reviews Sentiment
5.8
Number of Reviews
2
Ranking in other categories
Business Orchestration and Automation Technologies (28th)
Temporal
Ranking in Process Automation
3rd
Average Rating
8.6
Reviews Sentiment
6.8
Number of Reviews
18
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of July 2026, in the Process Automation category, the mindshare of IBM Cloud Pak for Automation is 1.3%, up from 0.5% compared to the previous year. The mindshare of Temporal is 3.8%, down from 7.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Process Automation Mindshare Distribution
ProductMindshare (%)
Temporal3.8%
IBM Cloud Pak for Automation1.3%
Other94.9%
Process Automation
 

Featured Reviews

SYEDMUJTABA - PeerSpot reviewer
Vice President - Digital Automation Services at Techvista Systems
Effectively handles parallel instances effectively
I find it quite straightforward, perhaps around 8.5 out of 10 in terms of ease. When we upgraded from the old version of IBM BPM to the new one within IBM Cloud Pak for Automation, we didn't encounter any major issues. There were some minor ones, but they were easy to overcome.The migration process was part of our deployment strategy. We had a plan to migrate two processes per week from on-premises to the cloud. The migration involved taking the instances and migrating them to the new environment. There is an inbuilt feature in IBM Cloud Pak for Automation that facilitates the migration process, although I personally haven't conducted it myself; it's managed by my team. Overall, the setup process was relatively smooth.
MP
Founder & CEO at Lanzar
Automation streamlines operations and improves time and cost efficiency
My overall experience with Temporal is rated between 8 to 9, mainly due to a learning curve that only senior developers can navigate effectively, which makes it a bit challenging for junior developers. We don't have any instances of on-premise, so I cannot comment on that because we are a first company, with all services deployed on cloud infrastructure. Most of the integration is through RPC or APIs, ensuring all our systems are in cohesion. We do state persistence to a Postgres instance, and we have modified it to our use case with better indexing. And for fault tolerance, we built a queue and an alerting mechanism that notifies us if any workflows fail after specific failure points so we can act upon it. On a scale of 1-10, I rate Temporal an 8.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"I believe two significant features of IBM Cloud Pak for Automation are the focus on SLA management and the capability to handle parallel instances effectively. Parallel instances, for instance, are valuable when dealing with a large number of users, enabling tasks to be performed concurrently for efficient system operation. The SLA aspect is crucial for tracking and ensuring timely completion of tasks. Additionally, the cloud compatibility of IBM BAW allows for seamless migration from on-premises to the cloud. This version also includes a business rule management system for storing and managing business rules effectively."
"What this product allows us to do is to move from on-prem instances where we are running independent instances of FileNet, Datacap, and ODM. It allows us to leverage container-based resiliency and availability modeling so that we have some visibility across the CP4BA ecosystem. We're now migrating all of our data to be in the Cloud Object Storage, and we can now use some of the features of Azure in terms of how we store and retrieve content for our members and our providers."
"Temporal provides visibility into workflow progress and analytics and supports scheduled tasks with customizable settings, making it very convenient."
"We like the fact that the whole process is durable, which is very useful to us."
"Temporal focus on developers rather than business users."
"The most valuable thing about Temporal is that we can create multiple and child workflows. We can segregate work as we want, which is good for work organization. It's also easy to maintain. We're trying to generate and fill PDF forms with custom data, including digital signatures. We call AWS and do all activities through Temporal, like calling and saving data in buckets. We do this because we have a lot of load, with multiple users requesting data. We have two types of users: admin and customer. The admin creates forms, and employees or customers fill them out. When admin gets a form, it's stored in Temporal."
"What I like best about the tool is that it's easy to install, especially since it uses JavaScript. It's also easy to set up with Docker, and the documentation is easy to understand."
"Temporal allows retryability for different workflows whenever they fail. It helps ensure idempotence and that things get done."
"When some jobs take a lot of time and fail midway, the solution’s retry feature automatically causes them to retry."
"What I like best about Temporal is its durable execution, which means you don't need to write many boilerplate code for critical pieces, especially for retries. It also has great observability and a nice dashboard to see issues without digging into logs. The interface for viewing activities is excellent, with good tracing that shows how long activities took and what ran, making it almost perfect for debugging."
 

Cons

"One of the challenges we're having is finding vendors who have experience in developing on the cloud. We can find developers on the old platform, but it is leading-edge technology. So, we are having some challenges, and IBM is assisting us to find vendor partners. To be able to leverage all the capabilities of the new platform, we have to upgrade our existing ecosystem of FileNet applications. Upgrading to the new platform while trying to modernize is always challenging because it is like you have a moving target."
"Upgrading to the new platform while trying to modernize is always challenging because it is like you have a moving target."
"I believe there is room for improvement in the user interface, particularly in the Process Portal that customers use to view and manage their tasks. The UI of the Process Portal needs enhancement. Additionally, in the next release, I would like to see improved compatibility with Angular, allowing for direct integration with front-end systems. It would be beneficial to have built-in GUI features based on Angular within the system, rather than developing separate applications externally. This, in turn, would provide a more seamless and enhanced front-end experience."
"Sometimes it scales kind of badly, but it depends on the process of our products."
"Temporal could be improved by making it more user-friendly for beginners and non-technical staff, ensuring easier integration and usability across different use cases."
"Temporal images aren’t FIPS compliant, and we have to be FIPS compliant."
"One issue is that we don't have enough resources in the community to get answers when we face problems. We once had a cross-cluster persistence issue, which we solved using different keys. I think Temporal is good right now, but I'm part of the community and will let you know if I think of any improvements."
"We previously faced issues with the solution's patch system."
"While the tool can be a bit daunting initially, especially if you're not used to async programming models, it's generally a pleasure. There's always room for improvement, though. I've noticed some limitations with the .NET SDK regarding dynamic workflows, but this might have been improved in recent versions. Overall, I think Temporal could be more open about implementing features in a more—.NET-friendly way, especially in how you add workers and clients."
"My overall experience with Temporal is rated between 8 to 9, mainly due to a learning curve that only senior developers can navigate effectively, which makes it a bit challenging for junior developers."
"Configuring workflows can be improved —the solution could offer more options, but it's not a must-have."
 

Pricing and Cost Advice

"IBM Cloud Pak for Automation is relatively expensive, especially considering it is designed for long-living processes, not for normal automation needs. On a scale of one to ten, I would rate the pricing at around 9. There are no additional costs beyond the standard licensing fees, but IBM has multiple pricing models that make it expensive in its own way. Different plans are available, but overall, the experience suggests it is a costly solution."
"Its cost is almost the same or comparable to what we pay with FileNet, but I'm not sure what we pay a year. A good part of CP4BA is the CPU-based licensing model. When we're dealing with 50,000 dentists, for example, if we were to use Salesforce, we would be hit with the licensing of 50,000 dentists, whereas when we build out in CP4BA, it is just based on our CPU usage, not on individual licenses."
"The tool is open source under the MIT license, so there are no hidden fees. You can freely use everything on their GitHub and Docker images."
"Temporal is open-source and free to use, which is great. We didn't have to pay for any premium features."
"It is worth the price."
"The savings weren't as big as we initially expected, but they were pretty great from a developer's perspective."
"Temporal is a free, open-source tool."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
902,988 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Wholesaler/Distributor
9%
Construction Company
9%
Government
7%
Financial Services Firm
27%
Computer Software Company
10%
Manufacturing Company
7%
Retailer
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise4
Large Enterprise6
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for Temporal?
In terms of pricing, Camunda is indeed costlier than Temporal. The cloud deployment costs differ, and while Camunda 7 can be cheaper due to its integrated setup, comparing latest versions between T...
What needs improvement with Temporal?
The only area for improvement in Temporal is the UI. I know it is a non-UI first product, but comparing Camunda versus Temporal UI, there is a difference. Moreover, n8n, being a no-code platform, i...
What is your primary use case for Temporal?
The main purposes for using Temporal are automation flows, especially financial automations and supply chain automations. Our company name is SR, we are a digital-first CPG brand making company, ma...
 

Overview

Find out what your peers are saying about IBM Cloud Pak for Automation vs. Temporal and other solutions. Updated: June 2026.
902,988 professionals have used our research since 2012.