ActiveBatch by Redwood vs Temporal comparison

ActiveBatch by Redwood and Temporal Technologies are both solutions in the Process Automation category. ActiveBatch by Redwood is ranked #9 with an average rating of 9.4, while Temporal Technologies is ranked #3 with an average rating of 8.6. ActiveBatch by Redwood holds a 0.6% mindshare in PA, compared to Temporal Technologies’s 7.0% mindshare. Additionally, 100% of ActiveBatch by Redwood users are willing to recommend the solution, compared to 94% of Temporal Technologies users who would recommend it.

ActiveBatch by Redwood

Read 35 ActiveBatch by Redwood reviews

532 Views
177 Comparison Views

100% willing to recommend

Temporal

Read 17 Temporal reviews

1,735 Views
590 Comparison Views

94% willing to recommend

ActiveBatch by Redwood

Temporal

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Dec 17, 2024

ActiveBatch by Redwood and Temporal compete in the field of automation and workflow orchestration. ActiveBatch has the upper hand in versatility and integration capabilities, making it a comprehensive solution for various IT processes.

Features: ActiveBatch offers robust features like monitoring job status, customizable scripting for task automation, and seamless integration with different systems. It effectively manages large volumes and enables automation of file transfers and database queries. Temporal focuses on developers with its workflow orchestration prowess, handling complex workflows and distributed transactions. It provides reliability and integrates well with existing tech stacks, making it ideal for microservice environments.

Room for Improvement: ActiveBatch can be complex for new users, requiring improved documentation and enhanced UI. It also needs better support for cloud integrations. Temporal's challenges lie in its complex terminology and limited documentation, alongside the absence of built-in data storage and unrefined visualization tools.

Ease of Deployment and Customer Service: Both ActiveBatch and Temporal offer flexible deployment options, including on-premises and cloud solutions. ActiveBatch users report mixed experiences with customer service, noting inconsistent support personnel knowledge. Temporal is praised for its fast and effective support, though it relies on additional deployments like AWS, which makes it more developer-friendly.

Pricing and ROI: ActiveBatch typically involves licensing costs with additional fees for specific integrations but is seen as offering good value for its comprehensive features and the operational efficiencies it brings. Temporal, being open-source, offers cost-effectiveness without licensing fees, although infrastructure costs can be significant. It provides flexibility and reliability, with potential indirect costs for custom workflow implementation related to infrastructure and maintenance.

To learn more, read our detailed ActiveBatch by Redwood vs. Temporal Report (Updated: June 2025).

Buyer's Guide

ActiveBatch by Redwood vs. Temporal

June 2025

Download the complete report

Helped 859,129 peers since 2012

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

Average Rating

9.2

Reviews Sentiment

7.4

Number of Reviews

Ranking in other categories

Managed File Transfer (MFT) (11th), Workload Automation (8th)

Temporal

Ranking in Process Automation

3rd

Average Rating

8.6

Reviews Sentiment

7.2

Number of Reviews

Ranking in other categories

No ranking in other categories

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 Temporal is 7.0%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Process Automation

Featured Reviews

Shubham Bharti

Senior Analyst at Capgemini

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.

Read full review

AbhishekDash

Senior Software Engineer at A.P. Moller - Maersk

Orchestrates infrastructure tasks like deployment, deletion, and management

Temporal focus on developers rather than business users. In contrast to older workflow orchestration engines like Camunda, which are more business-oriented and strongly emphasize UI and workflow authoring, Temporal is geared toward developers. It provides extensive capabilities for building complex workflows. A standout feature of Temporal is its handling of long-running workflows, a significant advantage over many other solutions. Temporal excels in managing distributed transactions and application state durability, especially in microservice environments where transactions might fail due to network issues. Temporal simplifies these challenges by managing retries, fail-safes, and circuit breakers. As a result, developers don't need to implement these features manually; Temporal handles them implicitly, though it also allows for tuning based on specific needs.

Read full review

Quotes from Members

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

Pros

"The Jobs Library has been a tremendous asset. For the most, that's what we use. There are some outliers, but we pretty much integrate those Jobs Library steps throughout the process, whether it's REST calls, FTP processes, or file copies and moves... That has helped us to build end-to-end workflows."

