No more typing reviews! Try our Samantha, our new voice AI agent.
You need to sign in or sign up before continuing.
reviewer2817654 - PeerSpot reviewer
Internship (Engineer) at a consultancy with 11-50 employees
Real User
Top 10
Apr 19, 2026
Training labs have expanded my skills and are helping me build AI projects and portfolios
Pros and Cons
  • "By using JAMS, my company has seen benefits such as getting to know about Google products and the latest features that are newly launched by Google, and they help me in building my projects portfolio and engaging with knowledge."
  • "I would enhance the compatibility feature of JAMS because sometimes when the server is under high load, it does not inform us and we cannot get answers."

What is our primary use case?

There are many types of use cases for JAMS. I get to know about Gemini and Google Cloud SDKs, which I use in making my projects for hackathons and my portfolios.

What is most valuable?

By using JAMS, my company has seen benefits such as getting to know about Google products and the latest features that are newly launched by Google. Additionally, they help me in building my projects portfolio and engaging with knowledge. I participated in many types of quests and seminars where I learned more about this, and I was also a speaker there so that I could explain what JAMS is and what the Google tools are.

JAMS helps notify and handle common issues that prevent jobs from running because when we use JAMS, we get to know about Google products and there is also a feature of Google Cloud notification. From there, the notifications are about open job roles, new job quests, and many more things that today's HRs use to build new jobs.

JAMS helps centralize the management of jobs on all my platforms and applications.

JAMS helps save time when troubleshooting stalled jobs because it provides troubleshooting features. If any of the programs are debugged or errors occur, then troubleshooting clarifies them.

What needs improvement?

I would enhance the compatibility feature of JAMS because sometimes when the server is under high load, it does not inform us and we cannot get answers. It often tries to give irrelevant answers, so I would improve that compatibility of JAMS.

For how long have I used the solution?

I have been using JAMS for about two to three months. I completed all the JAMS labs in one to 1.5 months.

Buyer's Guide
JAMS Scheduler
November 2026
Learn what your peers think about JAMS Scheduler. Get advice and tips from experienced pros sharing their opinions. Updated: November 2026.
922,942 professionals have used our research since 2012.

What do I think about the stability of the solution?

When I use JAMS and the troubleshooting method, it takes one to two hours to resolve problems. However, when the servers are under high load, it can take more than one day sometimes.

Which solution did I use previously and why did I switch?

My company did not migrate from another solution to JAMS.

How was the initial setup?

I have experience with the pricing, the setup cost, and the licensing, and I find it to be good.

What was our ROI?

I did not see a return on investment with JAMS because I did not invest in any type of JAMS. When the Google Cloud study JAMS arrived in India, they provided free credits to use JAMS products.

What's my experience with pricing, setup cost, and licensing?

I have experience with the pricing, the setup cost, and the licensing, and I find it to be good.

Which other solutions did I evaluate?

I evaluated many types of questions about how to build AI automations before choosing JAMS. I found that many features did not work properly when trying to make AI automations without JAMS, so I took the help of Gemini and all the Google Lab products that helped me build proper AI automation.

What other advice do I have?

I appreciate that JAMS has a very familiar UI because it is not complex. Every child, meaning 15 to 20 years of age, can easily use JAMS because the UI feature is very good and very eco-friendly for students who are going to use JAMS for the first time. I also appreciate the temporary user ID and address feature because it is very safe and secure.

I sometimes use JAMS' interactive agents because I have made projects where I did not get the code properly. I used Google Gemini according to JAMS where we get information on how to use Gemini for the project. That is how I leverage JAMS' contribution toward my project.

It is important for my company to use interactive processes because people who want to work with Google can collaborate and contribute toward JAMS, as it gives the best types of knowledge for today's and future curriculum of AI and development technology.

Running interactive tasks helps users focus on their business processes because according to the automations that we use in today's world, this can help in the business field.

It is important in my company because when we get new buyers or new customers, automation helps us very quickly and is very helpful for us. In the absence of any types of people or employers, we get this automation done in their work on their behalf. This is majorly important in today's time.

JAMS' interactive agents help bridge the gap between structured batch automation that happens on desktops and web browsers because they allow people without knowledge of coding or technical skills to use these types of agents to interact with them and also use JAMS products in their work and business.

I would rate JAMS' ability to handle exceptions between 9 to 9.5 because when I use JAMS, I get rid of all my problems by using the Google Cloud Labs in JAMS.

JAMS' code-driven automation has helped handle complex scheduling requirements because it helps in complex problems according to each person's need.

JAMS has helped eliminate data slack across my company.

It is important for my company that data is ready to go when users need it because we use JAMS products and prototypes in our company's database since it is eco-friendly and easy to use, without complex debugging issues.

JAMS helps to eliminate monitoring tools because it makes our work easier, so we do not need to buy some subscriptions, which means it eliminates them.

When I use JAMS, it helps me eliminate tools that sometimes make mistakes. However, due to JAMS, I get to know about products such as Gemini and other Google software, including Google Colab and Google Cloud Labs, which make my work easier, even compared to paid platforms.

JAMS has helped to free up my IT staff's time.

It has freed up enough time because it is eco-friendly and easy to use, which is why it helps.

I would advise companies considering JAMS to allow more time for study, as not only two to three months of evaluation might be insufficient. Sometimes students or beginners may not get the full information about JAMS in that timeframe, requiring them to wait for another cohort or another year. I suggest they should provide more free service and time for users to enhance and utilize all features of JAMS. I would rate this product a 9 overall.

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Google
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Last updated: Apr 19, 2026
Flag as inappropriate
PeerSpot user
Consultant at HCLSoftware
Consultant
Top 10
Feb 11, 2026
Centralized batch scheduling has reduced monitoring tools and saves time with quick issue alerts
Pros and Cons
  • "We can see all the batch execution status within the tool itself, which saves money, time, and cost, allowing us to handle everything in one single tool."
  • "For scalability, I would rate it as seven because when we have a huge volume, sometimes the tool is not so responsive."

