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

Flux vs IBM Workload Automation comparison

 

Comparison Buyer's Guide

Executive Summary

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

Flux
Ranking in Workload Automation
33rd
Average Rating
10.0
Reviews Sentiment
6.5
Number of Reviews
2
Ranking in other categories
Managed File Transfer (MFT) (33rd)
IBM Workload Automation
Ranking in Workload Automation
12th
Average Rating
8.0
Reviews Sentiment
7.1
Number of Reviews
32
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Workload Automation category, the mindshare of Flux is 0.1%, down from 0.2% compared to the previous year. The mindshare of IBM Workload Automation is 7.2%, down from 8.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation
 

Featured Reviews

it_user4206 - PeerSpot reviewer
User-friendly, extensible product with great customer support. Would like better support for multiple workflows.
* Need a better way to track a particular work item through multiple, independent workflows. There is a nice operations console to track the progress of an individual workflow, but if multiple workflows are related in some way, the engine doesn't really know/track this. * Lacks SLA-based work scheduling. It would be nice if the scheduler could take in to account SLAs and priorities to optimally schedule work across the cluster
Ilhami Arikan - PeerSpot reviewer
With an easy setup phase in place, agent-based installation can be done in minutes
Sometimes we have issues with the solution's stability. So, stability can be improved. Reporting and visibility of the solution need improvement. These days, we need more visibility. We need to access the logs and databases easily. You need to keep track of the running number of logs, like which ones are executed, completed, etc. So if there would be a good reporting dashboard, then it would be good. There's room for improvement in the solution since it is a challenging thing when we want to use the solution's technology with our new technologies. For example, if we need to use TWS on our OpenShift platform, the solution's API is not capable enough. So the product itself needs to be aligned with new technologies.
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
845,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Manufacturing Company
12%
Insurance Company
8%
Computer Software Company
8%
Financial Services Firm
32%
Computer Software Company
9%
Manufacturing Company
8%
Retailer
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Ask a question
Earn 20 points
What needs improvement with IBM Workload Automation?
IBM needs to move away from its native terminology and adopt a more cloud-centric approach. For example, IBM still refers to machines as 'workstations,' whereas other systems, like Control-M, use m...
 

Also Known As

No data available
IBM Tivoli Workload Scheduler, IBM TWS
 

Overview

 

Sample Customers

MetLife DHL Express The Clearing House Payments Company ADP Bank of New York Mellon Conway, Inc Carnegie Mellon University
Standard Life Group, Banca Popolare di Milano, A*STAR, ArcelorMittal Gent
Find out what your peers are saying about Flux vs. IBM Workload Automation and other solutions. Updated: March 2025.
845,406 professionals have used our research since 2012.