"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."

"The product offers a centralized platform for managing activities across many environments, applications, etc."

"Easy to configure and simple to develop new features."

"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."

"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."

"There are hundreds of pre-built steps."

"One of the valuable features is the ability to trigger workflows, one after another, based on success, without having to worry about overlapping workflows. The ability to integrate our BI, analytics, and our data quality jobs is also valuable"

More ActiveBatch by Redwood pros

"The solution's most valuable features include its ability to simplify the management of complex workflows, improve system resilience and fault tolerance, and reduce the need for extensive boilerplate code."

"The most valuable feature is its ability to manage and automate workflows without manual intervention efficiently."

"Temporal allows retryability for different workflows whenever they fail. It helps ensure idempotence and that things get done."

"Temporal provides visibility into workflow progress and analytics and supports scheduled tasks with customizable settings, making it very convenient."

"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."

"The solution's most valuable feature is its ability to fix things quickly."

"We like the fact that the whole process is durable, which is very useful to us."

"The initial setup is easy."

More Temporal pros

Cons

"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."

"Setting up the software was hard."

"The product should be improved by providing a customization option."

"It could be easier to provide dashboards on how many jobs are running at the same time; more monitoring."

"The documentation is very limited, and it can be improved."

"ActiveBatch is a little complex."

"As more organizations are moving towards a cloud-based infrastructure, ActiveBatch could incorporate more capabilities that support popular cloud platforms, such as AWS, Azure, and Google Cloud."

"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."

More ActiveBatch by Redwood cons

"Temporal doesn't have built-in data storage to store the state of the ongoing execution."

"Temporal lacks many resources, like YouTube videos, which users can use to learn or refer to if they get stuck with the solution."

"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."

"Retro compatibility needs improvement. Sometimes, when we make new changes to a workflow, it fails if it is not configured properly due to compatibility issues."

"There are areas where Temporal could improve. For instance, calling multiple microservices with Temporal introduces latency due to workflow registration and analytics overhead."

"One area for the product improvement is the learning curve."

"Temporal images aren’t FIPS compliant, and we have to be FIPS compliant."

"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."

More Temporal cons

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."

"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 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."

"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."

"It allows for lower operational overhead."

"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."

"Temporal is open-source and free to use, which is great. We didn't have to pay for any premium features."

"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."

"It is worth the price."

"Temporal is a free, open-source tool."

"The savings weren't as big as we initially expected, but they were pretty great from a developer's perspective."

See which vendors are best for you

Use our free recommendation engine to learn which Process Automation solutions are best for your needs.

See recommendations

859,129 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

20%

Computer Software Company

Manufacturing Company

Insurance Company

Financial Services Firm

28%

Computer Software Company

16%

Retailer

Manufacturing Company

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.

See all answers

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...

See all answers

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...

See all answers

What is your experience regarding pricing and costs for Temporal?

Temporal OSS is expensive in infrastructure, but it brings back the reliability that companies need.

See all answers

What needs improvement with Temporal?

The actual user interface is still in its early stages. It’s very basic. Users don’t really have a complex permission model yet. Users don’t really have ways to automate things like, for example, p...

See all answers

What is your primary use case for Temporal?

We [my company] use it to run a large workload. We have a set of security scans we want to perform, and we distribute them over a full day, that’s over 24 hours. We use it to orchestrate all the st...

See all answers

Comparisons

Control-M vs ActiveBatch by Redwood

Compared 18% of the time

MuleSoft Anypoint Platform vs ActiveBatch by Redwood

Compared 13% of the time

AutoSys Workload Automation vs ActiveBatch by Redwood

Compared 11% of the time

Stonebranch vs ActiveBatch by Redwood

Compared 10% of the time

Redwood RunMyJobs vs ActiveBatch by Redwood

Compared 9% of the time

More ActiveBatch by Redwood Competitors

Camunda vs Temporal

Compared 48% of the time

Flowable vs Temporal

Compared 16% of the time

Orkes vs Temporal

Compared 15% of the time

Pega Platform vs Temporal

Compared 5% of the time

Rundeck vs Temporal

Compared 4% of the time

More Temporal Competitors

Product Reports