What is our primary use case?

My use case is in batch scheduling and managing the batch jobs.

What is most valuable?

The best features of JAMS are that it is very user-friendly and not so complex. JAMS is not as complex as other tools, so we can easily get over with the tool.

Since implementing JAMS, I see a lot of improvement because they issue multiple new versions of the tool every three to four months. We usually upgrade it, which is a good thing, so we don't need to wait for a longer period of time to get our issues resolved.

JAMS does help notify and handle common issues that prevent jobs from running, which is time-saving for us. We do not need to wait for long hours; we get notified immediately, and that's a good thing. It also reduces the manpower, as there's no need for manual intervention in those cases.

JAMS helps centralize the management of jobs on all of my platforms and applications, which has helped my organization significantly. Everything is getting centralized now and all comes into the same place, where we take care of all the batch monitoring and everything. We know when and where the jobs are executing, which jobs are executing, and who is responsible for the jobs, giving us higher visibility and better handling of the batches.

Since JAMS itself is the tool that we are using for monitoring, it has helped eliminate any monitoring tools we previously used. We can see all the batch execution status within the tool itself, which saves money, time, and cost, allowing us to handle everything in one single tool.

What needs improvement?

An area that has room for improvement is related to the AWS RDS and database part, where they said that is in progress and they will be bringing it in the new version. It is handling the database in the Azure cloud environment as of now.

For how long have I used the solution?

I have been using JAMS for the past four years.

What do I think about the stability of the solution?

In terms of stability, JAMS is a stable solution, and I would rate it as nine.

What do I think about the scalability of the solution?

For scalability, I would rate it as seven because when we have a huge volume, sometimes the tool is not so responsive.

How are customer service and support?

I would rate the technical support from the vendor as eight.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I have tried other solutions including Control-M and workload automation tools from other vendors.

How was the initial setup?

The deployment was easy with not much complexity involved. We had good support from the vendor, so it was easy. We did it with the development area first, which took around two to three days. Initially understanding the requirements and building up the servers all took around two to three days to install everything. For production, it was easy since we had already done it for development and knew how it had to be done, so for production, it took around one day.

What about the implementation team?

JAMS does require maintenance, as we do patching on the servers where JAMS is installed. Other than that, we do regular upgrades whenever the new version of the tool comes into place. It is not complex to do maintenance; in fact, it is easier. Everything is a direct process, and we have proper documentation in place, so it is not complex.

What was our ROI?

I would say we have seen a 30% return on investment because we had multiple tools in place previously, and now we have stopped using all those tools.

What's my experience with pricing, setup cost, and licensing?

My thoughts on the pricing of JAMS are that I won't say it is cheap, but it is cost-efficient, and that should be acceptable.

What other advice do I have?

I do not regularly exchange files with vendors or customers because it is basically for our internal use. We have all the things within ourselves, not like external things, and there is not much file transfer within our tool.

JAMS has not helped handle complex scheduling requirements, as we usually don't use more code-driven scheduling. We always go with the sequencing and other GUI options and have not gone into that code-driven part.

It does not take much time when troubleshooting stalled jobs, as we can see all the error logs and everything within JAMS itself, making it time-saving. If a job fails, we can check the errors and logs within a few minutes to see why the job failed, which saves around 20% of our time.

Approximately 30 to 40 users work with JAMS in my organization.

The migration process to JAMS is moderate, not easier and not difficult, because a few processes are easy and a few processes are a little bit difficult. The processes I would consider on the more difficult side are some complex processes where we have to run some APIs or run some things in pipelines which are in Azure or AWS, as it requires a little bit of modifications and other things.

I would recommend this product to any users, especially for medium or smaller enterprises, because in terms of a huge volume of jobs, sometimes the tool gets a little slow in response. For medium and smaller enterprises, it is a very good tool; however, for a bigger environment, I am not sure how good it is.

Which deployment model are you using for this solution?

