Sold by: BMC Software
Deployed on AWS
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.
4.4
Overview
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
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
Pricing is based on the duration and terms of your contract with the vendor. This entitles you to a specified quantity of use for the contract duration. If you choose not to renew or replace your contract before it ends, access to these entitlements will expire.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
Dimension | Description | Cost/12 months |
|---|---|---|
Starter Pack (SaaS) | Control-M SaaS Start with 500 Executions (Base package) | $29,000.00 |
Vendor refund policy
BMC does not provide any refunds
Custom pricing options
Request a private offer to receive a custom quote.
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
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.
Similar products
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.
Control-M SaaS is a SaaS application workflow orchestration platform that integrates, automates and orchestrates complex data and application workflows across highly heterogeneous technology environments.
Control-M SaaS is a SaaS application workflow orchestration platform that integrates, automates and orchestrates complex data and application workflows across highly heterogeneous technology environments
SaaS-native BGP control plane for Telcos and Service Providers. Enable carrier-grade 5G deployments on public cloud with native SRv6 support, at 80% less cost than AWS Route Server.
Note: CTX Reflector (CTX-R) is offered under a Bring Your Own License (BYOL) model. For licensing and pricing, please contact us at sales@tryctx.com
Customer reviews
Paulofernandomarquesramada Rumos
Orchestration has transformed complex batch invoicing and now simplifies cross-platform workflows
Reviewed on Mar 13, 2026
Review from a verified AWS customer
What is our primary use case?
I lead a team of Control-M schedulers and operators, and I also do some scheduling myself. A specific example of a task or workflow I manage with Control-M is that I have re-engineered a monolithic script. The process I re-engineered was designed for printing invoices, specifically the invoices of EDP clients, which amounts to about eight million invoices per month.
To handle that scale with Control-M, I made changes by decomposing the monolithic script, which was made in shell scripting, into Control-M jobs, getting the complete workflow, a PDF, and transforming it into a Control-M workload. I do a lot of transformation from monolithic scripts or jobs that can be transformed into workloads within Control-M.
What is most valuable?
The best features Control-M offers include cross-platform dependency management, which is interesting because a job on the mainframe depends on a file arriving from a Unix system that, in turn, depends on a Windows process completing, and Control-M handles that heterogeneous dependency chain natively.
A time when this feature really made a difference for my team was when we had several workloads that are dependent on each other, using different platforms, and that interconnection between those platforms is really relevant to the whole process. There are more features that add value to Control-M, such as the calendar and condition system, which is really powerful to schedule almost to perfection many workloads that are critical for the business, whether in energy, insurance, banking, etc., because it maintains the logic.
Using the conditions allows me to create the re-engineering process that I have mentioned, which depends not only on the conditions but allows everything to run smoothly and on time. Tasks that in the original monolithic script would take about two hours now take at least fifty percent less time because it is more efficiently designed. The time savings were enabled mostly by parallelization, but not only that; I can adjust several aspects.
Control-M has positively impacted my organization because if some condition fails or if a calendar is incorrectly defined, a simple error in a condition can stop a critical workload, stop invoicing, and stop files that should go to the banking system.
What needs improvement?
Control-M can be improved with better integration with modern DevOps toolchains, as while it has made strides with APIs and the automation API, integration with tools such as JIRA and ServiceNow could be more seamless out of the box.
There is also a knowledge barrier that BMC should be aware of; Control-M has a steep learning curve for deep operational mastery, where basic administration is fairly accessible, but truly understanding the platform takes months to years for a new person, and BMC could invest more in advanced training and certification paths beyond the basics.
For how long have I used the solution?
I have been using Control-M for more than twenty years, since around 1996.
What do I think about the stability of the solution?
Control-M is stable in my experience. I have worked with Control-M environments processing tens of thousands of jobs, and currently, we have around six thousand jobs in the energy company.
What do I think about the scalability of the solution?
Control-M is used quite extensively; we execute around six thousand jobs a day, serving around seventy to eighty applications, and it is always growing, also serving many DevOps teams.
How are customer service and support?
BMC support is generally competent for standard issues.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Before choosing Control-M, I always worked with it and know alternatives such as TWS, Autosys, and other platforms similar to Control-M, but I have never worked with them.
What was our ROI?
The ROI of Control-M in critical infrastructure is less about percentage savings and more about what does not fail, such as when a national payment system opens every morning on time, or when millions of transactions are processed without a missed dependency.
What's my experience with pricing, setup cost, and licensing?
Control-M has premium pricing, which is justified for enterprise-scale operations, as we are paying for a platform with decades of maturity, proven reliability, and the capacity to handle complex orchestration scenarios that simpler tools cannot manage.
What other advice do I have?
I have always worked with Control-M, first on banking systems and then on energy systems, and though I worked with other systems, Control-M was always present. We have many users in many different roles; there are maybe four or five administration roles along with operation roles.
The biggest lesson I have learned from using Control-M is that it makes your life easier in dealing with batch processing, whether on mainframe or distributed servers, allowing you to define everything the way you want. I advise others looking into using Control-M to invest in people, not just the tool, emphasizing that a well-configured Control-M environment with experienced operators is essential for reliability.
Integrating Control-M with technologies for our data ops and DevOps processes can be difficult as technologies change. I would rate this review nine out of ten overall.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Cosmin A.
Reliable tool for job automation
Reviewed on Mar 12, 2026
Review provided by G2
What do you like best about the product?
I like how it makes it much easier to monitor jobs, manage dependencies, and identify issues
What do you dislike about the product?
The interface can be sometimes a little bit complex for new users
What problems is the product solving and how is that benefiting you?
It helps manage and automate jobs across different systems. The main benefit would be that everything is in one place so it’s much easier to monitor jobs and see if something goes wrong
Atima A.
Powerful Automation with a Complex Interface
Reviewed on Mar 09, 2026
Review provided by G2
What do you like best about the product?
I like Control-M for its centralized job scheduling, reliable dependency management, and clear monitoring of workflows. It provides reliable job dependencies and useful alerts, and I appreciate the centralized workflows monitoring.
What do you dislike about the product?
The interface can be complex, and troubleshooting failed jobs sometimes requires too many steps. Configuration and maintenance can also be time-consuming. The interface is complex and navigation can be slow when finding job details or troubleshooting failures.
What problems is the product solving and how is that benefiting you?
I use Control-M to automate job scheduling and workflow management, reducing manual intervention and improving reliability. It centralizes job scheduling, manages dependencies, and monitors workflows, ensuring processes run reliably.
Abhishek Kumar Singh
Automation has transformed daily job scheduling and consistently saves hours per batch run
Reviewed on Feb 28, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for Control-M is scheduling jobs and maintaining the EM server and the Control-M server, along with giving support to the asset team on troubleshooting of job failures.
We typically schedule OS jobs and AFT jobs in Control-M, and we also have SAP jobs and Informatica jobs running on Control-M.
Regarding my main use cases with Control-M, we are scheduling jobs for the asset team and maintaining the architecture of Control-M.
What is most valuable?
Control-M offers several great features, with scheduling jobs being a very good feature, while the GUI feature is user-friendly and makes scheduling jobs very easy, saving a lot of time compared to other scheduling tools.
The GUI helps my team day-to-day by making job scheduling very easy, as we can use planning tabs or the back-end of the job through drag and drop, and after adding a few job details, we are ready to proceed. The monitoring tab is also very useful for monitoring daily or scheduled jobs, and the forecast feature is excellent for predicting how jobs will execute in the future.
The reporting feature serves us well for extracting reports on job executions and past executions.
Control-M has positively impacted our organization as we have saved a lot of time and money by utilizing its features, which we found to be very convenient compared to other workload automation tools.
We are saving a lot of time as earlier we had numerous manual activities that usually took four to five hours to perform, and since automating those tasks in Control-M, we now execute them within two hours, effectively saving two hours per batch execution.
What needs improvement?
The reporting feature has limitations with job execution, and I believe there should be integration with Power BI or any visualization tool to provide a detailed summary of each job instance on a single dashboard.
Control-M could have more types of jobs that could be integrated with it, but for now, the features are adequate.
For how long have I used the solution?
I have been using Control-M for the last eight years.
What do I think about the stability of the solution?
Control-M is stable in both production and non-production environments.
What do I think about the scalability of the solution?
Control-M's scalability is convenient, easy to use, and flexible with various integrations.
How are customer service and support?
The customer support for Control-M is convenient, providing us with 24/7 assistance for architecture and job execution issues.
How would you rate customer service and support?
Negative
Which solution did I use previously and why did I switch?
Previously, we were using AutoSys, but we found AutoSys not user-friendly based on feedback from the asset team, prompting us to switch to Control-M, which is better suited for our organization.
How was the initial setup?
Control-M is deployed in my organization on a private cloud.
We use AWS as our cloud provider.
What about the implementation team?
We require around five to six staff for the deployment and maintenance of Control-M, all of whom are Control-M admins assisting in deploying Control-M for various asset teams and maintaining their services.
What was our ROI?
We have seen a return on investment due to money and time saved as we automate tasks in Control-M, allowing us to reduce staff numbers as well.
What's my experience with pricing, setup cost, and licensing?
The pricing for Control-M is genuinely fair compared to other workload automation tools in the market, and its features add value, making us satisfied with its pricing structure.
Which other solutions did I evaluate?
We evaluated AutoSys before choosing Control-M as our solution.
What other advice do I have?
The biggest lesson I have learned from using Control-M is that automation is very convenient, with workload automation and job scheduling being easy and maintaining jobs in Control-M being very manageable.
My advice for others considering Control-M is that it is definitely a reliable option since it is convenient, flexible, and stable.
Control-M is extensively used as we have deployed it for many asset teams, and we plan to increase its usage as we are in discussions with different teams to migrate their manual activities into Control-M.
I would rate this review as a nine out of ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Dan Dernoll
Workflow management has become highly reliable and has saved significant scheduling time
Reviewed on Feb 26, 2026
Review provided by PeerSpot
What is our primary use case?
My use case for Control-M includes file transfer and workload balancing, but it is mostly focused on workflow management.
What is most valuable?
I love Control-M 's reliability and ease of use. It offers ease of adaptability for upgrades, and the GUI features have been enhanced for better readability. Their reporting improvements are notable, and they developed software that helps manage licensing effectively.
Control-M is incredibly reliable, rarely having issues from an administrative standpoint. The high stability means I am rarely surprised by problems. Additionally, time-saving is significant; previously, scheduling involved paper and took much longer. Control-M reduced the scheduling time drastically, taking only about five to ten minutes to add a new job to the workflow.
What needs improvement?
One area that has room for improvement is support. Early on, support was fabulous, with efficient issue resolution processes. However, since approximately 2015, support has been lackluster, relying too much on email. I would suggest a return to hands-on support engagement.
Aside from the support aspect, I cannot think of anything else that needs improvement.
For how long have I used the solution?
I started using Control-M in 2000.
What do I think about the stability of the solution?
Regarding stability, I would give Control-M a ten. Control-M is such a reliable piece of software. I rarely, if ever, have to do anything from an administrative point of view. When someone calls me with a Control-M problem, it surprises me as it is mostly stable.
What do I think about the scalability of the solution?
Control-M is scalable. The easiest way to express this is regarding licensing; as you are scaling up, you should keep up with your licensing. BMC does an annual review, and your account representative will reach out for a licensing software run that generates a report using all Control-M components.
How are customer service and support?
From one to ten, with ten being the best, I would rate their technical support about a seven.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Concerning Control-M, I previously started out with scheduling package software back in the old Uccel, which was bought by Computer Associates and called CA-7.
How was the initial setup?
Installing Control-M was really quite easy; you simply download it and do the installation. The biggest thing is the front-end work prior to installation, such as deciding which database you will use.
What about the implementation team?
My relationship with BMC is probably transactional. I rarely have to reach out to them.
The BMC service team could be better at being more involved in mapping out migration strategies, though they have a really good process called AMIGO that yields positive outcomes.
What was our ROI?
In terms of time savings with Control-M, I spend maybe thirty minutes a week, if that, on Control-M compared to other software products I have dealt with.
What's my experience with pricing, setup cost, and licensing?
I did not have much engagement in the pricing area.
Which other solutions did I evaluate?
Regarding other solutions, Redwood was the only one I was familiar with. I saw a demo on that before 2010 when management was looking at maybe replacing Control-M.
What other advice do I have?
Deployment is on a Windows platform in a high availability environment.
I would recommend Control-M to others looking to implement it, but it is essential to ensure it fits your environment, so doing a proof of concept is always beneficial.