Buyer's Guide

ActiveBatch by Redwood

June 2025

Download ActiveBatch by Redwood product report

Buyer's Guide

Temporal

May 2025

Download Temporal product report

Also Known As

ActiveBatch

No data available

Overview

ActiveBatch by Redwood automates and manages batch processes, data integration tasks, and workflow scheduling. It's used for file transfers, data processing, server monitoring, and report generation, supporting both on-prem and cloud environments.

Organizations implement ActiveBatch by Redwood to automate complex job scheduling and data workflows, integrating seamlessly with FTP, SQL, PowerShell, and other systems. With features like real-time monitoring, error handling, and centralized management, users can significantly boost productivity while minimizing manual intervention. Its flexibility in supporting on-premises and cloud environments makes it adaptable for diverse IT landscapes. The tool simplifies workflow orchestration with an extensive library of pre-built steps and robust API integrations, ensuring efficiency in handling various workloads.

What are ActiveBatch by Redwood's key features?

Job automation: Automates routine and complex jobs.
Real-time monitoring: Offers instant insights into job performance.
Customizable workflows: Tailors workflows to specific business needs.
PowerShell integration: Supports advanced script execution.
Job triggering: Initiates tasks based on specific conditions.
File handling: Manages file transfers and processing efficiently.
Server management: Monitors and handles server tasks consistently.
API integration: Connects with various applications for streamlined operations.
Alerting: Provides notifications for critical job events.
Flexible scheduling: Enables detailed and adaptable job scheduling.

What benefits and ROI can users expect?

Centralized management: Simplifies oversight of all processes.
Productivity boost: Reduces manual effort and errors.
Time savings: Accelerates task completion and workflow execution.
Comprehensive visibility: Enhances monitoring of all job activities.
Reliable performance: Ensures consistent task execution.
Scalability: Adapts to growing business and IT needs.

In various industries, ActiveBatch by Redwood is used to streamline operations, whether in finance handling large-scale data processing, healthcare managing patient records, or retail optimizing supply chains. It addresses specific needs by offering robust automation, efficient job scheduling, and seamless integration with existing systems, driving operational excellence and efficiency.

ActiveBatch by Redwood

Temporal automates and manages workflows efficiently, offering resilience in distributed systems with features like retry and fault tolerance. Its capabilities in handling complex workflows and integrating with programming languages make it a valuable tool for managing diverse business logic.

Temporal excels in workflow orchestration, automating tasks across multiple platforms, and ensuring durability in asynchronous operations. It supports long-running workflows and simplifies handling distributed transactions, reducing boilerplate code. Temporal is noted for its durable execution and built-in retry policies, enhancing resilience. Despite its complexity and steep learning curve, it is valued for its integration with popular programming languages and relatively easy setup process, though it requires improvements in user-friendly features, documentation, community support, and security.

What are Temporal's key features?

Automation and Efficient Management: Automatically handles workflows without manual intervention.
Resilience and Fault Tolerance: Features built-in retry policies for increased reliability.
Integration: Supports various programming languages, easing development.
Distributed Transactions: Simplifies complex transaction handling with reduced boilerplate code.
Durable Execution: Ensures long-running workflows are reliably managed.

What benefits or ROI should users evaluate?

Scalability and Reliability: Enhances IT environments through robust workflow management.
Ease of Integration: Supports seamless multi-platform automation.
Improved Operational Efficiency: Reduces need for extensive coding, streamlining processes.
Durability and Fault Tolerance: Provides reliable asynchronous operations.

Temporal is implemented in sectors requiring robust workflow orchestration, such as managing data pipelines, API integration, and scheduling tasks. Organizations in a Kubernetes environment leverage it for its scalability and infrastructure management capabilities, securing integrations and enhancing reliability across IT operations.

Temporal Technologies

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

Buyer's Guide

ActiveBatch by Redwood vs. Temporal

June 2025

Free Report: ActiveBatch by Redwood vs. Temporal

Find out what your peers are saying about ActiveBatch by Redwood vs. Temporal and other solutions. Updated: June 2025.

DOWNLOAD NOW

859,129 professionals have used our research since 2012.

See our ActiveBatch by Redwood vs. Temporal 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.