Try our new research platform with insights from 80,000+ expert users

ActiveBatch by Redwood vs Nintex Process Platform 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
9th
Ranking in Workload Automation
8th
Average Rating
9.2
Reviews Sentiment
7.4
Number of Reviews
35
Ranking in other categories
Managed File Transfer (MFT) (11th)
Nintex Process Platform
Ranking in Process Automation
11th
Ranking in Workload Automation
13th
Average Rating
7.8
Reviews Sentiment
6.9
Number of Reviews
24
Ranking in other categories
Business Process Management (BPM) (13th)
 

Mindshare comparison

As of June 2025, in the Process Automation category, the mindshare of ActiveBatch by Redwood is 0.6%, down from 0.7% compared to the previous year. The mindshare of Nintex Process Platform is 1.8%, down from 3.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Process Automation
 

Featured Reviews

Shubham Bharti - PeerSpot reviewer
Flexible, easy to use, and offers good automation
Occasionally, I find myself contemplating if there is room for improvement in the user interface (UI), and envisioning that with certain enhancements. 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. New users might encounter a minor setback due to the absence of readily accessible training videos, which could have otherwise proven to be an invaluable resource in aiding their initial familiarization with the platform, potentially hindering their seamless onboarding process and delaying their ability to harness the software's full range of capabilities to its utmost potential.
Vitor Medeiros - PeerSpot reviewer
Offers capacity to integrate with external platforms but technically difficult
There is room for improvement in the user experience in the forms. When we need to develop the forms, we don't have much customization, and I think we need more flexibility there. It's technically difficult, but it would be great to be able to develop our own code and integrate it into the platform. We could then run our own code for specific actions and requests or even develop a page or form. So, if I can ask Nintex for something, it would be a way to integrate our own code for specific actions. When it comes to integration, it could have more options for custom requests.

Quotes from Members

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

Pros

"We use the main job-scheduling feature. It's the only thing we use in the tool. That's the reason we are using the tool: to reduce costs by replacing manual tasks with automated tasks and to perform regular, repetitive tasks in a more reliable way."
"Since we are no longer waiting for an operator to see that a job is finished, we have changed our daily cycle from running in eight hours down to about five. We had a third shift-operator retire and that position was never refilled."
"The most valuable feature is its stability. We've only had very minor issues and generally they have happened because someone has applied a patch on a Windows operating system and it has caused some grief. We've actually been able to resolve those issues quite quickly with ActiveBatch. In all the time that I've had use of ActiveBatch, it hasn't failed completely once. Uptime is almost 100 percent."
"We leverage the solution's native integrations regularly. We have to get files from a remote server outside the organization, and even send things outside the organization. We use a lot of its file manipulation and SFTP functionality for contacting remote servers."
"There are hundreds of pre-built steps."
"It is very useful in sending confidential files through FPP servers."
"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."
"As far as centralization goes it's nice because we can see all these processes that are tied to this larger process. The commissions, FTP processing, the reporting, the file moves to the business users — all that is right there. It's very easy to read. It's easy to tie it together, visually, and see where each of these steps fits into the bigger picture."
"It provides data accuracy with fewer failures."
"It leverages the out-of-the-box SharePoint back-end. This means that you don’t need to install or deploy additional infrastructure to support Nintex Workflow, unlike some of its competitors."
"The strength of this solution lies in its connectors and the accessibility of an open API. The presence of an open API allows users to create custom connectors if necessary, provided there is access to the source API documentation. Additionally, the platform features a straightforward yet highly effective forms tool. This tool not only seamlessly integrates with the workflow functionality but also facilitates the transmission of information to the document generation tool. This comprehensive integration is particularly noteworthy when compared to alternatives such as Oracle, which tends to rely on more complex and separate logic for similar functionalities. A key strength of Nintex lies in its user-centric approach to help documentation. The materials are designed to be easily understood, avoiding complex terminology. In cases where technical terms are used, they are linked to articles for further clarification. This contrasts with platforms like Microsoft and Oracle, which may employ technical jargon without clear explanations. Nintex further supports its users through a robust online community, fostering collaboration and shared insights. Additionally, Nintex University offers online training across all applications, following a role-based structure. Unlike some other platforms, Nintex's training is thoughtfully broken down into shorter courses, focused on specific roles. This approach ensures that users can efficiently access the information they need without navigating through extensive and potentially irrelevant content, as may be the case with Oracle's training structure."
"It's easy to configure your set of rules to make the form controls work perfectly, removing manual work and making processes seamless."
"I like the feature of getting an email for a workflow error, then I do not have to go through every instance."
"It creates workflows to handle business processes. It allows us to route approvals to users without human intervention."
"Provides the ability to automate SharePoint processes (building sites, lists, updating content). You can also automate document and content processes, onboarding and offboarding, and general IT and HR solutions."
"The workflow engine of K2 is its main strength. Its workflow engine is probably one of the best, and that's the reason why Nintex bought K2. It can clearly handle any complex process or scenario. K2 is almost low-code. It is a no-code or low-code solution. You don't have to read a whole lot of code. It is pretty much GUI based. Their support is also excellent. The biggest advantage of K2 is SmartObjects, which allow you to separate the data from the application. It is a standalone application that allows you to build a data source from different places, which a lot of other applications also do. It is called SmartObjects technology, which is pretty powerful. If I have data from different applications, such as JD and ServiceNow, I can just create a SmartObject based on a data source and use it. I have some forms that have six, seven, or eight applications in a single form with data from different places."
 

