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

ActiveBatch by Redwood vs ServiceNow Orchestration 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
16th
Average Rating
9.0
Reviews Sentiment
7.3
Number of Reviews
39
Ranking in other categories
Managed File Transfer (MFT) (10th), Workload Automation (9th)
ServiceNow Orchestration
Ranking in Process Automation
12th
Average Rating
8.2
Reviews Sentiment
6.6
Number of Reviews
16
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Process Automation category, the mindshare of ActiveBatch by Redwood is 1.2%, up from 0.6% compared to the previous year. The mindshare of ServiceNow Orchestration is 2.5%, down from 4.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Process Automation Mindshare Distribution
ProductMindshare (%)
ServiceNow Orchestration2.5%
ActiveBatch by Redwood1.2%
Other96.3%
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.
Claude-Yameogo - PeerSpot reviewer
Consultant at a comms service provider with 1,001-5,000 employees
Has helped orchestrate processes and integrate workflows across cloud environments
I recommend ServiceNow Orchestration for larger companies because they have the capability to manage complex environments where it performs better. I promote low-code solutions for these implementations. I don't currently have an idea regarding the pre-built integrations of ServiceNow Orchestration, but I plan to check my area to determine what added value it can bring. I would rate this solution a nine overall.

Quotes from Members

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

Pros

"ActiveBatch has reduced work by providing automated workflows across several different applications."
"It can connect to a number of third-party/legacy systems."
"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."
"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."
"There are hundreds of pre-built steps."
"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."
"By implementing a sophisticated scheduling mechanism, the system allows for the precise triggering of jobs at user-selected frequencies, enabling a seamless and automated execution of tasks according to specified time intervals."
"I found ActiveBatch Workload Automation to be a very good scheduling tool, and what I like best about it is that it has very less downtime when managing many complex scheduling workflows, so I'm very impressed with ActiveBatch Workload Automation."
"The interface of the solution is very user friendly and it is easily accessible via a simple URL. This makes it easier to complete the UI based tasks but using other features require expertise in languages like Java. But along with that, there are limitation in terms of network connectivity testing and administrator faces regular challenges in conducting connectivity tests due to these limitations."
"Provisioning of new systems is among the most impactful features for automating complex workflows with ServiceNow Orchestration."
"I would definitely recommend Orchestration if you're already on the ServiceNow platform."
"The automation ServiceNow has provided saves us a lot of time and resources."
"I use it to orchestrate processes and integration features to gather and update data during specified timeframes or exchange data in real-time when changes occur based on certain criteria."
"It's scalable."
"The product has a flexible interface for development."
"Employee onboarding, de-boarding, and other service-provision features make the process easier and it saves us a lot of time."
 

Cons

"It could be easier to provide dashboards on how many jobs are running at the same time; more monitoring."
"The monitoring dashboard could have been more user-friendly so that in the monitoring dashboard itself we can see the total number of jobs created in the system and how many were currently active/scheduled/chained."
"The interface is not that user-friendly and is a little tough to navigate."
"Some improvements can be made to the user interface."
"One way ActiveBatch by Redwood can be improved is through a more intuitive user interface for new users."
"Between version 10 and version 12 there was a change. In version 10, they had each object in its own folder. But on the back end, they saw it at the root level. So when we moved over to version 12, everything was in the same area mixed together. It was incredibly difficult and we actually had to create our own folders and move those objects—like schedules, jobs, user accounts—and manually put those into folders, whereas the previous version already had it."
"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."
"We currently face issues with the web console of ActiveBatch by Redwood. When users operate through an RDP session, every user has their own ActiveBatch by Redwood application. However, on the web console, users encounter daily activity issues where the job instances do not appear or update correctly, and they cannot view the latest logs."
"The flow rate for releases and updates is very, very slow and does not meet customers' objectives for scalability."
"The third-party integrations are challenging when the tools are not from ServiceNow partners. This presents issues when integrating solutions from other vendors."
"The only challenge I see is it requires a lot of technical expertise to implement these tools and modules and all those things."
"It is a highly complex platform to work on."
"The connectors need to be updated because certain connectors for third-party tools are not up to date, and our customers are having problems synchronizing data with some of these tools."
"We have found some gaps in integration because all of our customers require niche tools."
"The deployment requires awareness among the project staff."
"There is still room for more integrations. Or, it would be nice to bundle multiple products together rather than selling everything as a model as that turns out to be a bit costly."
 

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."
"Currently, we are paying approximately $7,000 yearly, which includes support."
"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 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."
"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."
"It allows for lower operational overhead."
"Pricing is custom to every customer."
"The solution is costly and orchestrations are very expensive."
"In terms of price, this solution is at the higher end of what you'll find."
"ServiceNow doesn't give a clear cost indication. They have different contracts with different organizations and it's all about negotiation, so you don't know how they are doing at the cost level."
"It is quite expensive because we've had some customers come back and say it's quite pricey because in order for them to go ahead with Orchestration, they must have already been paying for Discovery, service mapping, and a few other things."
"It is not very expensive."
"The cost of the solution is based on the number of plugins, conductors and integrations used and is charged annually. The licensing cause has been increasing gradually which makes it difficult to access. Initially offer free features but over the time the charges rise which make it an expensive solution with limited features. Along with that, the integration issues persist and require additional middle where and internet connectivity for effective usage."
"This is an expensive product, but it is the best in the market considering the features and lack of competitors."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
900,644 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Construction Company
9%
Performing Arts
6%
Manufacturing Company
6%
Financial Services Firm
22%
Manufacturing Company
9%
Comms Service Provider
7%
Insurance Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise13
Large Enterprise49
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise4
Large Enterprise9
 

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?
One way ActiveBatch by Redwood can be improved is through a more intuitive user interface for new users. I rate ActiveBatch by Redwood an eight out of ten because it is powerful, but a perfect scor...
What is your primary use case for ActiveBatch Workload Automation?
My main use case for ActiveBatch by Redwood is automating complex job scheduling and workflow orchestration across multiple systems. I also automate end-to-end IT maintenance tasks such as system h...
What is your experience regarding pricing and costs for ServiceNow Orchestration?
The cost of ServiceNow Orchestration is considered medium; it is expensive but powerful. I would rate the pricing experience as a six out of ten.
What needs improvement with ServiceNow Orchestration?
If I compare the interface of ServiceNow Orchestration with Boomi, it is easier to use Boomi than ServiceNow Orchestration. Boomi is an ESB with orchestration features to integrate and exchange dat...
What is your primary use case for ServiceNow Orchestration?
I use ServiceNow Orchestration's third-party integrations, and when I benchmarked ServiceNow Orchestration, I ensured that there are connectors and API capabilities available to integrate it with o...
 

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
experian, BEACHBODY, HealthPartners, Banosoft
Find out what your peers are saying about ActiveBatch by Redwood vs. ServiceNow Orchestration and other solutions. Updated: June 2026.
900,644 professionals have used our research since 2012.