Overview
Control-M simplifies workflow orchestration complexity, making it easy to define, schedule, manage and monitor complex application workflows, ensuring visibility, reliability and improved SLAs. It integrates, automates and orchestrates application workflows across on-premises, private and public clouds, so your jobs get delivered on time, every time. With a single unified view, you can orchestrate all your workflows, including file transfers, applications, data sources and infrastructure with a rich library of plug-ins. Easily provisioned in the cloud, Control-M leverages the ephemeral capabilities of cloud-based compute services. Using a Jobs-as-Code approach with REST APIs and JSON, workflows become versionable, testable, maintainable, and collaborative for developers and DevOps engineers as a part of their CI/CD pipeline.
For organizations with mainframe modernization initiatives, Control-M integrates with AWS Mainframe Modernization Service to preserve the continuity of mission-critical business outcomes.
BMC only sells Control-M via Private Offers and customized pricing, please reach out to BMC_Hyperscaler_Team@bmc.com if you want to make a purchase.
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
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
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
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Additional details
Usage instructions
When your instance is created, log in as ec2-user to the the EC2 instance. You will be prompted to enter the required parameters to complete the installation. Parameters such as username and password. You can use any of values for the initialization questions , below an example for input: Pg sql database admin password - manager Retype password - manager Controlm database user - emuser Password - empass Retype password - empass Controlm server database owner - ctmuser Password - ctmpass Retype password - ctmpass
After the installation process is finished, Control-M runs using the local PostgreSQL server. To start using Control-M, once your AMI or stack is running, wait a few minutes for Control-M to initiate and then navigate to: https://<DNS>:8446.
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
Automation has reduced manual intervention and supports reliable, seamless job scheduling
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.
Job scheduling has provided clear visibility into dependencies and efficient failure analysis
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?
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.
Reliable Workflow Automation with Strong Scheduling and Monitoring
Control-M Turns Hybrid Scheduling into a Deterministic, SLA-Smart Orchestration System
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 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.