Cons

"The reporting needs improvement. There is a real need for the ability to generate audit reports on the fly. It needs to be a lot easier than what I can do right now. This is a major item for me."
"One thing I've noticed is that navigation can be difficult unless you are familiar with the structure that we have in place. If someone else had to look at our ActiveBatch console and find a job, they might not know where to find it."
"The documentation is very limited, and it can be improved."
"Setting up the software was hard."
"Some of the advanced features in the user interface are a bit confusing even after referring to the documents."
"They could provide an easier installation guide or technical support to the organizations during the installation process."
"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."
"There is this back and forth, where ActiveBatch says, "Your Oracle people should be dealing with this," and Oracle people say, "No, we don't know anything about ActiveBatch." Then, it all falls back on me as to what happens. Nobody is taking responsibility. This is the biggest failing for ActiveBatch."
"Converting a document from PDF to MS Word, or vice versa, needs to be improved."
"The security features for this solution need to be improved."
"Nintex is still at the starting point of integrating with AI. It has integrated with a very small piece of artificial intelligence., like only integrated with the Google Cloud. There is a benefit, like a no-code and low-code solution. But, again, if you are a developer, especially if you are a hardcore developer, you are using your code knowledge, its skills, and all. And, suddenly, you are moving into the low-code solution, and then you will feel, like, so many things you can't achieve with the low-code solution."
"There is room for improvement in the user experience in the forms."
"The management server and the admin page where you can manage processes need improvement."
"​Bring all features available from the on-premise product into the cloud version and the workflow error reporting.​"
"At times, issues arise in certain scenarios. In such cases, the versioning can become quite difficult. There may be no other way but to restart the entire process or rectify it at that point."
"The solution does not integrate with many platforms."
 

Pricing and Cost Advice

"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."
"The price was fairly in line with other automation tools. I don't think it's exorbitantly expensive, relatively speaking."
"If you compare ActiveBatch licensing to Control-M, you're looking at $50,000 as opposed to millions."
"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."
"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."
"Currently, we are paying approximately $7,000 yearly, which includes support."
"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."
"It allows for lower operational overhead."
"The annual support costs are expensive."
"Nintex Workflow is more expensive than Microsoft's native products, but it is still considered moderately priced when compared to higher-end products such as K2."
"Prices for licenses of K2 are high."
"For the initial hundred users, the cost is $21,000 per year, which I find too high."
"This solution is affordable and is cheaper than most alternatives on the market. We have a standard cloud license that costs about 20k per year."
"Offering a licensing model that allows for multiple small workflows would be a huge improvement to an already great platform."
"There is an initial fee when purchasing and a fee for maintenance afterward."
"It's more suited for enterprise level, not for small or medium-sized businesses (SMBs)."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
859,129 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
Computer Software Company
9%
Manufacturing Company
8%
Insurance Company
8%
Computer Software Company
21%
Financial Services Firm
18%
Educational Organization
6%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about ActiveBatch Workload Automation?
Managing the workload and monitoring the tasks were very difficult with manual interventions. Now, by using ActiveBatch, the process is automated and it runs tasks on a scheduled basis.
What is your experience regarding pricing and costs for ActiveBatch Workload Automation?
I'd advise users to start by knowing what the actual requirement is and thoroughly assess the automation needs. New users should take advantage of the demos and trial versions so they get an idea o...
What needs improvement with ActiveBatch Workload Automation?
After upgrades we are facing a few issues and errors triggered, so focusing on this would be appreciated. Some of the advanced features in the user interface are a bit confusing even after referrin...
What do you like most about K2?
The latest version of Nintex has many features. We have a clear roadmap and the necessary application to integrate it into our platform.
What is your experience regarding pricing and costs for K2?
Nintex Process Platform is expensive. Prices relate to both features and the professional services necessary due to our lack of an implementation team.
What needs improvement with K2?
The user interface in Nintex needs improvement. It is not very intuitive and requires changes. Additionally, the deployment process should be easier.
 

Also Known As

ActiveBatch
K2 blackpearl, K2 Five, Nintex Workflow
 

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
SEA Corp, Omnicom Group, Verizon, STIHL
Find out what your peers are saying about ActiveBatch by Redwood vs. Nintex Process Platform and other solutions. Updated: May 2025.
859,129 professionals have used our research since 2012.