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

Astro by Astronomer vs AutoSys Workload Automation comparison

Why PeerSpot?
Sponsored
 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 18, 2026

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

JAMS Scheduler
Sponsored
Ranking in Workload Automation
2nd
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
57
Ranking in other categories
No ranking in other categories
Astro by Astronomer
Ranking in Workload Automation
6th
Average Rating
8.2
Reviews Sentiment
4.9
Number of Reviews
30
Ranking in other categories
No ranking in other categories
AutoSys Workload Automation
Ranking in Workload Automation
5th
Average Rating
8.4
Reviews Sentiment
6.6
Number of Reviews
84
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2026, in the Workload Automation category, the mindshare of JAMS Scheduler is 3.6%, up from 2.2% compared to the previous year. The mindshare of Astro by Astronomer is 1.3%, up from 1.2% compared to the previous year. The mindshare of AutoSys Workload Automation is 6.4%, down from 9.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS Scheduler3.6%
AutoSys Workload Automation6.4%
Astro by Astronomer1.3%
Other88.7%
Workload Automation
 

Featured Reviews

SP
Developer at a consultancy with 1,001-5,000 employees
Centralized scheduling has improved automation and reduces manual monitoring for complex workflows
The best features JAMS Scheduler offers are centralized job scheduling, dependency management, and monitoring. I also appreciate the alerts and retry options because they help us handle failures without constantly checking jobs manually. Centralized scheduling makes it easier to manage all our jobs from one place instead of maintaining multiple schedulers or scripts. Dependency management is especially useful for chaining workflows because JAMS Scheduler can automatically trigger the next job only when the required previous step completes successfully. Another useful feature is the monitoring and alerting. If a scheduled job fails or runs longer than expected, we can quickly identify it and take action, which is particularly helpful for production support and reducing manual monitoring. JAMS Scheduler has helped quite a bit with identifying common job failures, missed schedules, dependency issues, and execution errors. The alerts and job history make it easier to identify the failure point and take corrective action without manually checking every workflow. JAMS Scheduler's code-driven automation has been useful for handling more complex scheduling logic and workflows that go beyond simple time-based triggers. It is important for us because we can combine scripts, dependencies, conditions, and parameters to support different production scenarios without creating too much manual intervention.
FS
Data Platform Engineer at Babbel
Unified orchestration has reduced costs and improves governance for complex data workflows
I would say it would be much more helpful if Astro by Astronomer can provide an MCP to use and integrate with Astro by Astronomer and their AI agent Auto, so that we can use our tools like Claude, Code, or Cursor to have a central location where we integrate that MCP in Databricks via the AI gateway, and then we can have a place where we can connect to Astro by Astronomer, Databricks, other tools such as Jira and DataDog, and then have a much more comprehensive analysis and overview and monitoring of the entire data ecosystem. Having an MCP integration would tremendously help us to have a more comprehensive data platform that is more AI-ready. That is one of the features that I can think of. Another thought would be having an integration with Kubernetes instead of just scheduling everything on Astro by Astronomer workers. That would be helpful. One thing I can think of is that the Astro by Astronomer local developer environment can be improved further, but perhaps that is a very niche use case that I have in mind, and it may not be useful for others. There is room for improvement around having an improved UI and also integration with other tools. On governance, I would say we can have a more granular level of governance even inside workspaces. Having much more granular control over people belonging to the same team in Astro by Astronomer could have different access to different DAGs, depending upon our tagging strategy. That is one of the areas I can suggest in terms of improvement. The AI capabilities can be improved further. I would compare the current AI capabilities to newer models provided by Claude such as Opus or Codex.
PK
Assistant VP at a financial services firm with 10,001+ employees
Experience significant automation with robust integration and user-friendly interfaces
There are areas of AutoSys Workload Automation that have room for improvement. They are implementing good enhancements in the R24 release. The web UI needs some improvement. Cloud integrations are limited to 25 or 30 configurable plugins and integrations to the cloud. They can improve in that area. They have separate tools, not AutoSys Workload Automation, such as Atomic and other SaaS-based solutions that can run inside the cloud. AutoSys Workload Automation can be configured in the cloud, but it requires a substantial number of VMs depending on the load. For on-premises deployment, it is a very good solution. They need to increase their footprint in the cloud and improve the web UI. They are making excellent progress in the R24 release.

Quotes from Members

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

Pros

