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

ActiveBatch by Redwood vs IBM Cloud Pak for Automation 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

ActiveBatch by Redwood
Ranking in Process Automation
12th
Average Rating
9.0
Reviews Sentiment
7.2
Number of Reviews
41
Ranking in other categories
Managed File Transfer (MFT) (10th), Workload Automation (8th)
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 (30th)
 

Mindshare comparison

As of August 2026, in the Process Automation category, the mindshare of ActiveBatch by Redwood is 1.2%, up from 0.8% compared to the previous year. The mindshare of IBM Cloud Pak for Automation is 1.3%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Process Automation Mindshare Distribution
ProductMindshare (%)
ActiveBatch by Redwood1.2%
IBM Cloud Pak for Automation1.3%
Other97.5%
Process Automation
 

Featured Reviews

Sai  - PeerSpot reviewer
Ai/Data Analyst at CSD
Automation has streamlined complex data workflows and now saves time on recurring reporting
To improve ActiveBatch by Redwood, the UI could be more modern and intuitive, and another thing that comes to mind is that it can feel overwhelming when workflows become large and complex. Troubleshooting can take extra time when there are multiple dependencies, jobs, and integrations running together. Better visualization of workflow relationships and easier debugging would really help. I would also appreciate seeing more simplified onboarding and documentation for newer users, as there is a learning curve at the beginning. Another improvement area could be smarter analytics or AI-driven recommendations, such as proactively identifying workflow bottlenecks, failed job patterns, or optimization suggestions instead of relying mostly on manual monitoring. From an operational perspective, faster configuration for integrations and cloud-based workflows would make implementation smoother, especially in environments working heavily with APIs and data pipelines. I have covered the main points regarding needed improvements. Overall, the platform is very capable and reliable for automation and workflow scheduling, especially in data-heavy environments. Most of the improvements I want are around making it easier for day-to-day use, such as a more intuitive UI, simpler troubleshooting for complex workflows, better onboarding for newer users, and more intelligent monitoring or optimization insights. The core functionality is strong, and the biggest opportunity is improving the overall user experience and simplifying operational management.
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.

Quotes from Members

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

Pros

"One of the most valuable features is the job templates. If we need to create an FTP job, we just drag over the FTP template and fill out the requirements using the variables that ActiveBatch uses. And that makes it reusable. We can create a job once but use it for many different clients."
"The automation feature is a very valuable feature as the associates do not have to worry about performing repetitive tasks (i.e. endpoint security scans on a daily basis) that would take several hours to complete on a daily basis."
"ActiveBatch helped us automate and schedule routine tasks such as data backups, file transfers, database updates, and report generation, which frees IT staff to focus on other studies."
"We look at different products and this is definitely a very good one."
"It is very useful in sending confidential files through FPP servers."
"I like ActiveBatch Workload Automation's licensing model because they're not holding you down on an agentless model or agent model, where every server needs to have an agent."
"From a scheduling point of view, it is pretty good."
"The nice thing about ActiveBatch is once we have created a specific job that can be easily be replicated to another job, then minimal changes will have to be made. This makes things nice. Reduction of coding is substantial in a lot of cases. The replication of one job to another is just doing a few minor tweaks and rolling it into production. This decreases our development costs substantially."
"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."
"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."
 

Cons

"Some improvements can be made to the user interface."
"To improve ActiveBatch by Redwood, the UI could be more modern and intuitive, and another thing that comes to mind is that it can feel overwhelming when workflows become large and complex."
"An area for improvement in ActiveBatch Workload Automation is its interface or GUI. It could be a little better. There isn't any additional feature I'd like to see in the tool, except for the GUI, everything looks good."
"The UI could potentially offer a more refined and user-friendly experience, fostering smoother interactions and facilitating easier navigation for users engaging with the application."
"I can't get the cleaning up of logs to work consistently."
"There are some issues with this version and finding the jobs that it ran. If you're looking at 1,000 different jobs, it shows based on the execution time, not necessarily the run time. So, if there was a constraint waiting, you may be looking for it in the wrong time frame. Plus, with thousands of jobs showing up and the way it pages output jobs, sometimes you end up with multiple pages on the screen, then you have to go through to find the specific job you're looking for. On the opposite side, you can limit the daily activity screen to show only jobs that failed or jobs currently running, which will shrink that back down. However, we have operators who are looking at the whole nightly cycle to make sure everything is there and make sure nothing got blocked or was waiting. Sometimes, they have a hard time finding every item within the list."
"The technical support was difficult if you wanted to escalate the issue, it takes a little bit longer to escalate."
"There are some issues with this version and finding the jobs that it ran. If you're looking at 1,000 different jobs, it shows based on the execution time, not necessarily the run time."
"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."
"Upgrading to the new platform while trying to modernize is always challenging because it is like you have a moving target."
"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."
 

Pricing and Cost Advice

"I like ActiveBatch Workload Automation's licensing model because they're not holding you down on an agentless model or agent model, where every server needs to have an agent. That's the main selling point of the solution and I hope they stay that way."
"If you compare ActiveBatch licensing to Control-M, you're looking at $50,000 as opposed to millions."
"ActiveBatch is currently redesigning themselves. In the past, they were a low cost solution for automation. They had a nice tool that was very inexpensive. With their five-year plan, they will be more enhancement-driven, so they're trying to improve their software, customer service, and the way that their customers get information from them. In doing that, they're raising the price of their base system. They changed from one pricing model to another, which has caused some friction between ActiveBatch and us. We're working through that right now with them. That's one of the reasons why we're why we were evaluating other software packages."
"It allows for lower operational overhead."
"I don't think we've ever had a problem with the pricing or licensing. Even the maintenance fees are very much in line. They are not excessive. I think for the support that you get, you get a good value for your money. It's the best value on the market."
"Currently, we are paying approximately $7,000 yearly, which includes support."
"The pricing was fair. There are additional costs for the plugins. We have the standard licensing fees for different pieces, then we have the plugins which were add-ons. However, we expected that."
"The price was fairly in line with other automation tools. I don't think it's exorbitantly expensive, relatively speaking."
"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."
"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."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Construction Company
10%
Outsourcing Company
9%
Manufacturing Company
6%
Construction Company
12%
Outsourcing Company
10%
Financial Services Firm
8%
Wholesaler/Distributor
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business12
Midsize Enterprise13
Large Enterprise52
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for ActiveBatch Workload Automation?
I was not directly involved in the pricing, setup cost, and licensing decisions for ActiveBatch by Redwood, so my experience is from the user and workflow side rather than procurement. However, bas...
What needs improvement with ActiveBatch Workload Automation?
ActiveBatch by Redwood could be improved with a more modern and intuitive user interface, faster performance for very large workflows, and expanded built-in integrations with newer cloud and DevOps...
What is your primary use case for ActiveBatch Workload Automation?
My main use case for ActiveBatch by Redwood is enterprise workload automation, job scheduling, and orchestrating business processes across applications, servers, and cloud environments. For example...
Ask a question
Earn 20 points
 

Also Known As

ActiveBatch
No data available
 

Overview

 

Sample Customers

Informatica, D&H, ACES, PrimeSource, Sub-Zero Group, SThree, Lamar Advertising, Subway, Xcel Energy, Ignite Technologies, Whataburger, Jyske Bank, Omaha Children's Hospital
Information Not Available
Find out what your peers are saying about ActiveBatch by Redwood vs. IBM Cloud Pak for Automation and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.