JAMS OverviewUNIXBusinessApplication

What is JAMS?

JAMS is a centralized workload automation and job scheduling solution that runs, monitors, and manages jobs and workflows that support critical business processes. The software can automate jobs on any platform including Windows, Linux, UNIX, IBM i, zOS, and OpenVMS and includes native application integrations to run jobs specific to databases, BI tools, and ERP systems.

This solution can save you time & money, eliminate security risks, and give more visibility to the critical jobs that keep your business running.

Key Features:

  • Cross-platform scheduling with multiple interfaces including desktop and web clients, .NET SDK, REST API, and PowerShell cmdlets
  • Centralized monitoring with customizable alerts and notifications
  • Scheduling logic that includes triggers, dependencies, and sophisticated workflow logic
  • Enterprise security with granular controls for applying custom access privileges to jobs, folders, users, and schedulers
Buyer's Guide

Download the Workload Automation Buyer's Guide including reviews and more. Updated: September 2021

JAMS Customers



General Dynamics


CVS Health



Boston’s Children’s Hospital

JAMS Video

Pricing Advice

What users are saying about JAMS pricing:
  • "It was $10,000 for the first year. Then, there is a maintenance cost for licensing every year that we get billed $5,000 for every year."

Filter Reviews

Filter by:
Filter Reviews
Filter Unavailable
Company Size
Filter Unavailable
Job Level
Filter Unavailable
Filter Unavailable
Filter Unavailable
Order by:
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Showingreviews based on the current filters. Reset all filters
Vincent Kwok
Data Architect at San Francisco Public Works
Real User
Top 20
Works out dependencies between jobs, but doesn't have the friendliest of UIs

What is our primary use case?

We use it to schedule batch jobs. Batch jobs are a combination of SSIS jobs, which is actually our group's main use case. I brought it in mostly to schedule our SSIS batch jobs. Then, there are other groups who are using it for SQL Server stored procedures. We also have another group using it for a few Python scripts and FME, which is a different type of ETL tool. So, we are using JAMS to schedule those four types of jobs as well as a bunch of FTP jobs. The application developers have been doing a combination of migrating some of their older jobs, like Python scripts and SQL stored procedures… more »

Pros and Cons

  • "The fact that we no longer need to use Excel spreadsheets is huge. Before JAMS, every group was keeping track of their own batch jobs. Nobody really knew what the other jobs were. So, if jobs failed, other groups wouldn't necessarily know. With JAMS, everything is done through a single scheduler. You can choose who to notify."
  • "The client is horrible. Every time JAMS puts out a survey on what they can improve, I always say, "The client: When you are setting up jobs, it is quite horrible." The response has been, "Well, we are just using the Windows foundation," and I am like, "Why isn't it only your product?" We can get around it now that we know its quirks, but it is not the most user-friendly of tools out there. The UI is completely unintuitive. We had to go and open up a support ticket with JAMS just to get something back. It is not user-friendly at all."

What other advice do I have?

Biggest lesson learnt: It is critical having a scheduling tool that will show you where all the jobs are and what their dependencies have been when you are doing batch jobs. In the past, SQL Server Agent jobs allowed you to do it, but you really needed the ability to look at interdependencies between jobs. That is what JAMS gives you. The reason why I am giving it a seven is because of the UI. If they fix the UI, I would give a higher grade than seven.
Garth Ries
CTO at a financial services firm with 51-200 employees
Real User
Having a single pane of glass enables us to track the success of all of our automations throughout the day

What is our primary use case?

Our primary use case is for batch automation. We don't use the RPA product. We use the scheduling agents that can run on other machines so that when the scheduler kicks off the job, it can run either on the main JAMS server or it can run on an agent box. We do have some interactive jobs that interact with the desktop mainly in Excel, but that's not our preferred method. We want to be, as much as we can, a more structured batch. As far as interactive, we don't have folks that are interacting with the jobs. The jobs are built to run standalone. They may interact with the desktop or with the… more »

Pros and Cons

  • "JAMS has improved my organization by taking a myriad of manual processes and allowing us to automate them. It enables our folks to focus more on tasks that require their human intelligence and their creativity and less on just mundane tasks. It increases efficiency, accuracy, and consistency."
  • "One thing that I know that the JAMS people said that they were working on that would be huge for us is a search capability so that you could search for tasks. It may be available in version 7 or in a future release of 7. I think that's on their roadmap. But right now, for us to do a search, we have to search through database queries."

What other advice do I have?

We've been able to do more with less. In other words, we've either not had to increase staff in some cases, or when people left, we didn't replace them. We've been able to reduce staff. We didn't have layoffs, but when people left, we didn't replace them, and that was largely due to the automation efforts through JAMS. If I had to do it all over again, I would probably use their professional services to kickstart things. We did a lot of self-training on JAMS, so we've learned a lot along the way, but if I had to do it over again, I would probably have used more of their training capabilities…