"The most valuable aspect of JAMS Scheduler is that over two and a half years, I have never come across any issues when running the jobs."
"The user-friendly and adaptable scheduler allows us to manage various scheduling scenarios."
"We looked at other companies, like VisualCron, that were cheaper, but one of the main sticking points was the fact that they wouldn't have provided a central location for us to monitor across all servers. That was one of the biggest selling points of JAMS."
"The fact that we no longer need to use Excel spreadsheets is huge."
"JAMS has helped save IT staff time by automating tasks previously performed with scripts, and its scheduling feature has been particularly useful."
"JAMS offers diverse scheduling capabilities for any kind of job, including Linux, PowerShell scripts, and SQL, enabling automation of jobs, which has proven beautiful after three years of usage."
"The key benefits about JAMS is having the ability to run long running jobs on-premise as compared to products like Azure Data Factory."
"JAMS has been a beneficial monitoring tool for our project in terms of being able to deliver data that is essential for users."
"Astro by Astronomer has positively impacted my organization by automating ingestion pipelines, transformations, and error handling, and it has given us relief."
"The best features Astro by Astronomer offers, in my opinion, are easy setup and good tutorials."
"The positive impact of Astro by Astronomer has mainly been on team productivity and the standardization of development."
"Astro by Astronomer has positively impacted my organization because it has helped me save time due to the big support and large community, allowing them to help me solve problems that I encounter while working with Astronomer."
"I think the possibility to save time developing DAG in a smarter way with Astro by Astronomer is a significant benefit because, as I mentioned before, it suggests the best operator for your use case."
"Previously, developing DAGs took days and sometimes a sprint, now I can deliver within a couple of hours."
"Using Astro by Astronomer is definitely improving our team's productivity."
"Astro by Astronomer has positively impacted our organization by reducing our toil and reducing the time by around twenty-five percent of what we had; before moving to Astro by Astronomer, we had to manage Airflow and manage the Kubernetes cluster as well when we were running the Kubernetes cluster locally, which saved almost one working person per month in total."
"It is more scalable; we run around 100K jobs on a daily basis, and to manage that much workload on the system, it is very reliable in terms of the uptime on the system."
"Visibility into the workflow and ease of use to be able to schedule have improved our organization."
"The most valuable feature is the ease of coding up schedules to run jobs in both the mainframe and distributed environments."
"Automic Automation Engine provides us the ability to map logic using a scripting language, giving us an advantage where practically all automation problems can easily be implemented within the Automation Engine."
"It streamlines processing really well, so we're able to cut down on our processing times."
"It is very stable and we haven't had any problems."
"CA Workload Automation AutoSys Edition is one of the most powerful schedulers that you have on the open systems, or going between Window servers; to be able to schedule and take advantage of the different powers that the automation has with it."
"In terms of the basic functionality, I found this to be a really excellent tool to work with."
 

Cons

"There are some improvements needed for JAMS Scheduler; I would like to see more detailed error diagnostics and clearer troubleshooting guidance when scheduled jobs fail."
"The JAMS automation code isn't so clean."
"I would like a simple web interface that I could give to my team to go in and kill jobs or see why jobs died so that we don't have to drill down deeper into the application and know everything about it. It would be good to have a really clean web engine that would say here are the jobs running. We can then click to see the time running and whether any of them fails and other similar things. I know they have one, but it's not very simplistic."
"JAMS notifications for hung jobs could be improved."
"The error messages from JAMS often need clarification, hindering our ability to resolve issues swiftly."
"Improvements could be made in the service desk's knowledge and communication skills among engineers to better address customer needs and ensure issues are fully resolved."
"Sometimes the UI is not the most responsive I've ever used. But because it does its job, I don't complain."
"One area of improvement I see for JAMS Scheduler is making the user interface more intuitive for new users, especially when configuring complex job dependencies."
"Sometimes we experience performance bottlenecks, depending on the time we are running DAGs simultaneously."
"Overall, my experience with Astro by Astronomer was very positive, but there are a few areas where it could improve."
"I think that one year ago, Astro by Astronomer needed to improve in reliability because it was a bit slow to develop and sometimes it crashed."
"If I had to pick one thing that could be improved, it would be the speed when working in clouds."
"After using Astro by Astronomer for four years, I can say it has evolved significantly, which is positive; however, improving the debugging experience for complex workflows remains a pain point."
"I would recommend making it easier to read the logs in Astro by Astronomer because the logs are pretty hard to follow, especially for the pipelines that are processing much data, such as our DBT, where we have issues finding something in the logs."
"There is room for improvement around having an improved UI and also integration with other tools."
"I would like to add that the pricing could be improved."
"The solution could improve by having support for container environments."
"This is probably something you don't want to hear, but support seems to be getting worse over the years."
"It lacks support and integration with cloud computing platforms."
"The solution does not have a friendly subscription model because it forces users to take a five-year subscription simultaneously, charging millions of dollars."
"We had a few issues, however, the issues were more on the infrastructure rather than with the application itself."
"We see improvement possibilities in the processing provision of predefined evaluations or individual objects, or in the Self Service portal, which can be used by any user to monitor objects or start objects."
"Documentation and cross-application externals could be improved."
"I am looking forward to more of their dashboard features."
 

