Sold by
Control-M SaaS
Control-M SaaS is an application workflow orchestration platform that integrates, automates and orchestrates complex data and application workflows, leveraging AI capabilities across highly heterogeneous technology environments.
Reviews (316)
Ashak Ali Khan
Automation has reduced manual job handling and provides centralized control for complex workflows
Reviewed on Oct 05, 2026
Review provided by PeerSpot
What is our primary use case?
Our primary use case for BMC Control-M is enterprise job automation and scheduling. We use Control-M to centrally manage and monitor a large number of jobs across the organization, including scheduling, execution, failure handling, job resumption, and alerting. It provides end-to-end automation and centralized control of critical batch workloads.
How has it helped my organization?
Control-M has improved operational efficiency by automating and centrally managing job scheduling, reducing manual intervention, minimizing failures and downtime and providing faster alerts and recovery of failed jobs.
What is most valuable?
The features I appreciate most about Control-M are its user-friendly interface and simplicity. It is not overly complex and the built-in APIs make it easy to use and integrate with other technologies.
For DataOps and DevOps processes, integrating Control-M with other technologies is relatively easy with an overall medium level of integration complexity.
What needs improvement?
The version of Control-M I was using did not have AI capabilities. Control-M would benefit from stronger AI integration that can analyze error messages, identify the root cause and take appropriate corrective actions without human intervention. Currently, some basic errors still require manual intervention, which AI could help minimize.
For how long have I used the solution?
I have been working with BMC Control-M for more than 15 years, with my first implementation experience being for a leading Saudi telecom operator.
What do I think about the stability of the solution?
I rate the stability of Control-M as a stable 10. Control-M is a stable product.
What do I think about the scalability of the solution?
The number of users using Control-M is around 50 plus. We have a centralized administrator who has a team working with different stakeholders, making this a centralized tool.
Control-M is scalable. We can do both scale-out and scale-up. Both options are available.
How are customer service and support?
I rate Control-M support around nine out of 10.
Which solution did I use previously and why did I switch?
We have been using Control-M since the beginning. We explored other products in parallel, but this was a fresh installation with no migration.
What was our ROI?
Regarding ROI with Control-M, we have not quantified it, but it has definitely saved manual work. A lot of human work has been automated through Control-M, although we do not have quantification of the exact savings.
Which other solutions did I evaluate?
When I compare Control-M with other solutions such as Apache, ActiveBatch, Broadcom, and HCLTech HWA , I find that Control-M stands out, particularly in terms of product support and global support capabilities.
What other advice do I have?
I definitely recommend Control-M to others and some customers have already purchased Control-M based on our recommendation. I give this review an overall rating of 10.
reviewer2906376
Workflow tool has made patch deployments clunky and has limited automation flexibility
Reviewed on Oct 05, 2026
Review provided by PeerSpot
What is our primary use case?
My main use case for Control-M is that we use it for DevOps jobs.
A quick, specific example of a DevOps job I run with Control-M is that we patch servers often, and we have a sophisticated deployment process for different packages in our on-premises servers. We do not just use an out-of-the-box package manager; we have a Control-M process that handles pushing these patches into these controlled environments.
Regarding my main use case or how I use Control-M for these deployments, that is everything I do. We have lots of different Control-M jobs for doing different things, but we mostly use it for patching.
My main business use cases or services supported by Control-M include DevOps and management of devices used for deploying our application at different environments.
How has it helped my organization?
Control-M's reliability is its big appeal to me, as it has consistently worked for the organization since long before I got into it. Its simplicity in that way and its user interface are the big appeal, but that is about it.
That reliability and simplicity have helped my team when it works correctly and as desired, as the little task box turns red when it has failed, which is a good indicator for us that it is something we need to look at. It is an easy way to review a large number of jobs through a kind of world view of all the jobs, allowing us to see if anything has failed and letting us know what has failed in a nice user interface, making it very accessible to a lot of teammates. However, it has the drawback that just because a job has not completed successfully does not mean it has returned an error that turns the box red.
I do not have any metrics regarding how Control-M has improved the way my organization functions. It seems to have been picked a long time ago for its nice UI, but I think we made poor use of it. Good use of it is not very intuitive, and the lack of integrated version control makes people afraid to change things to try and improve them. Due to its proprietary nature, we lack environments to test adjustments on, which leads me to believe it has not been particularly helpful.
What is most valuable?
The best features Control-M offers, in my opinion, include the ability to selectively hold and run different jobs and the nice user interface, although I am not really keen on Control-M myself. It is not version controlled, which I really hate, or at least our implementation of it, but it is lacking in a lot of features. That is why I also use Jenkins.
The UI helps my daily workflow by giving us a quick visual way to establish what kind of progress a specific job is making.
What needs improvement?
I would appreciate Control-M providing better logging on the output of different jobs because sometimes a job completes and it thinks it succeeded, but it did not. There should be more programmability around error logging and better integration with version control. We are not really using Control-M as well as we could because we are not parameterizing all of our jobs and their steps, which I think can be done better, but that should be a lot easier to do. It is very hard to update these jobs, especially since we do not have something such as a JSON file for it that we can update.
To improve Control-M, there needs to be more programmability around how and when we log errors, and it would be nice to have some tools that actually allow us to interface with Control-M with scripts being run by the task steps. I think it would be beneficial to have some kind of configuration file that we could read, representing each job, giving us the ability to text edit these jobs instead of having to drag these boxes around, which is inconvenient. Additionally, better integration with version control, a web view, and improved resizing for the desktop application would be awesome. I also find that when I search jobs, the search bar does not order them in the order they are actually executed in, just alphabetically, and better searchability for these jobs is needed, especially when you have a large number of them in queue simultaneously.
It is very inconvenient to integrate Control-M with technologies for my data ops and DevOps processes as things change.
I would assess Control-M for building, scheduling, managing, and monitoring production workflows as not very effective. I use Control-M at least every few days, but it presents a kind of unhelpful user interface. While we have more senior people on my team familiar with all these functionalities, I mostly just run patches when needed, which is not very convenient. Coming from a more Linux-heavy world with depth in Jenkins, I find that these processes are much more convenient and the user interface for actual configuration and programming is much easier. Overall, Control-M comes across as very low-tech and clunky.
Using Control-M has made it pretty much impossible to create, integrate, and automate data pipelines across on-premises and cloud technologies. We almost never make new Control-M jobs because it is so inconvenient, and it is just a very clunky and tough tool to use. I would almost always prefer to do my work with Jenkins or simply write a Python script that logs its progress rather than use Control-M due to the cumbersome process of breaking steps into little boxes without version control.
For how long have I used the solution?
I have been using Control-M for just a year.
What do I think about the scalability of the solution?
I do not really know how many users are using Control-M in my organization, but my team consists of about ten people using it on and off, depending on our needs at the time.
How was the initial setup?
I do not know how long the deployment of Control-M took, as that predates me by a long time.
Which other solutions did I evaluate?
I did not participate in the migration to Control-M, and I assume that over time, we will migrate more to Jenkins, as much as we can in the probably distant future.
What other advice do I have?
I would rate Control-M overall a two out of ten.
I rate it that low because it is really very low-tech for what it does, and it has really fallen behind a lot of DevOps tooling. I use Jenkins here and there, which has version control and the convenience of managing credentials, making it easy to add agents and nodes, and it facilitates connections between those nodes more intuitively than what Control-M does. Control-M just makes you SSH into target machines; it essentially runs scripts and lacks built-in configuration compared to a tool such as Jenkins. Even though Control-M seems general-purpose, that just means it is not very well applied to the DevOps work I do, making it a clunky, proprietary piece of software. Its user interfaces are not really that valuable to actual technical people who just want good logging and good integrations for their automation.
Regarding Control-M's AI capabilities, I have not seen any governance and security features.
I have never used Control-M's AI capabilities to assess the accuracy and reliability of output.
The biggest lesson I have learned from using Control-M is that it is good to have code in front of you. Many organizations have followed trends onto tools that are very WYSIWYG, and I have used several such as Telerik Reports in the past. If you do not have code in front of you, you do not really know what is going on, and it becomes hard to facilitate integrations and log specific technical and business functionalities. Buying higher-level proprietary tools can lock you out of your own workflow due to the lack of customization and access.
My advice to others looking into using Control-M is to not do that because it is a proprietary product that overlaps a lot with newer open-source technology that is more accessible and paradigmatic for modern software development. Since it is a commercial product, the company likely offers consulting for best practices on how to use it, and getting training for its intended users along with documentation within the organization could help prevent other companies from falling into the same un-paradigmatic usage we have experienced.
Mahmudul Hoque Khan
Centralized workflows have improved automation and monitoring but onboarding still needs work
Reviewed on Sep 26, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for Control-M is primarily for workflow and job scheduling, automation, and monitoring recurring data processing tasks. Day-to-day, I use it to manage dependencies between jobs, monitor execution status, troubleshoot failed workflows, and ensure scheduled processes run reliably without manual intervention.
I use Control-M most often for scheduled data processing and reporting jobs. The reporting jobs I generate primarily involve scheduled processes that collect data from different systems, process and validate it, and then generate reports for operational teams. Control-M manages the sequence and dependencies, so the reports are produced automatically on schedule and alerts when a job fails or takes longer than expected.
For my main use case with Control-M, it provides not just scheduling from a central point of view but also workflow visibility and operational control. Having dependencies, alerts, and job status in one place makes it easier to identify issues quickly and reduces the amount of manual monitoring my team needs to do.
What is most valuable?
The best features I find most useful are workflow orchestration, job dependency management, centralized monitoring, and automated alerts. I especially appreciate being able to see the status of the entire workflow in one place and quickly identify where a failure occurred. The scheduling flexibility also makes recurring reporting and data processing tasks much easier to manage.
Control-M has positively impacted my organization by improving the reliability and visibility of our scheduled workflows. We have reduced manual monitoring, caught failing jobs faster with proactive alerts, and made recurring reporting and data processing tasks more consistent. It has also given my team better visibility into dependencies, which helps us troubleshoot issues before they affect downstream processes.
What needs improvement?
The user interface and configuration experience of Control-M could be more intuitive, especially for new users. Some advanced scheduling and dependency configuration can take time to understand. Better guided workflows, clearer documentation, and a simpler setup experience would make onboarding and day-to-day administration easier.
Another area where Control-M could be improved is in simplifying integration and administration. Setting up connections across different systems can sometimes require additional configuration and possibly more troubleshooting. More streamlined connectors, clearer configuration guidelines, and easier centralized administration would make the platform more efficient for teams managing a hybrid environment.
For how long have I used the solution?
I have been working in my current field for about two years.
What do I think about the stability of the solution?
In my experience, Control-M has been stable and reliable for production workflows. Scheduled jobs generally run consistently, and when issues occur, the monitoring and alerting capabilities are effective.
What do I think about the scalability of the solution?
Control-M has scaled well as our workflows and environment have grown. We have been able to add more jobs, workflows, and integrations without a major increase in manual administration. Its centralized scheduling and monitoring also make it easier to manage a larger number of workflows across different environments.
How are customer service and support?
I have reached out to customer support a couple of times, and they have been generally responsive and helpful. We contacted them mainly for configuration and troubleshooting, and they were able to help us identify issues and provide guidance quickly. The response time was reasonable, although more complex issues sometimes required additional follow-up and investigation time.
Which solution did I use previously and why did I switch?
Before using Control-M, we used Apache Airflow for workflow scheduling and orchestration. As our team grew and our environment became larger, we wanted stronger scheduling, centralized monitoring, dependency management, and broader integration capabilities, which led us to switch to Control-M.
How was the initial setup?
Setup required some initial planning with vendor-specific technical teams and configuration, particularly around integration and workflows. Once established, the ongoing administration was fairly manageable.
What was our ROI?
We have seen a return on investment with Control-M primarily through time savings and reduced manual effort rather than direct headcount reduction. Alerts also contribute by helping reduce delays and the time spent troubleshooting failed jobs.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing feels reasonable for an enterprise workflow orchestration platform, although the overall cost depends on the deployment size and required capabilities.
Which other solutions did I evaluate?
Before choosing Control-M, we evaluated several alternatives, including IBM Workload Scheduler and Broadcom Automic Automation. We compared them mainly for workflow orchestration, dependency management, monitoring, integration, scalability, and ease of administration.
What other advice do I have?
The biggest lesson I have learned from using Control-M is that workflow orchestration reduces operational complexity. Taking the time to properly define dependencies, alerts, and failure handling rules upfront makes production workflows much more predictable and reduces the need for manual intervention later.
My advice for others looking into using Control-M is to clearly map your existing workflows and dependencies before implementation and make proper planning. Control-M provides the most value when you have complex systems and processes that need centralized orchestration. Investing time for initial configuration and training for teams will help them take full advantage of its monitoring and automation capabilities.
Control-M has been a useful tool for workflow automation and production visibility. Its scheduling, dependency management, monitoring, and alerting capabilities have helped reduce manual effort and make our recurring production processes more consistent. The main areas I would like to see improved are the user experience, configuration simplicity, and onboarding for new users. I would rate this product a 7.
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?
Amazon Web Services (AWS)
MohammedMukhtar
Job scheduling has provided clear visibility into dependencies and efficient failure analysis
Reviewed on Sep 17, 2026
Review provided by PeerSpot
What is our primary use case?
I have been using Control-M in my career overall for quite some time. I joined this company about five years ago, but Control-M has been used there for way before, perhaps eight years, nine years, or more than that.
What is most valuable?
What I like the most about Control-M is that it is very reliable and works well for scheduling and even monitoring. The best thing I could say is the good visibility of jobs and their dependencies. When something fails, suppose when multiple jobs are affected, it would be useful to quickly identify the original failure and what was impacted because of it. Otherwise, it has very good visibility, scheduling jobs, and status is everything is good.
What needs improvement?
When something fails, as an improvement, it would be useful to have a clear explanation of what actually went wrong. The interface can sometimes feel a little busy for us. Finding the right information can take some time. It is not that we cannot find it, but it takes a few clicks. It is always helpful to have something very clear that quickly identifies what went wrong.
For how long have I used the solution?
Control-M has been used there for way before, I joined perhaps eight years, nine years, or more than that.
What do I think about the stability of the solution?
Regarding stability, there is no lagging and no issues with stability; it is pretty good.
What do I think about the scalability of the solution?
Regarding scalability, I can say ten out of ten because it gives very good visibility of all the jobs and stability. There is no crash or downtime. It runs pretty well.
How are customer service and support?
I have contacted the technical support or customer support of Control-M;. If we have any issues or need any help, we do contact them and raise tickets.
Regarding the quality and the speed of the support, as of now, I can say that it is acceptable. The response time is quite good. When we need them to be on call to help us, we decide on time and they come online to assist us. So it is acceptable.
Which solution did I use previously and why did I switch?
I have never used any alternatives or something similar; we have been using Control-M for quite some time.
How was the initial setup?
Regarding how easy or difficult it was to learn how to use Control-M, we have been using both web client and fat client, and I feel that the fat client is easier than the web client. There are a lot of options in the web client. With the fat client, I get more visibility and a more user-friendly interface. In terms of easiness, since it was already deployed and the functionality was there, it was pretty easy with some training from my team. It was not so hard to get through Control-M.
What about the implementation team?
Control-M does require some maintenance on my end; we have periodic updates and patches. However, that is regular and that is needed to patch the vulnerabilities. Other than that, there is not much maintenance required.
What's my experience with pricing, setup cost, and licensing?
I am not familiar with the pricing;I think it is still in discussion with Control-M.
Viju D.
Reliable Workflow Automation with Strong Scheduling and Monitoring
Reviewed on Sep 15, 2026
Review provided by G2
What do you like best about the product?
What I like most about it is its ability to reliably automate and manage complex workflows. It offers strong scheduling, monitoring, and dependency management, which makes it easier to ensure jobs run on time and that issues are identified and resolved quickly.
What do you dislike about the product?
One thing I find challenging is that it can be complex to manage and troubleshoot, especially in environments with a large number of jobs and dependencies. The interface and configuration also take some time for new users to learn and get comfortable with. That said, its strong scheduling, monitoring, dependency management, and automation capabilities still make it very valuable for enterprise workloads.
What problems is the product solving and how is that benefiting you?
It helps us automate and manage complex batch workflows by scheduling jobs, handling dependencies, monitoring executions, and alerting us when failures occur. As a result, we spend less time on manual intervention and face a lower risk of missed jobs or tasks running in the wrong sequence. It also provides clearer visibility into the overall workflow, which helps us troubleshoot issues more quickly and improve operational efficiency. Overall, it saves time, reduces errors, and makes our job scheduling and production operations more reliable.
Maalini K.
Control-M Turns Hybrid Scheduling into a Deterministic, SLA-Smart Orchestration System
Reviewed on Sep 11, 2026
Review provided by G2
What do you like best about the product?
What sets Control-M apart is its ability to eliminate the "invisible critical path" failure across hybrid infrastructure. In complex environments, the primary risk is rarely a complete server outage; it is unmonitored downstream latency creep. Native platform schedulers—whether on AWS, Azure, or legacy mainframes—operate in operational silos. A fifteen-minute delay in an on-premises transactional batch job can silently starve downstream cloud analytics pipelines hours later.
Control-M transforms these isolated tasks into a deterministic operational nervous system. By leveraging the Automation API, engineering teams can define orchestration as declarative code directly within standard CI/CD pipelines. This gives developers autonomous workflow ownership without sacrificing production governance, compliance auditability, or resource management. Furthermore, its Batch Impact Manager proactively recalculates critical path variance based on dynamic runtime history, identifying SLA drift hours before a breach occurs rather than firing reactive alerts after a job has already failed.
Control-M transforms these isolated tasks into a deterministic operational nervous system. By leveraging the Automation API, engineering teams can define orchestration as declarative code directly within standard CI/CD pipelines. This gives developers autonomous workflow ownership without sacrificing production governance, compliance auditability, or resource management. Furthermore, its Batch Impact Manager proactively recalculates critical path variance based on dynamic runtime history, identifying SLA drift hours before a breach occurs rather than firing reactive alerts after a job has already failed.
What do you dislike about the product?
The biggest hurdle with Control-M is that its architectural sophistication, granular governance rules, and sheer depth of enterprise orchestration power create a steep learning curve, requiring teams to fundamentally elevate their operational standards just to take full advantage of how capable the platform actually is.
What problems is the product solving and how is that benefiting you?
The core business challenge Control-M addresses is operational friction and systemic delivery risk across fragmented hybrid architectures. Enterprises routinely struggle with brittle data handoffs when mission-critical systems of record, on-premises legacy databases, and distributed cloud applications run on disconnected native schedulers. Without centralized visibility, teams inevitably face silent pipeline stalls, SLA breaches, and costly manual firefighting.
Control-M mitigates this vulnerability by serving as a unified, deterministic orchestration backbone. The operational and commercial benefits are significant:
Guaranteed Service Level Agreement integrity comes from real-time critical-path tracking that dynamically recalculates execution timelines based on historical variance. This helps prevent delays in time-sensitive transactional settlements, payroll runs, and regulatory reporting, instead of merely surfacing post-failure alerts.
Radical cost reduction and operational efficiency follow from replacing fragile custom scripts and scheduled cron routines with native, event-based workflow dependencies. This reduces manual triage hours and frees engineering talent to focus on product velocity rather than maintaining low-level orchestration plumbing.
Unified governance without sacrificing agile velocity is enabled by integrating workflow definitions into CI/CD pipelines as declarative code. This allows cross-functional developers to deploy workloads quickly while still maintaining rigorous compliance auditability, role-based controls, and end-to-end operational visibility across the broader data estate.
Control-M mitigates this vulnerability by serving as a unified, deterministic orchestration backbone. The operational and commercial benefits are significant:
Guaranteed Service Level Agreement integrity comes from real-time critical-path tracking that dynamically recalculates execution timelines based on historical variance. This helps prevent delays in time-sensitive transactional settlements, payroll runs, and regulatory reporting, instead of merely surfacing post-failure alerts.
Radical cost reduction and operational efficiency follow from replacing fragile custom scripts and scheduled cron routines with native, event-based workflow dependencies. This reduces manual triage hours and frees engineering talent to focus on product velocity rather than maintaining low-level orchestration plumbing.
Unified governance without sacrificing agile velocity is enabled by integrating workflow definitions into CI/CD pipelines as declarative code. This allows cross-functional developers to deploy workloads quickly while still maintaining rigorous compliance auditability, role-based controls, and end-to-end operational visibility across the broader data estate.
krishna K.
Control-M Makes Automation and Job Monitoring Effortless
Reviewed on Sep 09, 2026
Review provided by G2
What do you like best about the product?
What I like most about Control-M is its automation and monitoring capabilities. It makes it easy to manage job dependencies, track job status, and quickly identify failures without having to monitor everything manually.
What do you dislike about the product?
One area that could be improved is the user interface and troubleshooting experience. Sometimes it can take time to understand the root cause of a failed job, especially when there are multiple dependencies. Better error messages, simpler navigation, and more detailed failure explanations would make Control-M easier to use.
What problems is the product solving and how is that benefiting you?
Control-M helps us automate job scheduling, manage dependencies, and monitor data workflows instead of handling them manually. This saves time, reduces human errors, and helps us identify and resolve failed jobs faster, making our overall process more reliable.
Mahesh V.
Control-M Makes Batch Job Monitoring Organized and Reliable
Reviewed on Sep 08, 2026
Review provided by G2
What do you like best about the product?
What I like most about Control-M is how easy it makes it to manage and monitor scheduled jobs and workflows from one place. The job dependencies and visual workflow view are especially useful for understanding where a process is stuck or has failed. I also like the alerts and monitoring features, as they reduce the need for constant manual checking and make troubleshooting much quicker. Overall, it has made managing complex batch processes more organized and reliable.
What do you dislike about the product?
The main downside is that Control-M can take some time to learn, especially for new users who are not familiar with workload automation. Setting up and managing complex workflows can sometimes feel complicated, and troubleshooting failed jobs is not always straightforward. The platform also has a lot of features, which can make the interface feel overwhelming at first.
What problems is the product solving and how is that benefiting you?
Control-M helps reduce the manual effort involved in scheduling, monitoring, and managing batch jobs and data workflows. It gives us better visibility into job dependencies and failures, while automated alerts help the team respond quickly when something goes wrong. This improves reliability, reduces operational overhead, and makes it easier to manage complex workflows consistently.
Anonymous
Effective Centralization Despite a Steep Learning Curve
Reviewed on Sep 08, 2026
Review provided by G2
What do you like best about the product?
I love how Control-M allows us to centralize different scripts that were scattered, improving dependency management between projects. The documentation of processes and automatic retries are also aspects I greatly appreciate. The documentation provides developers with a centralized place to understand processes, while automatic retries enhance the robustness of pipelines in case of issues, such as network problems. Additionally, Control-M's ability to log everything automatically is very convenient, especially for the traceability of algorithm executions, which is critical in the space domain.
What do you dislike about the product?
The learning curve is not optimal with Control-M, making its initial use somewhat complex. The terminology is quite extensive with terms like "job, flow, agent, calendar, condition, event," and the interface is a bit concentrated. Additionally, the basic setup takes a few days, but full integration and connection to internal software took several weeks.
What problems is the product solving and how is that benefiting you?
I find that Control-M centralizes our scripts, improves dependency management, and automates logging for compliance. Its documentation and retries enhance the robustness of pipelines.
Unnikrishnan R.
Simplifying Complex Workflow Automation
Reviewed on Sep 02, 2026
Review provided by G2
What do you like best about the product?
What I like most about Control-M is how it brings everything together in one place. It makes it straightforward to monitor workflows, see and understand job dependencies, and quickly spot issues when something goes wrong. On top of that, the automation cuts down on a lot of manual effort and helps keep day to day operations running more smoothly. It was reliable and stable, especially when handling large numbers of jobs and complex workflows.
What do you dislike about the product?
What I dislike about Control-M is that it can feel a bit complex at first, particularly when you’re setting up and managing more complicated workflows. Some configurations take quite a few steps to complete, and troubleshooting can be time-consuming at times. The user interface could also be more modern and intuitive, which would make day-to-day navigation easier. Overall, it’s a powerful tool, but new users should expect a learning curve.
What problems is the product solving and how is that benefiting you?
Control-M helps address the challenges of managing and monitoring complex workflows and scheduled jobs across different systems. It cuts down on manual effort, provides clearer visibility into job dependencies, and makes it easier to spot and respond to failures. As a result, processes are more likely to run on time, and day-to-day operations become more reliable, simpler to monitor, and less time-consuming.