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
Buyer guide
Gain valuable insights from real users who purchased this product, powered by PeerSpot.
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 simplifies application and data workflow orchestration on hybrid environments, from mainframe to multi-cloud, making it easy to build, define, schedule, manage and monitor production workflows, ensuring visibility and reliability and improving service level agreements (SLAs).
Control-M simplifies application and data workflow orchestration on hybrid environments, from mainframe to multi-cloud, making it easy to build, define, schedule, manage and monitor production workflows, ensuring visibility and reliability and improving service level agreements (SLAs).
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.
Introducing BMC Control-M, delivered by Amdocs Digital Engineering: Streamlined Workflow Orchestration for Your Business. This innovative solution merges Amdocs' digital prowess with BMC's Control-M, offering unparalleled workflow orchestration capabilities. From automating complex batch processes to managing modern workloads, Control-M optimizes operational efficiency and productivity. With intuitive interfaces and advanced scheduling features, businesses gain real-time insights to prioritize and monitor workflows seamlessly. A strategic partnership between Amdocs and BMC ensures rapid deployment and continuous optimization. Experience the transformative power of BMC Control-M, empowering your business with streamlined operations and accelerated digital initiatives in today's dynamic market landscape.
Customer reviews
Abhishek Singh
Automation has transformed job scheduling and now saves significant time for multiple teams
Reviewed on May 04, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for Control-M is serving as a Control-M admin user where I manage Control-M, schedule jobs in it, and maintain the execution and troubleshooting of the jobs.
A specific example of a job I schedule with Control-M includes scheduling SAP jobs, MFT jobs, FT jobs, OS jobs, and Informatica jobs. I schedule many jobs on Control-M for different asset teams.
I have automated many things that were running on Jenkins to Control-M and deployed many automation parts for the scheduling team and admin team into the Control-M domain.
What is most valuable?
The best features that Control-M offers in my experience include a very easy scheduling component, a highly interactive GUI interface, and a variety of job types that I had never seen in different tools, including competitor tools of Control-M, such as AutoSys, TWS, Tivoli, or Dollar Universe. Control-M is a very easy tool, and it is easy to learn and easy to deploy.
While the scheduling is easy and the GUI is interactive, I find that the setting of jobs and setting up a feature is very easy, and the deployment and promotion of jobs is very straightforward in Control-M.
Control-M has positively impacted my organization by helping us automate many manual things specific to the development team.
The main positive impact of Control-M includes time savings; we have automated many manual things that usually take six to seven hours, and now it is taking less than thirty minutes to one hour. We have reduced our time by almost fifty percent to eighty percent.
What needs improvement?
Control-M can be improved with a dashboard that should show the job execution time, output, and execution time, including start time and end time, for at least a year, so we could monitor everything on a single dashboard, similar to what can be created on Power BI, which could be integrated with Control-M.
While the functionality of Control-M is very easy already, there is not much to do in the feature part, but the dashboard part showing the Control-M backend could be improved.
For how long have I used the solution?
I have been using Control-M for ten years.
What do I think about the stability of the solution?
In my experience, Control-M is very stable.
What do I think about the scalability of the solution?
Control-M's scalability has been good, as it has met my organization's needs as we have grown; the load balancer and load scheduling are very fine.
How are customer service and support?
The customer support for Control-M is very efficient and very fast.
Which solution did I use previously and why did I switch?
Previously, we were using AutoSys, but we switched to Control-M because AutoSys is more difficult than Control-M, primarily because the GUI is very interactive in Control-M.
What was our ROI?
I have seen a return on investment from Control-M, which includes it being a money-saver and a time-saver.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for Control-M has shown that compared to different scheduling tools, Control-M is definitely a cheaper option, and the licensing part is actually very convenient compared to other tools.
Which other solutions did I evaluate?
Before choosing Control-M, we evaluated other options including Dollar Universe, TWS Tivoli, and AutoSys, and then we decided to move to Control-M.
What other advice do I have?
Around one thousand users are using Control-M in my organization, with most of them coming from asset teams or different application teams, while around one hundred are from scheduling, operations, and administration.
I require about ten to fifteen staff specifically for the deployment and maintenance of Control-M, and their roles include consultant, scheduler, or administrator.
Control-M is currently used very extensively in my organization, and we do have plans to bring different asset teams onboard on Control-M, as we are helping them with ideas and features of Control-M.
The biggest lesson I have learned from using Control-M is that automation is very easy, and we can deploy almost anything into Control-M.
Integrating Control-M with technologies for my DataOps and DevOps processes has been easy, particularly with AWS and different Linux platforms.
It has not been a specific challenge to integrate Control-M with those different Linux platforms or other technologies, as Control-M already has a feature to integrate multiple types of jobs, making it easy.
My advice to others looking into using Control-M is that I would definitely suggest it because its features are very good.
I have given Control-M an overall rating of eight 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)
Himanshu Mohapatra
Orchestration has streamlined enterprise workflows and consolidates complex job scheduling
Reviewed on Apr 28, 2026
Review from a verified AWS customer
What is our primary use case?
I primarily use Control-M for scheduling jobs for scripts, batch scripts, and Linux scripts. Most of the writing involves service restarts on servers.
For data ops and DevOps processes, the requirement involves integration processes that need to be scheduled in Control-M , allowing management of cyclic processes for integration and continuous execution.
For building, scheduling, and managing production workflows, access is available through the URL or from the client software, Control-M Configuration Manager.
Control-M has made it easier to create workflows for both cloud and on-premises environments with features such as drag and drop functionality. This makes it simpler for users to create jobs and integrate them with dependent jobs.
Control-M has helped consolidate job scheduler tools with features such as SMS and mail capabilities, which other scheduler tools do not provide.
What is most valuable?
The best features of Control-M are particularly effective for Windows scripts and Windows servers, mainly for service restarts.
What is most appreciated about Control-M is that it is easy and reliable. Jobs that have been created can be accessed through the front end URL, where operations such as hold, release, and execution can be managed entirely from the user GUI front end.
Workflow orchestration is important for data ops and DevOps tasks as it makes scheduling scripts and managing various aspects of operations much easier through a single screen.
What needs improvement?
There are areas for improvement in Control-M as it carries some vulnerability points that could be fixed in any version, or it could be made easier for organizations to repeatedly install or update new patches with more stable versions.
For how long have I used the solution?
I have been using Control-M for four years.
What do I think about the stability of the solution?
On a scale from one to ten, with ten being the best, Control-M's stability is assessed as a solid product at approximately eight or nine. BMC support provides robust backing, with new patches arriving daily and being integrated with previous versions to replace outdated updates and fix bugs while unlocking more features. No stability issues have been noticed during the four years of use.
What do I think about the scalability of the solution?
Regarding scalability, based on the features and how they help with day-to-day tasks, Control-M can be considered scalable.
How are customer service and support?
In terms of technical support, the focus involves creating scripts for service restarts on particular servers with the main target of providing support for automation services, automation management, job failure management, and managing the agent package and Control-M package.
How was the initial setup?
The deployment of Control-M is easier than other tools. There are no critical tasks or activities required to deploy on the server; it simply involves setup and installation on the server with the tool ready to use immediately.
What's my experience with pricing, setup cost, and licensing?
Regarding pricing, Control-M is not the cheaper option. License renewal is based on active jobs in a year, but it is cost effective. More features are provided compared to other tools at the same price.
Which other solutions did I evaluate?
When comparing Control-M with other solutions such as ActiveBatch , JAMS , and IBM, Control-M offers easier manageable operations for hold, release, and execution, which can be managed directly from its front-end URL. In its configuration tools where jobs are created, there are no difficulties encountered. Unlike other tools where dependency tools and jobs must be mentioned separately, Control-M provides direct drag and drop functionality with arrows. This is much easier than other tools such as IBM Task Scheduler or Jenkins .
What other advice do I have?
Approximately 2,000 to 3,000 people use Control-M, including users from Axis Bank where all employees are using Control-M.
Control-M is recommended to other users by providing them a demo and showing them the uses, which helps them understand the benefits and features that Control-M provides that cannot be obtained from other tools. This allows them to rely on Control-M for their day-to-day tasks.
One point is deducted from the overall rating because Control-M carries some vulnerability points. The overall rating for Control-M is nine out of ten.
Md Saklen
Centralized workflows have improved batch scheduling and visibility with AI-driven monitoring
Reviewed on Apr 22, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for Control-M is to process batch workloads. We have multiple batch scripts which need to be run at a particular scheduled time, and we use Control-M for MFT and certain kinds of services where we need files to transfer to the client location.
For batch workload automation, we have SSIS packages and Microsoft SQL packages which need to be executed through the batch file. For MFT , we have Excel files which need to be transferred from source to destination.
What is most valuable?
The best features Control-M offers are better visibility through the dashboard and an AI-enabled system where users can ask their workflow details through chatting with AI.
The dashboard definitely helps to get better visibility because checking failures one by one by visiting the job is difficult. We are getting the exact figures through the dashboard.
Control-M has impacted my organization positively by improving the SLA and the overall workflow. Timely, we are receiving triggers for daily notifications due to the SLA improvement, and such type of information is useful.
What needs improvement?
In areas where we need a notification alert whenever the agent goes down, that is something that can be improved so people and clients can be aware and can take immediate action to remediate agent-related issues.
They can work on the integration part where Azure storage and Azure-related things can be integrated seamlessly with Control-M.
For how long have I used the solution?
I have been using Control-M for the last two years.
What other advice do I have?
Control-M is a great platform to centralize all the workflows. I would rate this product a 9.
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?
Prodriguez Rodriguez
Reliable scheduling has supported enterprise-wide monitoring and automated alert handling
Reviewed on Apr 17, 2026
Review provided by PeerSpot
What is our primary use case?
My main use case for Control-M is that my team is in charge of all the alerting and monitoring, as well as the scheduling and creation of all schedules within Control-M .
The scheduling my team creates with Control-M serves all the IT audience within the company, so we have a mix of everything. Any need from developers, database administrators, or anyone from the infrastructure or development teams is handled, such as transferring files or updating databases. We deal with all requests within the company related to scheduling.
Within my team, we have around 10 people using Control-M who are focused on monitoring and reacting to alerts, as well as creating all schedules and doing all scheduling work. Beyond that, we have developers, DBAs, and others who check Control-M to review the performance of their jobs and logs. We have around 50 people total, though I don't know the exact number.
What is most valuable?
The best features Control-M offers are the stability and ease of use.
The interface of Control-M is easy to use and it is a very stable and reliable application. Control-M has a very high positive impact on my organization as it is a reliable tool that is very stable. We usually don't have issues related to the application itself, so there is a very high impact.
What needs improvement?
Control-M can be improved by including more options for automating things from an alerting handling perspective.
Reporting features are a field that we would like to have more statistics about, including jobs, usage, and errors. We definitely would also like to have more options to integrate Control-M with other applications such as JSM, ServiceNow , OmniCenter, or other monitoring tools that can provide information from Control-M. There is always room for improvement for any application.
It is easy in theory, but I find it challenging to integrate Control-M with technologies for my data ops and DevOps processes as changes occur. There have been a few efforts to integrate Control-M with other applications like Ansible , JSM, and OmniCenter, and it has been very challenging. From a DevOps perspective, I am not aware of any efforts, so I don't have information about that. However, related to the ones that I mentioned, it has been very challenging because there are not many options to integrate with Control-M. I'm not sure if this is due to a lack of training or application knowledge from our side or if it is something that the application itself is not providing.
For how long have I used the solution?
I have been in my current field for 20 years.
What do I think about the stability of the solution?
Control-M is stable.
What do I think about the scalability of the solution?
Its scalability is challenging.
How are customer service and support?
Control-M has very good customer support.
What was our ROI?
We don't have a metric for return on investment from a Control-M perspective. We are expecting to see some of that if at some point Control-M starts integrating AI features and AI functions into the application.
What other advice do I have?
The biggest lesson I have learned from using Control-M is the importance of having a reliable and stable scheduler.
My advice for others looking into using Control-M is that training is key to learning how Control-M works behind the scenes and in the scheduling part. I also advise looking for stability and implementing the HA environment.
I would rate Control-M an eight on a scale of one to ten.
reviewer2802231
Automation has streamlined cross‑platform workloads and reduces manual effort for data pipelines
Reviewed on Apr 14, 2026
Review from a verified AWS customer
What is our primary use case?
The core purpose of Control-M is automation, workload automation, and job scheduling. We use it for cross-platform services including clouds such as AWS and GCP , along with different databases. We are dependent on each service, which gives us a clear understanding of our architecture. Control-M is very easy to use and easy to monitor.
We migrated to Control-M from services including some databases and some cloud services.
We use different scripts with Control-M following standard scripting practices. We also follow the agents approach by installing agents to our targeted machines. Additionally, we use the UI, which is very good. We log in using SSO . Control-M makes it very easy for ETL jobs, data pipelines, and everything else.
What is most valuable?
The main features of Control-M are the UI and the monitoring part. It has a very comprehensive UI and monitoring system. Control-M agents are another valuable feature, allowing us to run jobs on the target machine easily across any machines. Enterprise-level support is also a very good feature.
We use different scripts with Control-M following standard scripting practices. We follow the agents approach by installing agents to our targeted machines. The UI is very good, and we log in using SSO .
Control-M has saved us a lot of time and effort. Previously, it reduced the human touch and manual work significantly. It has brought substantial changes to our organization.
What needs improvement?
Control-M is a very sophisticated tool overall. The main issue is that there are some RBAC issues related to improper access control. There is no clear role defined, though there are some operator and admin kinds of roles. Control-M should integrate some primitive roles or define them better. In short, there should be very minor permissions so that roles can be properly defined for users.
Another suggestion regarding Control-M is that there should be more automation APIs. Since we are mostly dependent on automation and do not rely heavily on the UI, we need additional automation APIs for triggering jobs, fetching status, and similar functions.
For how long have I used the solution?
I have been using Control-M for more than four years.
What do I think about the stability of the solution?
Control-M is very stable. During more than four years of use, it has remained reliable and stable. I would rate it 10 out of 10 for stability.
What do I think about the scalability of the solution?
Control-M has significant scalability. I would rate it 9 out of 10 for scalability.
How are customer service and support?
Technical support for Control-M is very good. The support team helps us considerably. Even when we were new to Control-M, they assisted us greatly with any integration issues or other concerns.
Which solution did I use previously and why did I switch?
Compared to other vendors, Control-M has many features that are very helpful. The features are defined rather than broad level. We know there are many other solutions in the market, but we were previously using Azure Data Factory. Control-M has significant advantages in that it is simple to use, and anyone can operate it.
Control-M requires maintenance, but very little. Maintenance for Control-M is easier compared to other solutions.
How was the initial setup?
The deployment of Control-M was easier, and we received support from the Control-M team. The deployment of Control-M took approximately one to two months.
What about the implementation team?
The deployment of Control-M was easier, and we received support from the Control-M team. The BMC service team helped us map out our migration strategy and served as our architects.
There were some challenges, but I can say the migration to Control-M was easy overall.
What was our ROI?
Control-M has reduced our work by more than 35%.
What's my experience with pricing, setup cost, and licensing?
Pricing for Control-M is at a medium level. I cannot say it is cheap or high.
Which other solutions did I evaluate?
I would recommend Control-M. We were also using Airflow , and there is a very significant difference in our workforce and environments when comparing the two solutions.
What other advice do I have?
I give Control-M an overall rating of 9 out of 10. More than 30 developers are using Control-M in our organization. My relationship with BMC is more transactional in nature. We are currently customers, and we plan to become partners.