Pricing and Cost Advice

"Take advantage of its scalability. You can start small. The initial cost is very reasonable. Once you have started picking up the tool and adopting it, then you can scale up from there and buy more agents."
"In the end, you'll find that it's really worth the price. There is some sticker shock, but it's worth every dime."
"Our licensing is pretty cheap because we have a state solution. So, we pay only $1,000 a year."
"JAMS is priced competitively compared to similar solutions and offers flexible licensing options to cater to user needs."
"For what it does, the product is priced very well."
"The product is reasonably priced, and we don't have any add-ons."
"The licensing model for JAMS is straightforward and based on the number of agents, not the number of jobs you run. It's cheap and fairly simple."
"I haven't been involved in the financial side for several years, but we buy one host and unlimited agents, and we get a reasonable price for that. We're happy with the amount we pay and the scalability it provides."
Information not available
"Validate how many agents you need beforehand."
"The return on investment would be very high because doing things manually without this product would be extremely expensive."
"CA pricing has been a problem, and not looked upon favorably here at all."
"I don't have information on the exact licensing cost of AutoSys Workload Automation because that's managed by the tools and financing teams. For agents, it's close to $4,00, but for the server setup, it's usually a one-time license initially, and it's AMC which is paid every year and comes close to $8,000 to $10,000."
"The pricing needs to be improved. Some of my client's complained that it was too expensive."
"People need to pay attention to how they use their ESP agents on the distributed platform. That's where some of the cost comes in, based on how many you need or how many you use."
"The price of this solution is reasonable and there is an annual license required."
"It is overpriced."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
922,528 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Comms Service Provider
10%
Construction Company
9%
Manufacturing Company
9%
Financial Services Firm
15%
Outsourcing Company
13%
Educational Organization
13%
University
6%
Financial Services Firm
30%
Outsourcing Company
9%
Manufacturing Company
7%
Retailer
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business17
Midsize Enterprise18
Large Enterprise30
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise6
Large Enterprise25
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise5
Large Enterprise79
 

Questions from the Community

What is your experience regarding pricing and costs for JAMS?
My experience with pricing for JAMS Scheduler was good. The pricing was reasonable, and the vendor only charged us fo...
What needs improvement with JAMS?
JAMS Scheduler can be improved by sectioning off credentials and also the web functionality and setting that up.
What is your primary use case for JAMS?
My main use case for JAMS Scheduler is to trigger integrations as well as send out alerts and reports. For sending al...
What is your experience regarding pricing and costs for Astro by Astronomer?
It was as we expected in terms of cost because previously we had three different orchestrators, and now we have only ...
What needs improvement with Astro by Astronomer?
If we can improve something, it would be to have hibernation for the production deployment. Currently, setting up hib...
What is your primary use case for Astro by Astronomer?
The main purpose of Astro by Astronomer today is Airflow. We are using Airflow in order to orchestrate our data pipel...
How does Control-M compare with AutoSys Workload Automation?
Control-M acts as a single, centralized interface for monitoring and managing all batch processes, which is helpful b...
What needs improvement with AutoSys Workload Automation?
There are areas of AutoSys Workload Automation that have room for improvement. They are implementing good enhancement...
 

Also Known As

No data available
No data available
CA Workload Automation, CA Workload Automation AE
 

Interactive Demo

Demo not available
Demo not available
 

Overview

 

Sample Customers

Teradata, Arconic, General Dynamics, Yum!, CVS Health, Comcast, Ghiradelli, & Boston’s Children’s Hospital
Information Not Available
Gaumont, Mercantil do Brasil, CCEE, Hanwha Life
Find out what your peers are saying about Astro by Astronomer vs. AutoSys Workload Automation and other solutions. Updated: November 2026.
922,528 professionals have used our research since 2012.