Overview

Product video
Fully Managed Enterprise AI Workflow Orchestration for AWS
Run mission-critical application, AI, and data workflows without managing infrastructure. Faster delivery, consistent governance, and scalable automation, powered by AI.
The solution integrates with Amazon Bedrock and leverages AWS GenAI services to create AI agents orchestrated by Control-M.
Control-M SaaS delivers:
- Fully managed enterprise AI orchestration, no infrastructure or upgrades to handle
- Centralized control across application workflows, file transfers, and data pipelines that keep workflows running on time
- Proven reliability, visibility, and governance for hybrid and multicloud environments
- Natively integrates with AWS services (S3, Bedrock, Snowflake, etc.) and hundreds of other enterprise systems
- Orchestrates AI agents in event-driven workflows
- Modern AI assistant (Jett) and agentic AI capabilities to create workflows
Start now by purchasing directly through AWS Marketplace.
All the power of Control-M; delivered as SaaS.
Highlights
- Simplifies workflows across hybrid and multi-cloud environments
- Deliver data-driven outcomes faster by managing production data pipeline workflows in a scalable way
- In-depth workflow observability with intelligent predictive analytics and reports
Details
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Custom pricing options
How can we make this page better?
Legal
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Vendor resources
Support
Vendor support
BMC provides documentation and general support at our BMC DOCs site. We also offer direct support plans and support from BMC Partners. For more information please visit
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Standard contract
Customer reviews
Daily scheduling work has become more reliable and has saved time coordinating complex jobs
What is our primary use case?
I work as a scheduler.
I have not yet integrated Control-M with AI or ML workloads.
I use Control-M with SAP.
To coordinate between SAP jobs and non-SAP jobs such as SAP HANA or BW, I work on multiple types of jobs.
Control-M integrates with other vendors or solutions as usual, but we do not have many jobs in SAP, and I work on the OS file watcher.
I do not use ITSM or change management tools such as ServiceNow or other incident response solutions with Control-M.
What is most valuable?
The best features are probably that I work on the planning and scheduling of jobs.
Besides that, I work on the connection profile.
Control-M helps me save schedule time.
I do not work on other applications. I use only Control-M throughout my whole day, and it is reliable.
What needs improvement?
I used version 9.01 until last week, I guess.
Since yesterday, I have been using version 9.22.
Comparatively, I guess it is a little bit faster.
For how long have I used the solution?
I have been working with Control-M for more than eight years.
What do I think about the stability of the solution?
I rate stability an eight out of 10.
What do I think about the scalability of the solution?
In our team, we have around 20 members using the solution.
I rate scalability a seven out of 10.
How are customer service and support?
I rate technical support an eight out of 10.
How was the initial setup?
The solution does not require any maintenance yet, and so far everything is good.
What's my experience with pricing, setup cost, and licensing?
I am not sure about pricing, but I guess it is affordable.
What other advice do I have?
Apart from my work, I do not use Control-M.
I recommend Control-M for schedulers also.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Workflow orchestration has improved and simplifies database pipelines with helpful AI agents
What is our primary use case?
My main use case for Control-M is to connect it with my database and use it for projects and data pipelines.
A specific example of a workflow I connect with it is the database and the data pipeline for my projects. I use Control-M to schedule and coordinate those database and pipeline tasks. I store my full stack development data in the database and pipeline, set up security, and build my CI/CD integration flow.
Our main business use cases supported by Control-M are mostly in supply chain.
How has it helped my organization?
My impression of Control-M for giving business users visibility and control over their jobs is that it has been helpful. This is important for the organization because it helps with the easy flow of work.
My impression of Control-M for freeing up IT personnel to focus on essential operations is that it is a very good tool and really helpful. It is also very useful for the organization in focusing on the main business area.
Using Control-M has helped simplify, rather than complicate, creating and integrating data pipelines across on-premises and cloud technologies. Creating and integrating the flow is easier using Control-M.
It has had a positive impact by providing different features, such as agentic capabilities, which have been really useful.
Debugging faster using agentic capabilities is one of the main benefits. Having log summaries from that agent feature is another.
It has improved organizational work, such as enabling faster delivery and maintaining SLAs.
What is most valuable?
The best feature Control-M offers, based on my experience, is the database and pipeline support.
What is most useful in my CI/CD workflow is the agent and agentic agent capabilities.
Those agents have helped with my database and pipeline workflow so far, mostly in debugging and analyzing what the issue is. I get help there.
My view of the governance and security of Control-M's AI capabilities is that it is good. Guardrails have been added, and the responses it gives are very helpful.
Integrating with technologies for our DataOps and DevOps processes as things change is of easy to medium difficulty.
Of the Control-M Python client and the API, I have used only the API, and it is really good, with all the validations and controls that it has.
What needs improvement?
Control-M can be improved with a better UI flow, I believe.
The UI flow is all right, but I feel that responsiveness and other aspects of it can be improved.
The accuracy and reliability of Control-M's AI output is limited. It sometimes hallucinates a lot, but that can be improved.
For how long have I used the solution?
I have been using Control-M for almost a month.
What do I think about the stability of the solution?
It is stable. It is good.
What do I think about the scalability of the solution?
Around 100 to 200 users interact with Control-M in my organization. Their main roles are developers.
The solution is not extensively used at present, as it is only in the initial phase. I plan to increase usage, though I am not sure by how much, as we are at a very early stage of usage.
Five people use it, and they are developers.
Scalability is good, both vertical and horizontal.
How are customer service and support?
Customer support is quick, with faster replies. It is decent.
I would rate it eight.
How was the initial setup?
The initial setup took one hour.
What about the implementation team?
Around 15 developers in DevOps manage deployment and maintenance activities.
What's my experience with pricing, setup cost, and licensing?
I purchase directly.
It is easy. Pricing is decent. Licensing is okay.
What other advice do I have?
On a scale of 1 to 10, I would rate Control-M overall at nine.
My reason for giving a nine is that I find it useful, and its features are really good.
Agents can make the work easier and faster.
Control-M is good for easing the work that we do. It makes the work easier, simpler to understand, and faster to execute. I suggest it, and people can use it.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Automation has reduced time to production and simplifies building and monitoring workflows
What is our primary use case?
The main use case for Control-M is workload automation.
How has it helped my organization?
We are able to automate a lot for the client, and the time to production is reduced because of the automation and workflow building.
What is most valuable?
One of Control-M's best features is its quick integrations with many tools. It has positive integrations.
I find those helpful because it has so many inbuilt connectors, which make connectivity to any other tools very easy. It is quick, and we are able to integrate it with various tools, such as Apache Airflow and SAP, without having to customize it.
I would rate Control-M well for building, scheduling, managing, and monitoring production workflows.
Using Control-M makes it simpler to create, integrate, and automate data pipelines across on-premises and cloud technologies because it has a very easy UI to do that.
The UI makes it easier to automate everything.
What needs improvement?
I can't think of anything at the moment for how Control-M could be improved in its next release. One of the things is that the cost is a bit on the higher end.
For how long have I used the solution?
I have been using Control-M for around two to three years.
What do I think about the stability of the solution?
Control-M is stable.
Control-M is reliable because we are able to build the workflows very efficiently, and the connectivity with other systems makes it by far a very good tool to use.
What do I think about the scalability of the solution?
Scalability-wise, Control-M is good. It has pretty decent features on that part, and we are able to install quite a lot of agents in it.
In our production system, we have 300 odd agents installed, and the connectivity is flawless. There are no issues with that. Scalability-wise, we do not face any issues, and whenever we have to run more workload, it runs fine.
How are customer service and support?
Customer service and technical support are good. Customer service is very prompt, they always provide details whenever we request them, and the documentation is also very good.
On a scale of 1 to 10, with 1 being the worst and 10 being the best, I would give their customer service and technical support a nine.
What was our ROI?
I see a return on investment with Control-M.
Because Control-M automates a lot of workflows for us, and the time to execution for those improves our efficiency, the return on investment is there and cost saving is there.
Working with Control-M helps reduce the total cost of ownership overall.
What's my experience with pricing, setup cost, and licensing?
My experience with the pricing and the setup cost is that it is on the higher side.
What other advice do I have?
I do not think the Control-M that we are using was purchased through the AWS Marketplace. I think it is enterprise level, so it was bought directly from BMC.
On a scale of 1 to 10, with 1 being the worst and 10 being the best, I would rate Control-M overall a nine.
My one piece of advice for other organizations considering Control-M is to consider the cost of implementing the solution. However, I think that at the enterprise level, there are further deals they bunch in with different BMC products as well, so that should be good from the organization's perspective.
Integrated orchestration has simplified hybrid workflows and now provides stronger audit governance
What is our primary use case?
Our use case for Control-M is workflow automation across a hybrid multi-cloud IT infrastructure, legacy ERP systems, and modern open-source technologies.
Regarding how our organization has adapted to integration with AI or ML workloads with Control-M, we are from the services industry, so we need to keep up with the speed of AI because we also need to deliver AI perspectives to our clients. From the internal IT perspective, we are a kind of customer zero, where we implement things from our end and then showcase them to our clients, and they get adopted in the different client environments. We are very well into the AI journey.
Regarding MLOps workflows such as MLflow, SageMaker, Vertex, or Azure, we are in the journey of adopting cloud workloads at this moment. Until now, we have only run legacy workloads, including .NET, OS jobs, DB jobs, and SAP jobs, which we run directly using Control-M right now.
We are now adopting cloud-native workloads and then progressing to ML. No ML workload is running now, but some aspects of it are running. We have Python jobs that provide some ML aspects, but not in a native form. We are using them in some other form.
Control-M contributes to our AI governance requirements mainly through orchestration, which is one part, because we also have agents deployed as an orchestrated tool to take up the work assigned to them and do the job.
We have self-service portals exposed to our application teams, where they can request some of the work done by the admin team. They can do some of it themselves, and those jobs get piled up in Control-M. The application programs are based on Control-M, and then Control-M picks up that job, executes it, and provides that requirement fulfillment to the end users. That is the way we are mainly using it at this moment.
We manage the coordination between SAP batch jobs and non-SAP workflows, such as HANA BW, with Control-M. As part of our complex hybrid IT environment, we need to juggle between SAP and non-SAP, because we expect some data from SAP, and since SAP is not that GUI friendly or the data is in a different format, we generally do that work on the non-SAP side.
We use the job chains concept in Control-M for mixing SAP and non-SAP workloads. We use it for data movement and the data lineage part of it in that sense.
We have Control-M deployed in a hybrid model. Movement happens because we generally have data movements across this multi-cloud environment. Currently, since we are restricted to on-prem, the other data cloud is having a challenge right now, which we are trying to avoid with our Control-M SaaS at this moment.
We use Control-M to orchestrate workloads across multiple environments, including on-prem, virtual, and cloud.
How has it helped my organization?
Control-M helps us handle complex data pipelines, and that is one use case we are looking at, because data movement across clouds or across different data centers is always a problem, since you don't have the connectivity and other things. Control-M serves as a major orchestration layer. You move data between different places and get complete observability and complete data lineage from them. It helps a lot from that perspective.
Control-M helps us build, schedule, manage, and monitor workflows, and it is the best at the technology. That is the power of Control-M. It is very good. There is no problem for any new team member to walk in and learn the product. It is pretty easy, and compared to other tools, the learning curve is very easy.
We have offloaded the complete operations of Control-M to our L1 team. They don't have a technical background, but they are still able to manage the complete operations. That is the power of the product, because if the product were so complex, we would not be able to run it. We would need specialists. We have specialists, but not in my operations team. I have them in my technical and engineering team.
To run it for this large scale of users and these kinds of applications, we manage almost 6,000 plus jobs, so you can understand how often these jobs change and how their schedules change. There are releases, and all of this has to be managed by a team. Considering this much application support, we may need 20 or 30 plus resources just to manage and run the operations of the controller. We are doing it with a very minimal number, fewer than 10.
Those are our L1 resources, so they also get some technical exposure, and we reduce the burden on operations so we can focus mainly on the engineering perspective.
What is most valuable?
The best features we use and appreciate most in Control-M are the integrated orchestration and the compliance and governance capabilities. We run finance-related applications, and since I am from internal IT, we run a lot of finance work and get audited often on the workflow automations, because this happens behind the applications.
Control-M has given us a lot of visibility from the audit perspective and the governance aspect. We don't have to spend so much time telling the audit teams, "Okay, this is what we have." We have readymade things available in Control-M to provide the details auditors have been requesting. That is the other thing I find attractive about this solution.
Before we started using Control-M, we used a Redwood product called CPS. It is from SAP, actually. SAP acquired it, and we used that until we moved away from it during the COVID times.
My role is technical mentor and infrastructure solution architect, which generally means I look at infrastructure feasibility, automation governance, and all those things from the application side. I implement the same things and do the feasibility checks. We do the same thing for infrastructure. That is my role.
The orchestration, the automation, and the stability are the more important things I need to mention. We have not had any bigger outages or anything of that sort, which we had problems with in the earlier tool. The stack is pretty cool and stable, so we don't want to put effort into maintaining the tool, but rather leverage what the tool has to offer. That is another thing I can tell.
What needs improvement?
Orchestrating Kubernetes jobs or cloud-native workflows with Control-M presents some challenges and opportunities, and we are working through them. The major challenge we have is from the security perspective, because of the strict governance and controls from our company. If you want to run any of your agents, it requires bi-directional communication between the Control-M server and the agent at this moment. That is what I understand from them.
In some places, for example, if I place my agent on my cloud, such as Azure Kubernetes, I need bi-directional communication from Azure Kubernetes, which might not be allowed these days because of security controls. We have communicated and highlighted to our Control-M team that it may not be feasible for the company to provide full-fledged bi-directional communication. Instead, they could proxy it or forward the traffic to the different cloud provider or different environment protected by firewalls.
These are the things we are having some challenges with in adopting some of the cloud-native workloads. We are still seeking some of our security approvals, because generally any traffic inwards to the corporate network is disallowed, including from the cloud. Apart from normal HTTPS and HTTP, if you want DB connectivity from my cloud to my on-prem, that is generally not allowed. That kind of communication is required for the Control-M agent to talk to the Control-M server. That is where we have some problems at this moment, and we are trying to work through them.
At the same time, we are also exploring the SaaS part of it, but that is another challenge for us, though we have started exploring. We got the demo tenant, and we are trying to do some POCs on it to see whether the security challenges posed by our company can be accommodated in the SaaS version.
In my opinion, regarding areas in Control-M that have room for improvement, at this moment I don't see anything that is missing. We are not leveraging most of the features, as I understand it. We have the file transfer capability and many other capabilities. Because of our use case, we are destined to use some OS jobs, DB jobs, and SAP jobs at this moment. We are planning to explore cloud-native, then Kubernetes, and then AI. That is our roadmap at this moment. I don't have any feature request or anything pending with BMC.
That was the main problem we had with Control-M. If you ask me about challenges, I remember one now, which is the integration with an external CMDB, or Configuration Management Database. For example, we have 300 plus applications run and hosted within Control-M. I cannot give Control-M access to the whole team, because their jobs and workloads are all different. I need to provide 300 groups with different logins or different ways to communicate, and they should see only their own jobs.
Those capabilities were not present in Control-M when we were looking at options a year back: the external integration with CMDBs. That is the reason we built our own layer, our own self-service portal on top of it, which we integrate. We integrate our CMDB from our wrapper service, and then we call your API and do the Control-M work. That is how we are doing it right now.
Because that particular external integration is not there, we are doing it with our self-service portal at this moment. That is one challenge we have, the external integration with the CMDB. Since the automation APIs are available, we are making use of them and getting around that challenge at this moment. It would be good to have external integration with CMDBs built into the system, so you wouldn't need to manage and build this system for us.
For how long have I used the solution?
My experience with Control-M is more than six years now.
What do I think about the stability of the solution?
Stability is one of the main reasons I am still with Control-M, because my team doesn't have to spend a lot of time on the stability part. Once it has been set up, the product is very stable, apart from the external ecosystem where it runs, such as VMs or other ecosystems we have, and that is where the challenges come from. As a product, I don't see issues such as a bug in the product, frequent hangs, or unexplainable outages. I am not seeing anything like that with Control-M right now.
We are migrating from our VMs to physical machines, because we are exiting VMware and moving to physical servers and similar machines. Previously, we ran Control-M on VMware, and now we are moving to physical servers. Some cutovers are planned for today, and I am still talking to you, which means I have that much stability in my team. That is very good.
I would rate Control-M's stability at 98%, or more than that. Maybe you can put 99%. I just keep that 1% with me.
What do I think about the scalability of the solution?
The number of platform admins using Control-M is less than 10. The business applications, meaning the application owners, number 1,000 plus. They have visibility into the systems. They get a read-only version of their jobs, and they can look at the monitoring console and all those things to see whether their jobs are running. They can see the logs and their schedules, but they cannot make schedule changes or anything on the platform side. The platform side is less than 10, and the users might be more than 1,000 plus.
I think scalability is nine out of 10. It is pretty much able to run. I think we run more than 10,000 jobs, from what I understand of the overall workloads. It is able to manage them with no problem. There are no unexplainable outages, no non-scheduled jobs being missed, and no vanishing schedules, which were very frequent in my earlier tool. Compared to the earlier tool, this is a big boon for us, from the stability perspective as well as the governance perspective.
How are customer service and support?
Technical support from Control-M is very good. It is excellent support. Even with any issues, they make sure we get a technical solution, or if it cannot be technical, they can come to a logical conclusion as well. The technical support of Control-M is the best I have seen, because I have worked with more than 20 or 25 products, not only Control-M, but other workload products, cloud products, cloud hosting providers, and many other products. Control-M has one of the superlative support teams I have seen.
I would rate Control-M a nine.
Which solution did I use previously and why did I switch?
When I compare Control-M to other solutions or vendors, that is always in regard to the features I mentioned earlier that I appreciate most. The orchestration part, the integrated orchestration, lets us use SAP, non-SAP, DB, and open-source technologies in all formats. We are able to stitch together all the application requirements and data movements across all these platforms. I am not sure whether other products have this feasibility, because I haven't had a chance to review them, but I know about one tool we were using prior to Control-M, which doesn't have this flexibility. Stitching across or cutting across multiple technologies is always a bigger problem.
From the automation perspective, we have built an in-house tool that helps the application teams or business teams trigger jobs based on their needs. We use the Control-M APIs, which the product uses internally for scheduling and running all those things. We use those same APIs and expose them to our in-house applications, providing an interface for our business teams to trigger jobs as and when they need. That is the self-service portal I mentioned earlier.
That kind of flexibility is not available in the earlier tool. You had to go to the tool and do it yourself, and because of some restrictions, we could not give access to our tools. So we provide simplified dashboards or screens with access controls.
How was the initial setup?
Our overall experience with the migration process with Control-M is very smooth. The migration perspective is very smooth, because for any upgrades or migrations, you have the migration approaches built into the way the product is designed. We have primary and secondary concepts. First, we do it on the secondary, then we monitor it for some time, then we fail over to the secondary and see whether things are working wherever we have upgraded. Then you have the option to do it on the primary.
The way Control-M is built, upgrades and migrations are all considered in the tool engineering itself. That is the best thing for adoption, as well as for any migration or upgrade that brings more features. That helps us adopt it. If upgrades are difficult, people will be reluctant to move to the next versions because of the effort involved, and whether that effort is worth the features in the next version. Those kinds of concerns don't come to mind when we do a Control-M upgrade.
What was our ROI?
The return on investment we see is more than 50% for sure. It is not 100%, I would say, maybe because we are not using it to the fullest of its features, whatever is available to us. That is also on us. We have yet to adopt the modern workloads as well as the cloud-native workloads because of the security controls we have. I would say more than 70%. That might be my ballpark number.
What's my experience with pricing, setup cost, and licensing?
Pricing for Control-M is not cheap and not expensive. I would say it is cost-effective. It is not cheap.
What other advice do I have?
Control-M does require maintenance, and it is very easy to maintain. The complexity is very low. It is easy to maintain, it is stable, and it is pretty good compared to the other tools I have used.
Centralized workflows have reduced manual effort and have improved container-level tracking
What is our primary use case?
My main use case for Control-M is batch job scheduling, data pipeline and ETL architecture, and enterprise application workloads.
For a recent example, we used Control-M for orchestration, where automated workflows were created around a business use case to make tracking easier for us. My application is for a shipping company. We work at the container level, so Control-M has made it easier to build an application that tracks what happens to a container, specifically to design these workflows.
Control-M is deployed as a hybrid cloud in our organization and is used to orchestrate workflows across on-premises systems and cloud platforms. It serves as a central scheduling and monitoring solution for critical business processes, data pipelines, and operational jobs.
For our hybrid cloud deployment, we primarily use Amazon Web Services (AWS) as our cloud provider. Control-M is used to automate and monitor our flows running in AWS.
How has it helped my organization?
Control-M has positively impacted our organization by reducing manual effort through automating repetitive tasks, batch jobs, and operations. This allows the team to work more on architecture and new features, rather than spending time on repetitive jobs that need manual intervention every time.
Application reliability has also improved, and Control-M has been reliable since we started using it. We can also predict a better SLA based on the tickets we receive. In addition, central operations have improved because multiple schedules and workflows are consolidated into a single platform, which reduces complexity. These impacts have significantly improved our organization.
In terms of measurable outcomes, we have reduced manual effort by almost 50 percent and job failure dependency by around 30 to 40 percent.
What is most valuable?
In my opinion, the best features of Control-M are centralized scheduling across different locations, cross-platform workflow orchestration, dependency-based and event-based automation, and SLA management.
Control-M also offers extensive integrations with SAP, Oracle, Snowflake, Kafka, and Kubernetes. These integrations bring information and data from those platforms into one place so that we can automate those processes, which is very useful.
Regarding governance and security, Control-M provides strong capabilities through role-based access controls, audit trails, and centralized management and control of workflow execution. These features help ensure that only authorized users can create, modify, or execute jobs while maintaining visibility into operational activities.
From a governance perspective, the centralized management capabilities help organizations enforce standards and maintain compliance across teams and environments. Overall, I believe its governance and security features are mature and suitable for enterprise-scale operations.
Regarding the accuracy and reliability of Control-M's AI output, my experience has been positive. The AI-generated insights and recommendations are generally accurate and helpful for understanding workflows. They have helped reduce investigation time and improve productivity.
Although critical decisions require human validation, the AI has helped a lot. The accuracy has been very high, and it has met my expectations.
What needs improvement?
There are a few areas where Control-M could be improved, such as licensing and cost. It is expensive compared to alternatives such as Autosys. Faster troubleshooting, enhanced root cause analysis, and more diagnostics for failed jobs would also help support teams resolve issues. Control-M is a mature and reliable workload automation platform, but it should be improved through a more modern user interface, simplified administration, and more flexible licensing.
The main improvements I would like to see in Control-M are UI simplicity, advanced reporting, and faster troubleshooting.
While Control-M is a mature and reliable workload automation platform, the main improvements I would like to see are more intuitive AI, better AI-powered troubleshooting, and more flexible licensing. These enhancements would further improve the overall user experience and operational efficiency.
For how long have I used the solution?
I have been using Control-M for around a month.
What do I think about the stability of the solution?
In my experience, Control-M has been stable. I do not think we have faced any downtime. It has been very stable.
What do I think about the scalability of the solution?
Regarding scalability, Control-M has scaled up effectively to handle our increased workload. We have been able to scale the number of jobs and flows while maintaining performance, reliability, and operational visibility. This has enabled our support team to grow without a proportional increase in manual effort.
Which solution did I use previously and why did I switch?
Control-M currently serves our needs.
What was our ROI?
Control-M delivered an ROI primarily through time savings and operational efficiency. We estimated that it reduced manual effort.
What's my experience with pricing, setup cost, and licensing?
We purchased Control-M through the AWS Marketplace.
My experience with Control-M's cost and licensing has been reasonable for an enterprise-grade workload automation platform. The organization mostly handles the cost and licensing side, and we were involved only in the selection criteria. That said, the reduction in effort justifies the investment well, but I feel there could be a little bit more.
Which other solutions did I evaluate?
However, based on my experience using Control-M, it has proven to be reliable. Some common alternatives suggested during that time were Tidal Automation, IBM Workload Scheduler, and Stonebranch. We finally decided on Control-M, and it has been good for us.
What other advice do I have?
I would rate Control-M a nine out of ten.
I rated Control-M a nine because it is a highly reliable and mature workload automation platform. I did not give it a ten because there is still room for improvement in areas such as licensing cost, user interface modernization, reporting capabilities, and some cloud-native features. These are the factors that led me to take a point off.
My recommendation to others reading reviews on PeerSpot is to use Control-M, since it has been a great help for our organization and our team. For someone with a use case like ours, it has been a great help, and they can look forward to using it.