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 (310)
Chaitra Anurag
Automation has reduced manual intervention and supports reliable, seamless job scheduling
Reviewed on Sep 17, 2026
Review provided by PeerSpot
What is our primary use case?
Control-M is a reliable service provider, specifically for workload automation and job scheduling. In terms of monitoring and dependency management capabilities, it would be more viable and definitely help in reducing manual intervention.
What is most valuable?
My favorite thing about Control-M is the automation of workloads.
In terms of what I could see improved in Control-M, it involves the integration capabilities with other software. Currently, the specificities are somewhat limited, and capturing and configuring the workload can be made much easier and seamless. I wouldn't say that it needs to be changed because whatever is built is constructed in such a manner for certain reasons. However, particularly for new users, if the configuration can be made simpler, that would be helpful.
What needs improvement?
Integration capabilities with other software could be enhanced. Currently, the specificities are somewhat limited, and capturing and configuring the workload can be made much easier and seamless. Whatever is built is constructed in such a manner for certain reasons. However, particularly for new users, if the configuration can be made simpler, that would be helpful.
For how long have I used the solution?
I have been working with Control-M overall, with BMC, for roughly 18 months, equivalent to 1.5 years.
What do I think about the stability of the solution?
In terms of stability, I have not seen any downtime with Control-M.
What do I think about the scalability of the solution?
Control-M is definitely scalable. It was seamless and easily scalable.
How are customer service and support?
I have not personally contacted their support, but I am aware that my team reached out one or two times in the past.
My experience with Control-M support in terms of speed is that they were fast and reliable. They were able to understand the issue and fix it quickly.
If I were to score the support on a scale from 1 to 10, with 10 being the highest, I would give them a nine or 10.
Which solution did I use previously and why did I switch?
If I were to pick between Control-M and other solutions, I would definitely go with BMC Control-M.
How was the initial setup?
The initial deployment of Control-M was easy, considering we went through a seamless training module that was provided to us. It was also comprehensive enough for us to understand, and from my technical background, it was much simpler.
What about the implementation team?
As for maintenance, it is done by BMC. If we raise a ticket, it is managed by them.
What other advice do I have?
My relationship with BMC is more transformative. I would rate this review a 9 out of 10.
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.
Nikhil C.
Control-M: Exceptional Reliability for Complex Enterprise Workflows
Reviewed on Sep 01, 2026
Review provided by G2
What do you like best about the product?
What I like best about Control-M is its exceptional reliability and robust handling of complex enterprise job workflows and batch processing dependencies. As a backend engineer working with distributed microservices, managing scheduled tasks, file transfers, and downstream triggers seamlessly is critical. The platform's intuitive interface, powerful automation API, and comprehensive monitoring dashboard make it effortless to track execution statuses, troubleshoot failures, and ensure smooth, automated data pipelines across systems without manual intervention.
What do you dislike about the product?
The initial setup and configuration process can be quite steep and complex, requiring a significant learning curve for new team members to fully master the platform's workflow definitions and parameters. Additionally, the resource consumption and licensing costs are relatively high, making it a heavy tool for smaller-scale deployments or lighter environments. The user interface can also occasionally feel cluttered and sluggish when navigating through massive enterprise-scale job topologies and extensive historical logs.
What problems is the product solving and how is that benefiting you?
Control-M is helping us solve the fragmentation and lack of centralized visibility across our distributed microservices and batch data pipelines. Previously, managing disparate scheduled tasks and file transfers led to operational blind spots, delayed failure notifications, and heavy manual intervention overhead. By centralizing our workflow orchestration, Control-M has significantly reduced downtime, streamlined cross-system dependencies, and accelerated incident response times. This allows our engineering team to focus on building core application features rather than constantly troubleshooting broken data flows.
Recommendations to others considering the product:
Recommendations for improving Control-M include simplifying the initial setup process to reduce the learning curve for new users, optimizing resource consumption to make it more accessible for smaller deployments, and enhancing the user interface for smoother navigation through complex job topologies.
Anaswara S.
A Reliable Backbone for Enterprise Job Scheduling
Reviewed on Sep 01, 2026
Review provided by G2
What do you like best about the product?
Control-M has been really reliable for our batch processing. I like having everything in one place across mainframe, cloud, Hadoop, and ERP systems. The visual workflows make troubleshooting much easier, and the flexible scheduling and alerting save us a lot of manual effort. It’s not flashy, but it’s dependable and works well at scale.
What do you dislike about the product?
The biggest downside for me is the cost, especially as you scale and add more agents or features. It also has a bit of a learning curve, and the UI can feel dated in some areas. Upgrades and patching sometimes take more planning than expected, and custom reporting could definitely be more flexible.
What problems is the product solving and how is that benefiting you?
Control-M has helped us simplify job scheduling across different systems by giving us one place to manage and monitor everything. It’s reduced manual work, improved job reliability, and helped us catch issues before they turn into bigger problems. Overall, we spend less time babysitting jobs and have more confidence that our processes will run as expected.