On-premises

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer. partner
PeerSpot user
Buyer's Guide
JAMS Scheduler
November 2026
Learn what your peers think about JAMS Scheduler. Get advice and tips from experienced pros sharing their opinions. Updated: November 2026.
922,942 professionals have used our research since 2012.
MANOJCHOUDHARY - PeerSpot reviewer
MANAGER IT at Axis Bank
Real User
Top 5Leaderboard
Sep 24, 2026
Centralized job automation has improved reporting speed and optimized daily IT operations
Pros and Cons
  • "JAMS Scheduler helps centralize the management of jobs across all platforms and applications, which is very important for our organization because it has improved scalability and reduced costs."

    What is our primary use case?

    JAMS Scheduler serves as our main solution for MIS management and IT management services within our organization.

    For particular tasks and workflows, we have different requirements for IT management and MIS reporting, and JAMS Scheduler addresses both of these needs effectively.

    Using JAMS Scheduler is not time-consuming as it provides quick responses, and for MIS reporting, it proves to be very effective for managing IT teams within our organization.

    What is most valuable?

    JAMS Scheduler offers features including reliability, cost savings, and time efficiency.

    Whenever we generate reports through this software, the MIS reporting capabilities are exceptional.

    The quick response from JAMS Scheduler helps with managing various operational aspects on a daily basis.

    JAMS Scheduler enables our team to work faster and has made our processes considerably easier.

    What needs improvement?

    JAMS Scheduler operates effectively as it currently functions, and there is no need for improvement.

    For how long have I used the solution?

    I have been using JAMS Scheduler for one and a half years.

    What do I think about the stability of the solution?

    Currently, we do not experience any issues with JAMS Scheduler as it performs well and the jobs run smoothly.

    JAMS Scheduler is stable.

    What do I think about the scalability of the solution?

    JAMS Scheduler's scalability is good.

    How are customer service and support?

    Customer support for JAMS Scheduler is exceptional.

    I rate the customer support of JAMS Scheduler a 10 out of 10.

    Which solution did I use previously and why did I switch?

    We were not using different solutions prior to this implementation as we are using JAMS Scheduler for the first time, and it performs well.

    What was our ROI?

    We have saved both money and time with JAMS Scheduler.

    What's my experience with pricing, setup cost, and licensing?

    The pricing, setup cost, and licensing for JAMS Scheduler are favorable.

    Which other solutions did I evaluate?

    We did not evaluate other options as we are using JAMS Scheduler for the first time in our organization, and it has proven to be reliable while saving time and money.

    What other advice do I have?

    We are utilizing agents related to AI with JAMS Scheduler, and it is important to add an interactive process within our organization as it delivers significant value.

    Current user focus on business processes is good, and it is very important to run interactive tasks for our organization as JAMS Scheduler excels in this capacity.

    The requirement for JAMS Scheduler code-driven automation serves our IT management team effectively, and the organization is satisfied with this approach as it delivers quick response times.

    JAMS Scheduler helps centralize the management of jobs across all platforms and applications, which is very important for our organization because it has improved scalability and reduced costs.

    I rate this review overall at 10 out of 10.

    Which deployment model are you using for this solution?

    Hybrid Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
    Last updated: Sep 24, 2026
    Flag as inappropriate
    PeerSpot user
    Raheid Dirden - PeerSpot reviewer
    Applications Supervisor, Operations at a energy/utilities company with 1,001-5,000 employees
    Real User
    Top 10
    Oct 9, 2026
    Automation has streamlined alerts and reports and delivers timely, reliable data for decisions
    Pros and Cons
    • "JAMS Scheduler has positively impacted our organization by allowing us to avoid building custom tools and use something that is more enterprise-ready."

      What is our primary use case?

      My main use case for JAMS Scheduler is to trigger integrations as well as send out alerts and reports.

      For sending alerts, I typically query databases or look at folders to make sure that the expected behavior is happening. For integrations, some are on a scheduled basis, some are ad hoc. Some are database-based, some are file-based. When it triggers, we currently use BizTalk and are moving towards using Boomi.

      We're mostly using PowerShell, which is usually used to do quick checks or run code in the background.

      How has it helped my organization?

      JAMS Scheduler has positively impacted our organization by allowing us to avoid building custom tools and use something that is more enterprise-ready.

      Since adopting JAMS Scheduler, we were planning on building a reporting and scheduling tool for the users to use, and we saved six months in development by building Python scripts in the background and allowing JAMS Scheduler to trigger the reports for users to access as needed.

      JAMS Scheduler has helped notify us of common issues that prevent our jobs from running, specifically files being backed up that need to be processed.

      JAMS Scheduler's code-driven automation has helped handle complex scheduling requirements, and it is important to our organization because we need to get data to where it needs to be in a reliable time, and that all starts with making sure the proper things are triggered at the right time.

      JAMS Scheduler has helped eliminate data slack across our applications, and it is very important to my organization that current data is ready to go when our users need it because we make decisions based off data, and having the most accurate data will provide us with that capability.

      JAMS Scheduler does help save time when troubleshooting stalled jobs, but I do not have metrics on that.

      What is most valuable?

      The best features JAMS Scheduler offers are the reporting, the logs, the ease of use, portability, and overall interaction.

      The dashboard of JAMS Scheduler allows me to quickly see if anything failed, and the reports can give me specifics on which report failed, the directory, and the error message. It also has the ability to allow you to create custom reports.

      What needs improvement?

      JAMS Scheduler can be improved by sectioning off credentials and also the web functionality and setting that up.

      For how long have I used the solution?

      I have been using JAMS Scheduler for the past three and a half years.

      What do I think about the stability of the solution?

      JAMS Scheduler is stable.

      What do I think about the scalability of the solution?

      I have not worked with scaling JAMS Scheduler just yet, but it is working just fine with our smaller server at the moment.

      How are customer service and support?

      The customer support for JAMS Scheduler is very reliable and very prompt.

      I would rate the customer support a 10.

      Which solution did I use previously and why did I switch?

      We did not migrate from another solution; mainly we used Task Scheduler.

      What's my experience with pricing, setup cost, and licensing?

      My experience with pricing, setup cost, and licensing for JAMS Scheduler was a good experience.

      Which other solutions did I evaluate?

      Before choosing JAMS Scheduler, I did evaluate other options, but I do not remember the name of those.

      What other advice do I have?

      I would give JAMS Scheduler a nine on a scale of one to ten.

      I chose a nine for JAMS Scheduler because it has everything I need, and it is very rare when it cannot do what I need it to do.

      I have not worked with JAMS Scheduler's AI capabilities yet, so I cannot provide an opinion on its governance and security.

      I have not used the AI capabilities of JAMS Scheduler yet, so I cannot comment on its accuracy and reliability of output.

      I do not use JAMS Scheduler's interactive agents, so I cannot comment on how important adding interactive processes would be to my organization.

      My advice to others looking into using JAMS Scheduler is to experiment with the different job types.

      I give JAMS Scheduler an overall rating of nine out of ten.

      Which deployment model are you using for this solution?

      On-premises
      Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
      Last updated: Oct 9, 2026
      Flag as inappropriate
      PeerSpot user
      Principal JD Edwards CNC Technical Consultant at DXC Technology
      Real User
      Top 10
      Jun 8, 2026
      Centralised scheduling has improved management of complex batch jobs and dependencies
      Pros and Cons
      • "JAMS positively impacts my organization because it helps make it easier to manage JD Edwards scheduled jobs and fills the gap that the JD Edwards application has with scheduling, resolving a lot of those issues."
      • "To improve JAMS, it should resolve the issues with the JD Edwards application and the need for the SSH agent in the current version, which has been a problem for a while."

      What is our primary use case?

      My main use case for JAMS is to install, set up, and configure for customers working with JD Edwards application.

      A specific example of how I use JAMS during an install or setup for a customer includes setting it up on a JD Edwards system with the JD Edwards batch server agent and using the run UBE command to submit the jobs remotely from JAMS. I then set up jobs in JAMS and configure sequences.

      I also add some high availability options to provide solutions for having redundancy with multiple batch servers, including leveraging JD Edwards virtual batch functionality.

      How has it helped my organization?

      Implement at customer sites rather than for ourselves however it improves on management of JDE batch processing and overall management at customer sites.

      What is most valuable?

      In my opinion, the best feature JAMS offers is enterprise-level scheduling.

      What stands out to me about the enterprise-level scheduling is that it's relatively straightforward to set up, straightforward to copy and create new jobs, and I can easily understand how all my jobs are set up and configured, monitor them, look at their history, check the logs, and track what's going on across the system while also building in dependencies.

      JAMS positively impacts my organisation because it helps make it easier to manage JD Edwards scheduled jobs and fills the gap that the JD Edwards application has with scheduling, resolving a lot of those issues.

      What needs improvement?

      To improve JAMS, it should resolve the issues with the JD Edwards application and the need for the SSH client connection in the current version, which has been a problem for a while. I suggest implementing tighter integration with JD Edwards virtual batch, catering for multiple batch servers in production versus non-production and different server maps.

      Getting bug fixes pushed through into the product has been quite difficult, which has been challenging.

      For how long have I used the solution?

      I have been using JAMS for over 7.5 years.

      What do I think about the stability of the solution?

      JAMS is very stable and we've seen minimal issues with the applications stability.

      What do I think about the scalability of the solution?

      JAMS has some scalability even without the enterprise scalable options. We have been able to leverage the agents and hook into the JD Edwards virtual batch and that configuration, performing quite well.

      How are customer service and support?

      The customer support is very good, reasonably quick, and very personal.

      Which solution did I use previously and why did I switch?

      We have worked with other business partners and looked at other solutions, but JAMS was the recommendation solution based upon our analysis and the features and functionality of the production. I have worked with Tidal previously and had some exposure to RevSoft. Tidal was very good but very expensive, and JAMS looks like the best product that works with JD Edwards and also had some local contacts who I've worked directly with and this has helped with the relationship.

      We were more of a business partner. However, as I mentioned before, we have looked at Tidal and RevSoft and some other solutions we have seen out there, but for any kind of enterprise scheduler with JD Edwards for any of our customers, we mainly look at JAMS first.

      How was the initial setup?

      Relatively straight forward but need to leverage the knowledge base for additional support or client specific requirements.

      What was our ROI?

      I probably do not have visibility regarding a return on investment. Obviously, the expectation is that there will be a return based on the product and the benefits it has.

      What's my experience with pricing, setup cost, and licensing?

      I was not really involved in the pricing, setup cost, and licensing at that level. I am more involved in the technical side rather than the commercial side.

      Which other solutions did I evaluate?

      Considered other products however costs and local support were a big factor after comparing technically

      What other advice do I have?

      JAMS helps notify and handle common issues that prevent my jobs from running. The notifications help to a certain extent, although it could possibly add further details in the email, which would also help.

      I have not had experience with the code-driven automation, although I have heard of it. I am predominantly working with the JD Edwards application, which is fairly straightforward.

      JAMS does help centralize the management of jobs across all my platforms and applications. It is very important because I predominantly work with the JD Edwards application, but I have customers who leverage it centrally, making it a lot easier to manage and also have dependencies on different types of jobs, maybe hooking into third-party integrations.

      JAMS helps eliminate monitoring tools regarding the status of JD Edwards jobs, which are not very good at all built into the application. Thus, we have to set up custom scripting and jobs to capture that information. JAMS provides all of that and access to the JD Edwards logs as well as the JAMS logs, all in a central location.

      My advice to others looking into using JAMS would be to review some of the documentation on JAMS, look at what it can do, consider the AI capabilities in the newer version, and evaluate how many agents they actually might need versus what they might have sold to ensure the correct number of agents based on the number of environments they want to set up.

      I would rate this product an eight out of ten.

      Which deployment model are you using for this solution?

      Private Cloud

      If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

      Other
      Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Business Partner
      Last updated: Jun 8, 2026
      Flag as inappropriate
      PeerSpot user
      Colm Byrne - PeerSpot reviewer
      Head of Vendor Management at a financial services firm with 1-10 employees
      Real User
      Top 20
      Oct 15, 2026
      Centralized scheduling has delivered reliable automation and saves time on routine data jobs
      Pros and Cons
      • "JAMS Scheduler has positively impacted my organization because we know it works, we know it is reliable, and we know we can set up jobs and schedules to run without needing to think about them again."

        What is our primary use case?

        My main use case for JAMS Scheduler is for scheduling tasks and activities and jobs on a hosted OMS platform.

        A quick specific example of a job or task I regularly schedule with JAMS Scheduler is extracts, database extracts from an OMS transmission, sending to recipients internally and outside the organization.

        How has it helped my organization?

        JAMS Scheduler has positively impacted my organization because we know it works, we know it is reliable, and we know we can set up jobs and schedules to run without needing to think about them again.

        This reliability has led to measurable outcomes in terms of time saved, as we have less time dedicated to issue resolution and incident investigation.

        JAMS Scheduler has helped centralize the management of jobs on all my platforms and applications through a centralized UI, making it easy to control and manage all of the child nodes in one location.

        What is most valuable?

        The best features JAMS Scheduler offers are its reliability, highly resilient nature, and an easy-to-use user interface.

        The reliability and resilience of JAMS Scheduler have helped my team because we have not had any issues with the application since it was provisioned and went live in production, making reliability and availability an absolute requirement for us.

        JAMS Scheduler's code-driven automation has not overly helped handle complex scheduling requirements for us, but it is important for us to have a single unified UI to manage all of those scheduling requirements rather than individually on distributed servers and machines.

        What needs improvement?

        It is hard to say how JAMS Scheduler can be improved at this point without a valid use case to consider. We will absolutely be considering JAMS Scheduler now and into the future for our future infrastructure changes and evolution.

        For how long have I used the solution?

        I have been using JAMS Scheduler in its current form and previous form for three to four years.

        What do I think about the stability of the solution?

        JAMS Scheduler is stable.

        What do I think about the scalability of the solution?

        Our platform is finite, and we do not see or envisage a scalable doubling in size or volume of jobs scheduled, but we are happy with having a solution that is fit for purpose and suitably scaled.

        How are customer service and support?

        The customer support for JAMS Scheduler is responsive and reactive when engaged. I would rate the customer support a nine on a scale of one to ten.

        Which solution did I use previously and why did I switch?

        JAMS Scheduler has not eliminated any monitoring tools, but it replaced a previous model which evolved into JAMS Scheduler, that previous tool being Fortra. I previously used Fortra, which was sunsetted, hence the migration to JAMS Scheduler.

        How was the initial setup?

        My organization did migrate from Fortra to JAMS Scheduler without doing a proof of concept, as it was a logical evolution in the product. It took two to three months to migrate over to JAMS Scheduler from my previous solution due to the complexity driven by a platform migration from on-premise to cloud.

        What about the implementation team?

        The overall migration process was relatively easy and very straightforward with the assistance of JAMS resources and the JAMS technical experts.

        What was our ROI?

        We have not seen a return on investment of that nature because that was not the driver for implementing JAMS Scheduler or upgrading from Fortra to JAMS Scheduler.

        What's my experience with pricing, setup cost, and licensing?

        My experience with pricing, setup cost, and licensing has been very positive, as it has been very straightforward and clear at all stages.

        Which other solutions did I evaluate?

        Before choosing JAMS Scheduler, I considered other options but did not evaluate them or do a proof of concept, as our decision was made to migrate to JAMS Scheduler.

        What other advice do I have?

        I would rate JAMS Scheduler a nine out of ten. I chose nine out of ten because I never give a perfect score. I do not know enough at this point to comment definitively on JAMS Scheduler's AI capabilities regarding its governance and security. I do not know enough at this point about JAMS Scheduler's AI capabilities in terms of accuracy and reliability of output to comment. My advice to others looking into using JAMS Scheduler is to absolutely consider all use cases, the cost of migration, and the cost of resources required to manage JAMS Scheduler, as it is a very positive, easy to use, logical, configurable application.

        Which deployment model are you using for this solution?

        Private Cloud

        If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

        Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
        Last updated: Oct 15, 2026
        Flag as inappropriate
        PeerSpot user
        reviewer2836170 - PeerSpot reviewer
        Vice President, Information Technology at a financial services firm with 501-1,000 employees
        Real User
        Top 10
        May 8, 2026
        Automation has transformed complex job dependencies and scheduling across diverse platforms
        Pros and Cons
        • "This feature helps my team day-to-day by running hundreds and hundreds of jobs on JAMS in a timely fashion, which is extremely important and sensitive, providing a lot of reporting to the entire firm and beyond."

          What is our primary use case?

          My main use case for JAMS is scheduling, which is the primary usage. I am mainly using JAMS for scheduling various jobs of all kinds.

          I onboarded JAMS when I developed our custom framework of components, and I was not relying on JAMS capacities at that time. Since then, I have primarily utilized JAMS for scheduling a variety of jobs.

          What is most valuable?

          The best features JAMS offers in my opinion allow me to create dependencies to set very complex sets of jobs to run them in a particular manner. This is what I love JAMS for.

          This feature helps my team day-to-day by running hundreds and hundreds of jobs on JAMS in a timely fashion, which is extremely important and sensitive, providing a lot of reporting to the entire firm and beyond.

          JAMS definitely centralizes the management of jobs on all my platforms and applications, and it is extremely important because it helps to run a variety of jobs on different platforms and applications. That is why I value JAMS.

          I appreciate the constant improvements in JAMS, its reliability, and it is a very powerful engine. I JAMS for that.

          JAMS has greatly improved my ability to schedule jobs and relieved me from manual execution by approximately 50%.

          What needs improvement?

          I am fine with what JAMS offers and have nothing to suggest for improvement.

          JAMS' code-driven automation is not widely used in the present environment, because I use my internally built framework components. As such, JAMS' provided code-driven automation has not been used.

          For how long have I used the solution?

          I have been using JAMS for more than 10 years.

          What do I think about the stability of the solution?

          JAMS is stable.

          What do I think about the scalability of the solution?

          JAMS is scalable.

          How are customer service and support?

          If I come across any potential or real issues, JAMS support always addresses them, which definitely helps.

          Which solution did I use previously and why did I switch?

          JAMS was a great improvement over what we used to have before. We had a scheduler called 24/7, and it had a lot of issues, but JAMS runs seamlessly and very efficiently.

          Prior to JAMS, I had a different scheduler which was not satisfactory. It was 24/7, and it was not running smoothly. JAMS helped me a lot.

          How was the initial setup?

          The overall migration process was easy because JAMS' support team provided all necessary documentation.

          What was our ROI?

          I have already shared the metrics that it saved IT time by 50%, and I think that is the most important improvement.

          What's my experience with pricing, setup cost, and licensing?

          My experience with pricing, setup cost, and licensing is that the pricing was acceptable. I have gone with JAMS licensing for years now, and I am happy to have it.

          Which other solutions did I evaluate?

          Before choosing JAMS, I evaluated other options. I looked around at what is presently employed in the industry and identified JAMS as my best solution.

          What other advice do I have?

          JAMS has positively impacted my organization in all of the above aspects. I give this review an overall rating of 9.

          Which deployment model are you using for this solution?

          On-premises

          If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

          Other
          Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
          Last updated: May 8, 2026
          Flag as inappropriate
          PeerSpot user
          reviewer2839242 - PeerSpot reviewer
          Database Engineer at a financial services firm with 201-500 employees
          Real User
          Top 20
          May 15, 2026
          Centralized scheduling has supported secure on-premise data transfers and long-running jobs
          Pros and Cons
          • "The key benefits about JAMS is having the ability to run long running jobs on-premise as compared to products like Azure Data Factory."
          • "Right now there's not much of an Azure integration with JAMS at the moment directly because we run separate pipelines."

          What is our primary use case?

          JAMS is used in my company for scheduling jobs like copying files from other customers to my company and to other databases or other systems.

          My company has been using JAMS for quite a few years now, and I think it's really good for running long running jobs.

          We exchange data files with customers every day, so we have critical, mission-critical jobs involving customer personal data and accounting transactions being in a finance industry.

          We haven't gone that far yet. It's pretty much a very basic job, collecting information and transferring files.

          I wouldn't say we've implemented advanced features yet because currently it's still very basic, just data transfers and storing locally on disk. We have other tooling for that.

          What is most valuable?

          I think what is good about this product is that it's a very well-consolidated tool that is on-premise, which includes scheduling jobs with support for Python. It also supports making API calls to cloud services like Azure, which is pretty much the main use case in my company. JAMS also has built-in SQL command lines, which attracted my attention as well.

          The major benefits I see are the ease of management and having no scattered jobs around using different tooling. If this is an environment where you don't need a DevOps engineer or it's too expensive to operate with a DevOps engineer building custom pipelines, this tool is amazing. The best use case is usually for data engineers and data analysts who are not full-time or hardcore specialized developers. This tool will definitely help them a lot.

          We have our own banking regulations in Australia, and we definitely have our own custom regulations and auditing involved. What I see as good about JAMS here is that it has all the trails of logs for each job run. That's very important.

          Generally, with the audit logs and trace downs and email alerting, I think that's very handy to have for a non-developer centric kind of environment to run jobs.

          The key benefits about JAMS is having the ability to run long running jobs on-premise as compared to products like Azure Data Factory. Azure Data Factory probably costs a few thousand per run depending on how parallel the job is. However, JAMS is different. It's licensed using a per license model.

          What needs improvement?

          I would definitely love to see a GitHub integration so that all the code written by developers is integrated with it. The jobs could be running the latest source code rather than the custom way we're doing it at the moment.

          Not directly at the moment, but I'm looking forward to GitHub integration. I think a JAMS partner or sales manager that contacted my head of department mentioned that there's a GitHub integration coming in September, so I'm really looking forward to that.

          Monitoring is not heavily used in my company.

          Most of our services are in the cloud, such as Azure, which have their own monitoring in place, so we don't use any of the monitoring in JAMS.

          Unfortunately, the monitoring features are not used as extensively as I think the tool is capable of. That's where I'm looking at hopefully having my colleagues venture deeper into all the other components, maybe the SQL server and Python integration.

          Right now there's not much of an Azure integration with JAMS at the moment directly because we run separate pipelines. We were trying to revamp everything to use Azure Data Factory, but it's not cost-effective, and there's also data governance requirements that I foresee. Having JAMS is much more feasible with on-premise data needing to be on-premise.

          For how long have I used the solution?

          I just started using JAMS about two months ago, from last month onwards and this month.

          How are customer service and support?

          I contacted the customer service team when I requested a license key for the developer edition. There's a sales representative locally in Perth from JAMS that reached out to me. I also raised a ticket to the support team in JAMS scheduler, and I think they are very helpful and amazing.

          Which other solutions did I evaluate?

          We partially use another product called SAS as a scheduler. However, what I envision is to have SAS run everything because it's a simpler platform environment and it's much more open, having support for other programming languages like Shell, PowerShell, and Python scripts.

          There's a mixture of SAS product, Azure Data Factory, and also Microsoft Fabric being used in our organization.

          I think I will probably recommend others looking at JAMS for a hybrid architecture integration to run jobs with Azure cloud services or AWS or GCP or any cloud provider that they have. I think this is the bridge to all these services. Looking at the roadmap of JAMS scheduler, I see they are introducing more cloud integration. It's moving in the right direction, so having Git integration in the September release is very exciting. JAMS is really forward thinking.

          Which deployment model are you using for this solution?

          On-premises

          If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

          Microsoft Azure
          Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
          Last updated: May 15, 2026
          Flag as inappropriate
          PeerSpot user
          Patrick Norton - PeerSpot reviewer
          Manager of Reliability Engineering and Security Operations at a computer software company with 501-1,000 employees
          Real User
          Top 10
          Dec 23, 2024
          Support has been among the most helpful and knowledgeable we've ever worked with but performance monitoring needs improvement
          Pros and Cons
          • "I appreciate JAMS for its readily available templates that allow me to create and deliver stand-up presentations within minutes quickly."
          • "JAMS has helped save IT staff time by automating tasks previously performed with scripts, and its scheduling feature has been particularly useful."
          • "The monitoring of the JAMS product and its performance is an area of concern for me."

          What is our primary use case?

          We use Fortra's JAMS as our orchestration and scheduling platform to manage workloads executed on various timelines, from daily to every few minutes. Additionally, we incorporate ad hoc workloads, manually scheduled by individuals as needed.

          How has it helped my organization?

          JAMS support has been among the most helpful and knowledgeable we've ever worked with. They're always eager to assist and quickly find solutions. While a few minor issues required escalation, we've been able to resolve them all within the current version of JAMS. 

          After initial misuse, we have optimized the use of several agents deployed in our environment. This improvement was made possible through collaboration with internal stakeholders and guidance on JAMS best practices. While agents might appear to directly solve user problems due to their ability to perform custom tasks on machines, in our cases, they operate behind the scenes, unseen by users.

          JAMS handles exceptions well, especially when calling PowerShell scripts, successfully bubbling up errors.

          It centralized our job and orchestration management functionalities into a single control plane, providing visibility into previously siloed work. This consolidation streamlined operations and enhanced oversight through a unified dashboard. Additionally, JAMS empowered us to build advanced processes by effectively managing retries, workflows, and sequences. Without JAMS, replicating this functionality would have been manual and inefficient, lacking the comprehensive visibility and control JAMS provides.

          Data Slack refers to delays in data pipelines caused by disparate and siloed processes. Using JAMS, while powerful for scheduling and orchestration, can exacerbate this issue if teams break down processes into isolated tasks within different tools. This fragmentation leads to data sitting in queues and folders, awaiting processing. To improve efficiency and timeliness, it's recommended to consolidate these fragmented processes entirely under JAMS. This allows JAMS to execute the entire workflow from start to finish within a single execution, eliminating data slack and ensuring timely data delivery.

          JAMS has helped save IT staff time by automating tasks previously performed with scripts, and its scheduling feature has been particularly useful.

          What is most valuable?

          I appreciate JAMS for its readily available templates that allow me to create and deliver stand-up presentations within minutes quickly. This efficient feature has been invaluable, enabling us to streamline our workflow and enhance productivity.

          JAMS' flexibility by allowing the use of PowerShell scripts adds to its value.

          What needs improvement?

          The monitoring of the JAMS product and its performance is an area of concern for me. I also need better tools to adopt version seven. Another area for improvement would be the addition of source control for jobs internally, as this feature would solve several problems for me.

          JAMS has some quirks. It has a bit of a learning curve.

          Some exceptions are not intuitive, such as when a job is terminated due to exceeding its defined runaway time limit. This generates a misleading exception message that is difficult for new users to understand and requires experience to interpret correctly.

          Stalled jobs present a unique challenge, particularly when pushing a system like JAMS version six to its limits. While rare, these instances occur when jobs become unresponsive despite appearing in API queries but not in the monitoring console. Although workarounds exist, they highlight the need for improved native monitoring capabilities within JAMS. Currently, the system assumes flawless operation, necessitating supplemental monitoring tools to detect issues like excessive pending or stalled jobs, ensuring timely intervention by our teams.

          For how long have I used the solution?

          I've been the platform owner of Fortra's JAMS for four years now. Before that, I used JAMS at Fortra for several years.

          What do I think about the stability of the solution?

          Through our outdated JAMS version 6 installations, we process approximately half a million executions per hour, significantly exceeding the supported capacity. Despite surpassing the rated limits by five times, we generally maintain stability. However, we experience periods of major incidents annually due to capacity constraints, which result in job failures. These performance concerns are attributed to the high execution volume. Conversely, our version 7 environment, which handles fewer jobs, has proven to be much more stable.

          What do I think about the scalability of the solution?

          If I am below those capacity issues, JAMS scales very well. However, at higher capacities, like over three hundred thousand executions, there are significant performance issues.

          How are customer service and support?

          The customer service is of high quality, and their response is prompt, exemplifying how support should be.

          How would you rate customer service and support?

          Neutral

          Which solution did I use previously and why did I switch?


          How was the initial setup?

          The initial deployment of JAMS is deceptively easy. However, there are some caveats, particularly regarding SQL permissions when setting up the database, which my team encountered. Beyond the permissions aspect, the process is straightforward; my team completed the initial setup in less than a week, with most of that time spent resolving permission issues. 

          Which other solutions did I evaluate?

          I have experience with Ansible, which can handle similar workloads as JAMS. Both have their pros and cons.

          What other advice do I have?

          I would rate JAMS a six out of ten. It is a solid platform with caveats in scalability.

          First, understand the inheritance system in JAMS, as it is not apparent. Then, consider using execution methods to streamline processes and reduce variance between jobs. 

          Which deployment model are you using for this solution?

          On-premises
          Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
          PeerSpot user
          Peter Hegland - PeerSpot reviewer
          Peter HeglandManaging Director, Automation at a tech vendor with 201-500 employees
          Top 20MSP

          Hi Patrick - thank you so much for taking time to write a detailed and honest review. I truly appreciate it! Also, thank you for being a longtime, loyal JAMS customer. I'd like to spend more time with you hearing about your areas for improvement/concerns. I do think moving to version 7 will help address any stability concerns (time and action will tell). I agree that we need to add source control features and improve the monitoring capabilities. I will reach out to you. Thanks again!Best, Peter Hegland
          Managing Director of JAMS
          peter.hegland@fortra.com

          G Srivastava - PeerSpot reviewer
          Senior Cloud Engineer at a tech services company with 201-500 employees
          MSP
          Top 5Leaderboard
          Nov 12, 2026
          Automation workflows have reduced tickets and have freed staff time for complex job orchestration
          Pros and Cons
          • "The quality of support from JAMS Scheduler team is very good."
          • "Sometimes I feel that the dashboard or the UI of JAMS Scheduler gets very heavy or sometimes not responsive. As soon as we integrate more and more jobs on it, it is getting a little clumsy or not working perfectly."

          What is our primary use case?

          My main use case for JAMS Scheduler is that several teams where I used to work have enough jobs to run, and JAMS Scheduler was the main tool for us to schedule and orchestrate all of those jobs. Those jobs were dependent, and once that one would complete, then another would start. So there were very complex jobs, and those jobs were running on Windows and Linux boxes, the SQL jobs, the Oracle jobs, and the jobs were also running the integration on the cloud. The main case of using JAMS Scheduler was to schedule all those complex jobs.

          I can give you a specific example of a job or workflow I scheduled with JAMS Scheduler. I scheduled a batch job on a Windows server that is going to run continuously the whole day. On the next week, I created another job that is going to run only at a particular specific time, for example, 12:00 a.m. in the morning on Wednesday. I just need to set the timing of the job and it is going to run. If there are any issues with the job and if it did not get succeeded, JAMS Scheduler is going to notify me via email that the job is not successful and I need to troubleshoot. I have put many jobs with the help of JAMS Scheduler.

          What is most valuable?

          One of the best features JAMS Scheduler offers, in my opinion, is that it allows me to create dependencies to set a very complex set of jobs to run them in a particular manner. For example, one job gets completed and then another two jobs are going to start. As soon as they are going to run or they are going to complete, another set of jobs is going to start. That is how the whole schedule gets completed and we get the outcome of our schedules of jobs.

          The UI of JAMS Scheduler is great and very easy to use. Sometimes I have faced some issues, but otherwise, the UI is totally terrific to use. I can easily create every job, and these jobs are centrally monitored with the notifications of success or failure and an audit trail of every execution. I can go and explore what the job has done and what are the logs of it. There are built-in conversion tools to migrate the existing jobs from Windows Task Scheduler, SQL Agent, or Cron without rebuilding them into JAMS Scheduler. They simply migrate from them into JAMS Scheduler. That is why I feel the dependencies have been really well managed in JAMS Scheduler.

          The quality of support from JAMS Scheduler team is very good. Whenever I have got into an issue, I have created a ticket, and they have come to the call and really helped me. The UI is very easy to use and set up all those jobs, and anyone can monitor. We have the web URL so I can forward it to users who are not using JAMS Scheduler day-to-day, but they can easily see the outcome of the job.

          JAMS Scheduler has positively impacted my organization. We were using some other tools for job scheduling that were giving us headaches, which I have learned from the company members and team members. Those jobs would complete sometimes and they do not provide any output. Sometimes they might have failed, but still gave the output of completion. That was a very difficult thing for us to troubleshoot. But with JAMS Scheduler, we have seen the jobs are interdependent with it, and they are running successfully, or if they are failing, they are simply providing the notification whether they are succeeding or failing. That has impacted our organization very positively, and we have started seeing improved outcomes if we compare it with our previous tool.

          What needs improvement?

          Sometimes I feel that the dashboard or the UI of JAMS Scheduler gets very heavy or sometimes not responsive. As soon as we integrate more and more jobs on it, it is getting a little clumsy or not working perfectly. I feel this should be checked. I have already notified their team about it, so they are working on it. I have tried to use the dashboard to generate some reports, and I found it difficult to understand where to get the columns or rows. I tried to use their documentation, but it was not as up to date with the tool, so there was a mismatch. I feel that both of those things should be updated accurately so that we can correlate.

          For how long have I used the solution?

          I have used JAMS Scheduler in one of my previous companies and I had used it for six to seven months.

          What do I think about the stability of the solution?

          JAMS Scheduler is stable in my experience. We have not found any issues with its stability.

          What do I think about the scalability of the solution?

          Regarding JAMS Scheduler's scalability, I would give it a number eight. As soon as we started to migrate our other applications and increase the number of jobs, it has started getting hung sometimes on the tool, and the server also gets hung. I feel it is scalable, but something more is needed.

          How are customer service and support?

          The customer support of JAMS Scheduler is very good. Whenever we opened a ticket, we received a proper RCA and solutions.

          Which solution did I use previously and why did I switch?

          We used to use Control-M and TWS Maestro before switching to JAMS Scheduler. JAMS Scheduler has given us many good features and ease of use for scheduling our jobs, which our users and team find very useful. That is why we started using this tool.

          How was the initial setup?

          We did a POC with JAMS Scheduler. For example, we took five or six servers, both Windows and Linux boxes. We simply clicked migrate for all those jobs, and it took all of those jobs from the Linux and Windows servers, added them into JAMS Scheduler, and asked us to provide the timings or how we were going to implement those scheduling, and it started giving output at the same time. The POC was very good, and we did it for seven to ten days. After that, the management found it very useful and fruitful for their employees and users, so we started the next phase on it.

          For the Windows Task Scheduler, all the jobs simply migrated from the Windows server to JAMS Scheduler with a click. I feel we did not need to migrate or just copy-paste from Windows server to Scheduler or create those jobs; it was simply migrated. I think it was a very useful and easy migration process.

          What was our ROI?

          We have seen a return on investment. For example, 30% of ROI has been saved on the number of tickets. A fewer number of employees are now needed to monitor those jobs. They just need to click the job scheduler and wait for their completion notifications via email. We receive alerts regarding whether the job succeeded or failed. If it fails, we have integrated it with our ticketing tool, so we get alerts and start troubleshooting those issues. That is how we are getting helped by JAMS Scheduler.

          Which other solutions did I evaluate?

          Before choosing JAMS Scheduler, we evaluated other options like Control-M and TWS Maestro. We had to migrate from them due to various issues. We also had a POC with another tool, but I need to recall that name.

          What other advice do I have?

          JAMS Scheduler has helped free up IT staff's time. As I mentioned in my previous answers, our users have started to create their own jobs. There is a 30% reduction in tickets for scheduling just one job. I think with the ROI of 30%, a significant amount of IT staff's time has been freed up.

          My advice to others looking into using JAMS Scheduler is that if you have complex infrastructure and jobs to run 24x7, 365 days, then I think JAMS Scheduler is a very good choice of tool for your business automation and workflow automation. I would recommend going for it if you have any of these needs. I would rate this product a 9 out of 10.

          Which deployment model are you using for this solution?

          On-premises

          If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

          Other
          Disclosure: My company does not have a business relationship with this vendor other than being a customer.
          Last updated: Nov 12, 2026
          Flag as inappropriate
          PeerSpot user
          Buyer's Guide
          Download our free JAMS Scheduler Report and get advice and tips from experienced pros sharing their opinions.
          Updated: November 2026
          Product Categories
          Workload Automation
          Buyer's Guide
          Download our free JAMS Scheduler Report and get advice and tips from experienced pros sharing their opinions.