Overview

Product video
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
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
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
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
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
Customer reviews
Modern workflow orchestration has empowered teams to own APIs, pipelines, and data operations
What is our primary use case?
What is most valuable?
What I like most about Control-M is the modernized API, which allows me to integrate with many other applications to create job flows using JSON. Application teams can own their own responsibility to create jobs instead of relying on a Control-M admin to create a job every time they need it.
What needs improvement?
Control-M should evolve into a more web-based SaaS level product, which they are looking into. They should improve the features that were available in Control-M localized installations. For example, if I have the server on-premises, more features are with the client, whereas with the web-based version they moved to now, many features have been missing that we expect should be coming as well. Configuration and CCM are missing most of the features that are in the on-premises version. Those features should be coming very soon, and that would be the best improvement they could bring.
Additionally, auto deployments and patch management always require manual work, so those should be coming through auto deployment, which would help significantly. Software upgrades and similar processes should be more optimized.
For how long have I used the solution?
I have been using Control-M since at least 2014, which is about 13 years now.
What do I think about the stability of the solution?
Regarding stability, I would say it is based on the environment. For my bank, I never had an issue with crashing or anything; the performance was good.
What do I think about the scalability of the solution?
Scalability is easy for me. It is all based on the plan regarding how many jobs I am going to use. I do not see any complications with scalability.
How are customer service and support?
I have contacted technical support and we raise cases with them before every single upgrade or migration. We have a method of procedure plan where we check with them about recommendations. Most of the time, BMC does not recommend against proceeding, and they say I am good to go with it.
When there is an issue, the quality of support for a P1 case is good, but the solution they provide can be complicated sometimes, which takes time for them to investigate. Then they have to engage their developer team. Sometimes I would have already known that this is not solvable and only the developer team can advise on it, but they do not take it immediately. They take their own time to provide the solution, meaning they take one or two additional hours. If I were to put support on a scale from one to ten, I would give Control-M support a score of seven.
Which solution did I use previously and why did I switch?
I have used alternatives like Redwood and some other internal tool called Insights software. Comparing Control-M to Redwood, Control-M is better; however, Redwood has a simpler tier level architecture than Control-M.
I did not migrate from Redwood to BMC; I worked on that software at my previous company where both software were used. AutoSys has also been used there. I have seen developers compare AutoSys to Control-M.
Migrating from other software does not require much work from my side; it is easier even for the developers. Control-M requires a little understanding of how these things work. For example, when the application person reaches out to me, they need to understand first how job creation works and how their job executes on their agent, and it is not more transparent for them. I have to conduct a learning session to help them understand these things, and those aspects are complicated in Control-M. However, Control-M is more optimized in that part. When they understand the tool, they prefer Control-M to any other solution.
How was the initial setup?
When I joined my current bank, Control-M was already deployed but with a very old version. I took care of upgrading it to the very latest version. We were ten years behind, and there was no support, but I managed to get it upgraded to the latest version.
The upgrade was challenging at first. The OS flavors were very old, which Control-M does not support with the latest version. We had to plan carefully, thinking about how we would move to which version, and then we did a parallel build in Red Hat to move it. It was a very comprehensive plan we had to develop. However, it went well. When I am more experienced with the tool, I know how to execute the migration properly.
What about the implementation team?
When it comes to deployment and maintenance, maintenance stays with the administration team, which is my team. We currently work as a core of five people for the deployments. When it comes from the application team to create a job, workflows, or whatever they need planned, it involves four to five people.
What's my experience with pricing, setup cost, and licensing?
Regarding pricing, BMC is a little costlier. They need to come down with execution-based pricing. For my understanding, BMC charges based on executions, whereas Redwood charges or AutoSys charges based on successful completion. BMC is a little higher on that.
What other advice do I have?
Integrating with technologies for my DataOps and DevOps processes as things change is easy. We use DevOps and data pipelines related to Azure data pipelines, and it has been easy for us because the latest version does have the support. We use our own application integrator developed by ourselves, so it was easier for us since we know the tool. My review rating for Control-M is ten out of ten.
Control_M Powerful Centralized Workload Orchestration with Strong Monitoring and Integrations
2. Dependency management – You can define complex job dependencies (time-based, file-based, application-based, event-based), making it reliable for enterprise workflows.
3. Strong monitoring and alerting – Operators can quickly identify failed jobs, receive notifications, and restart jobs without rerunning the entire workflow.
4. Wide integration support – It integrates with databases, ERP systems, cloud services, file transfers, ETL tools, and scripting languages, making it suitable for heterogeneous environments.
* Complex administration: Initial setup, upgrades, and maintenance often require experienced administrators.
* Older UI in some areas: Although BMC has modernized parts of the product, some screens and workflows can still feel dated compared to newer cloud-native tools.