Control-M Self-Hosted
Workflow orchestration has improved and simplifies database pipelines with helpful AI agents
What is our primary use case?
My main use case for Control-M is to connect it with my database and use it for projects and data pipelines.
A specific example of a workflow I connect with it is the database and the data pipeline for my projects. I use Control-M to schedule and coordinate those database and pipeline tasks. I store my full stack development data in the database and pipeline, set up security, and build my CI/CD integration flow.
Our main business use cases supported by Control-M are mostly in supply chain.
How has it helped my organization?
My impression of Control-M for giving business users visibility and control over their jobs is that it has been helpful. This is important for the organization because it helps with the easy flow of work.
My impression of Control-M for freeing up IT personnel to focus on essential operations is that it is a very good tool and really helpful. It is also very useful for the organization in focusing on the main business area.
Using Control-M has helped simplify, rather than complicate, creating and integrating data pipelines across on-premises and cloud technologies. Creating and integrating the flow is easier using Control-M.
It has had a positive impact by providing different features, such as agentic capabilities, which have been really useful.
Debugging faster using agentic capabilities is one of the main benefits. Having log summaries from that agent feature is another.
It has improved organizational work, such as enabling faster delivery and maintaining SLAs.
What is most valuable?
The best feature Control-M offers, based on my experience, is the database and pipeline support.
What is most useful in my CI/CD workflow is the agent and agentic agent capabilities.
Those agents have helped with my database and pipeline workflow so far, mostly in debugging and analyzing what the issue is. I get help there.
My view of the governance and security of Control-M's AI capabilities is that it is good. Guardrails have been added, and the responses it gives are very helpful.
Integrating with technologies for our DataOps and DevOps processes as things change is of easy to medium difficulty.
Of the Control-M Python client and the API, I have used only the API, and it is really good, with all the validations and controls that it has.
What needs improvement?
Control-M can be improved with a better UI flow, I believe.
The UI flow is all right, but I feel that responsiveness and other aspects of it can be improved.
The accuracy and reliability of Control-M's AI output is limited. It sometimes hallucinates a lot, but that can be improved.
For how long have I used the solution?
I have been using Control-M for almost a month.
What do I think about the stability of the solution?
It is stable. It is good.
What do I think about the scalability of the solution?
Around 100 to 200 users interact with Control-M in my organization. Their main roles are developers.
The solution is not extensively used at present, as it is only in the initial phase. I plan to increase usage, though I am not sure by how much, as we are at a very early stage of usage.
Five people use it, and they are developers.
Scalability is good, both vertical and horizontal.
How are customer service and support?
Customer support is quick, with faster replies. It is decent.
I would rate it eight.
How was the initial setup?
The initial setup took one hour.
What about the implementation team?
Around 15 developers in DevOps manage deployment and maintenance activities.
What's my experience with pricing, setup cost, and licensing?
I purchase directly.
It is easy. Pricing is decent. Licensing is okay.
What other advice do I have?
On a scale of 1 to 10, I would rate Control-M overall at nine.
My reason for giving a nine is that I find it useful, and its features are really good.
Agents can make the work easier and faster.
Control-M is good for easing the work that we do. It makes the work easier, simpler to understand, and faster to execute. I suggest it, and people can use it.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Automation has reduced time to production and simplifies building and monitoring workflows
What is our primary use case?
The main use case for Control-M is workload automation.
How has it helped my organization?
We are able to automate a lot for the client, and the time to production is reduced because of the automation and workflow building.
What is most valuable?
One of Control-M's best features is its quick integrations with many tools. It has positive integrations.
I find those helpful because it has so many inbuilt connectors, which make connectivity to any other tools very easy. It is quick, and we are able to integrate it with various tools, such as Apache Airflow and SAP, without having to customize it.
I would rate Control-M well for building, scheduling, managing, and monitoring production workflows.
Using Control-M makes it simpler to create, integrate, and automate data pipelines across on-premises and cloud technologies because it has a very easy UI to do that.
The UI makes it easier to automate everything.
What needs improvement?
I can't think of anything at the moment for how Control-M could be improved in its next release. One of the things is that the cost is a bit on the higher end.
For how long have I used the solution?
I have been using Control-M for around two to three years.
What do I think about the stability of the solution?
Control-M is stable.
Control-M is reliable because we are able to build the workflows very efficiently, and the connectivity with other systems makes it by far a very good tool to use.
What do I think about the scalability of the solution?
Scalability-wise, Control-M is good. It has pretty decent features on that part, and we are able to install quite a lot of agents in it.
In our production system, we have 300 odd agents installed, and the connectivity is flawless. There are no issues with that. Scalability-wise, we do not face any issues, and whenever we have to run more workload, it runs fine.
How are customer service and support?
Customer service and technical support are good. Customer service is very prompt, they always provide details whenever we request them, and the documentation is also very good.
On a scale of 1 to 10, with 1 being the worst and 10 being the best, I would give their customer service and technical support a nine.
What was our ROI?
I see a return on investment with Control-M.
Because Control-M automates a lot of workflows for us, and the time to execution for those improves our efficiency, the return on investment is there and cost saving is there.
Working with Control-M helps reduce the total cost of ownership overall.
What's my experience with pricing, setup cost, and licensing?
My experience with the pricing and the setup cost is that it is on the higher side.
What other advice do I have?
I do not think the Control-M that we are using was purchased through the AWS Marketplace. I think it is enterprise level, so it was bought directly from BMC.
On a scale of 1 to 10, with 1 being the worst and 10 being the best, I would rate Control-M overall a nine.
My one piece of advice for other organizations considering Control-M is to consider the cost of implementing the solution. However, I think that at the enterprise level, there are further deals they bunch in with different BMC products as well, so that should be good from the organization's perspective.
Integrated workflows have unified hybrid data pipelines and simplify audit-ready governance
What is our primary use case?
We use Control-M for workflow automation across a hybrid multi-cloud IT infrastructure, legacy ERP systems, and modern open-source technologies.
As a services industry company, we need to keep up with the speed of AI, because we also need to give our clients AI perspectives. From the internal IT perspective, we are customer zero. We implement things from our end, showcase them to our clients, and then they get adopted in the different client environments. We are doing very well in our AI journey.
We are currently adopting cloud workloads. Until now, all the legacy workloads have been running, including the .NET part, OS jobs, DB jobs, and SAP jobs, which directly use Control-M right now. We are now adopting cloud-native workloads and then progressing further to ML. No ML workload is running at the moment. However, some aspects of ML are running, such as Python jobs that provide some ML aspects, not in a native form, and we use them in some other form.
Orchestration is one part of how Control-M contributes to our AI governance requirements, because we also have agents deployed as an orchestrated tool to take up the work assigned to them and fulfill their purpose.
We have self-service portals which we expose to our application teams, and they use these portals to request some of the work done by the admin team. They can do some of the work themselves, and those jobs are piled up in Control-M. The application programs are based on Control-M, and Control-M picks up the job, executes it, and provides the requirement settlement to the end users. That is how we mainly use it at this moment.
We manage the coordination between SAP batch jobs and non-SAP workflows. As part of our complex hybrid IT environment, we need to juggle between SAP and non-SAP, because we expect some data from SAP.
Since SAP is not very GUI friendly or the data is in a different format, we generally handle it on the non-SAP side. We use the job chains concept in Control-M for mixing SAP and non-SAP workloads, such as for data movement and the data lineage part.
We orchestrate workloads across multiple environments, including on-prem, virtual, and cloud.
How has it helped my organization?
Handling complex data pipelines is one use case we are looking at, because data movement across clouds or across different data centers is always a problem, since the connectivity is not there. Control-M serves as a major orchestration layer. We move data around between different places and get complete observability and the complete data lineage perspective. It helps a lot from that perspective.
Control-M is the best technology when it comes to building, scheduling, managing, and monitoring workflows. That is the power of Control-M. It is very good. There is no problem for any new team member to walk in and learn the product. It is pretty easy, and the learning curve is very easy compared to other products. We have offloaded the complete operations of Control-M to our L1 team. They are not from a technical background, but they are still able to manage the complete operations of it. That is the power of the product, because if the product were so complex, we would not be able to run it and would need a specialist.
We have specialists, but not in my operations team. I have them in my technical and engineering team.
To run Control-M for this large scale of users and these kinds of applications, we manage almost 6,000 plus jobs. You can understand how often these jobs and their schedules change. There is a release, and all of this has to be managed by a team. Considering this much application support, we may need 20 plus or 30 plus resources just to manage and run Control-M operations.
We are doing it with a very minimal number, fewer than 10, and these are our L1 resources. They also get occupied with some of the technical work, and we reduce our burden on operations and focus mainly on the engineering perspective.
What is most valuable?
The best features we are using and liking most are the integrated orchestration and the compliance and governance part. We run finance-related applications, and I am from internal IT. We run a lot of finance workloads and we get audited often on the workflow automations, because this happens behind the applications.
Control-M has helped us get a lot of visibility from the audit perspective and the governance aspect. We do not have to spend much time telling the audit teams what we have, because we have ready-made information available in Control-M to provide the details the auditors have been requesting. That is another thing I find attractive about this solution.
Before we were using Control-M, we were using a Redwood product called CPS. It is from SAP, actually. SAP acquired it and we were using it. During the COVID times, we moved away from it.
My role is technical mentor and infrastructure solution architect, which generally involves looking at the infrastructure feasibility and the automation governance from the application side. I implement the same things and do feasibility checks. We do the same thing in an infrastructure.
The orchestration, the automation, and the stability are the more important things which I need to mention. We do not have bigger outages or anything of that sort, which we had problems with in the very early tool. The stack is pretty much cool and stable, so we do not want to put effort into maintaining the tool, but just to leverage what the tool has to provide. That is another thing I can tell you.
Integrating Control-M with technologies for our DataOps and DevOps processes is easy.
What needs improvement?
The challenge we are facing when orchestrating Kubernetes jobs or cloud-native workflows with Control-M is mainly from the security perspective, because of the strict governance and controls from my company side. If you want to run any of your agents, it requires bi-directional communication between the Control-M server and the agent at this moment. That is what I understand from them.
In some places, for example, if I place my agent on my cloud, such as Azure Kubernetes, I need to have bi-directional communication from Azure Kubernetes, which might not be allowed these days because of the security controls. We have communicated and highlighted this to our Control-M team, saying that it may not be feasible for the whole company to provide full-fledged bi-directional communication. Instead, you can just proxy it or forward the traffic to your different cloud provider or different environment protected by firewalls. We are having some challenges adopting some of the cloud-native workloads because of these things.
We are still seeking some of our security approvals with respect to this, because generally any traffic inwards to the corporate network is disallowed, including from the cloud. Apart from normal HTTPS and HTTP, DB connectivity from my cloud to my on-prem is generally not allowed. That kind of communication is required for the Control-M agent to talk to the Control-M server. We have a problem with this at the moment, and we are trying to resolve it.
At the same time, we are also exploring the SaaS part of it, but that is another challenge for us, though we have started exploring. We got the demo tenant, and we are trying to do some of our POCs on that, to see whether the security challenge posed by our company can be accommodated in the SaaS version. We are trying to do that.
At this moment, I do not see anything which is missing. We are not leveraging most of the features, as I understand it. We have the file transfer capability and many other capabilities. Because of our use case, we are limited to using some of the OS jobs, DB jobs, and SAP jobs at this moment. We are planning to explore cloud-native, then Kubernetes, and then AI. That is our roadmap at this moment. I do not have any feature request or anything pending at BMC.
Comparing Control-M to other solutions or vendors always comes back to what I told you earlier about the features I like most. The integrated orchestration part is where we have SAP and non-SAP, DB, and the open-source technologies, which we use in all the formats. We are able to stitch all the application requirements and data movements across all these platforms. However, I know about one tool we were using prior to Control-M, which does not have this flexibility. Stitching across or cutting across multiple technologies is always a bigger problem.
From the automation perspective, we have built an in-house tool which helps the application teams or the business teams trigger jobs based on their needs. We use the Control-M APIs, which the product uses internally for scheduling, running, and other functions. We use those same APIs and expose them to our in-house applications, providing an interface for our business teams to trigger jobs as and when they need. That is the self-service portal I told you about earlier.
That kind of flexibility was not there in the earlier tool. You have to come to the tool and do it, and for some reasons, we cannot give access to our tools. So we provide simplified dashboards or screens with access controls.
That was the main problem we had with Control-M. If you ask me what the challenge is, I remember one now, which is the integration with the external CMDB, Configuration Management Databases. For example, we now have 300 plus applications running and hosted within Control-M. I cannot give the whole team access to Control-M, because their jobs and workloads are all different. I need to provide 300 groups with different logins or different ways to communicate, and they should see only their jobs. That was not present in Control-M when we were looking at the options a year back.
The lack of external integration with CMDBs is the reason we have built our own layer, our own self-service portal on top of it. We integrate our CMDB from our wrapper service, and then we call your API and do the Control-M work. That is how we are doing it right now. Because that particular external integration is not there, we are just doing it with our self-service portal at this moment.
That is one challenge we have, the external integration with the CMDB, but since the automation APIs are available, we are making use of them and getting around that challenge at this moment. It would be good to have external integration with CMDBs built into the system, so that we do not have to build and manage this particular system ourselves.
For how long have I used the solution?
I have been working with Control-M for more than six years now.
What do I think about the stability of the solution?
The solution does require maintenance, but the complexity is very low. It is very easy to maintain, and it is stable. It is pretty good compared to the other tools which I have used.
Stability is one of the main reasons I rate Control-M highly, because my team does not have to spend a lot of time on the stability part. Once it has been set up, the product is very stable, apart from the external ecosystem where it runs, such as VMs or the other ecosystem we have, and that is where the challenge is. As a product, I do not see a bug in the product, frequent hangs, or unexplainable outages. I am not seeing anything like that with Control-M right now.
As we speak, we are doing a migration from our VMs to physical servers, because we are exiting VMware and moving to physical and similar machines at this moment. Previously, we were running Control-M on VMware, and now we are moving to physical servers. Some cutovers are planned for today, and I am still talking to people about them, which shows how much stability I have in my team. That is very good.
I can say Control-M's stability is 98% or more. Maybe you can put 99%. I just keep that 1% with me.
What do I think about the scalability of the solution?
The platform admins number fewer than 10. The business application owners number 1000 plus. They have visibility into the systems. They get a read-only version of their jobs, and they can look at the monitoring console and see whether their jobs are running. They can see the logs and their schedule, but they cannot make schedule changes or any changes on the platform side. So the platform side is fewer than 10, and the users might be more than 1000 plus.
I would rate scalability nine out of 10. It is pretty much able to run. I think we run more than 10K jobs, from what I understand of the overall workloads. It is able to manage them, and there is no problem. There are no unexplainable outages, no non-scheduled jobs being missed, and no schedules vanishing, which was very frequent in my earlier tool. Compared to the earlier tool, this is a big, big boon for us, from the stability perspective as well as the governance perspective.
You can put nine for Control-M's scalability.
How are customer service and support?
Technical support from Control-M gets a very good rating from me. It is excellent support. Even with any issues, they make sure that we get a technical solution, or if it cannot be technical, they come to a logical conclusion as well.
The technical support of Control-M is the best I have seen, because I have worked with more than 20 or 25 products, not only Control-M, but also other workloads, such as the cloud, cloud hosting providers, and many other products. Control-M has one of the most superlative supports I have seen.
I can say nine out of 10 for Control-M.
How was the initial setup?
The migration process with Control-M is very smooth. Currently, any upgrades or migrations are also smooth, because you have the option, and the migration approaches are built into the way the product has been designed. We have primary and secondary concepts. First we do it on the secondary, then we monitor it for some time, and then we fail over to the secondary and see whether things are working wherever we have upgraded. Then you have the option to do it on the primary.
The way Control-M has been built, the upgrades and migrations were all considered in the tool engineering itself. That is the best thing for adoption, as well as for any migration or upgrade that brings more features. That helps us adopt it.
If upgrades are difficult, people will be reluctant to move to the next versions because of the effort involved, and because of whether that effort is worth spending to get the features in the next version. Those kinds of things do not come to mind when we have a Control-M upgrade. We say, "This is pretty easy. We can go to the next versions and leverage the features." It is very smooth.
What was our ROI?
I think we can say more than 50% for sure. It is not 100%, maybe because we are not using it to the fullest of its features, whatever is available to us. That is also on us. We are yet to adopt the modern workloads as well as the cloud-native workloads because of the security controls we have. I would say more than 70%. That might be my ballpark number.
What's my experience with pricing, setup cost, and licensing?
Control-M's pricing is not cheap, and it is not expensive. I would say it is cost-effective. It is not cheap.
What other advice do I have?
I would rate Control-M overall 10 out of 10.
Integrated orchestration has simplified hybrid workflows and now provides stronger audit governance
What is our primary use case?
Our use case for Control-M is workflow automation across a hybrid multi-cloud IT infrastructure, legacy ERP systems, and modern open-source technologies.
Regarding how our organization has adapted to integration with AI or ML workloads with Control-M, we are from the services industry, so we need to keep up with the speed of AI because we also need to deliver AI perspectives to our clients. From the internal IT perspective, we are a kind of customer zero, where we implement things from our end and then showcase them to our clients, and they get adopted in the different client environments. We are very well into the AI journey.
Regarding MLOps workflows such as MLflow, SageMaker, Vertex, or Azure, we are in the journey of adopting cloud workloads at this moment. Until now, we have only run legacy workloads, including .NET, OS jobs, DB jobs, and SAP jobs, which we run directly using Control-M right now.
We are now adopting cloud-native workloads and then progressing to ML. No ML workload is running now, but some aspects of it are running. We have Python jobs that provide some ML aspects, but not in a native form. We are using them in some other form.
Control-M contributes to our AI governance requirements mainly through orchestration, which is one part, because we also have agents deployed as an orchestrated tool to take up the work assigned to them and do the job.
We have self-service portals exposed to our application teams, where they can request some of the work done by the admin team. They can do some of it themselves, and those jobs get piled up in Control-M. The application programs are based on Control-M, and then Control-M picks up that job, executes it, and provides that requirement fulfillment to the end users. That is the way we are mainly using it at this moment.
We manage the coordination between SAP batch jobs and non-SAP workflows, such as HANA BW, with Control-M. As part of our complex hybrid IT environment, we need to juggle between SAP and non-SAP, because we expect some data from SAP, and since SAP is not that GUI friendly or the data is in a different format, we generally do that work on the non-SAP side.
We use the job chains concept in Control-M for mixing SAP and non-SAP workloads. We use it for data movement and the data lineage part of it in that sense.
We have Control-M deployed in a hybrid model. Movement happens because we generally have data movements across this multi-cloud environment. Currently, since we are restricted to on-prem, the other data cloud is having a challenge right now, which we are trying to avoid with our Control-M SaaS at this moment.
We use Control-M to orchestrate workloads across multiple environments, including on-prem, virtual, and cloud.
How has it helped my organization?
Control-M helps us handle complex data pipelines, and that is one use case we are looking at, because data movement across clouds or across different data centers is always a problem, since you don't have the connectivity and other things. Control-M serves as a major orchestration layer. You move data between different places and get complete observability and complete data lineage from them. It helps a lot from that perspective.
Control-M helps us build, schedule, manage, and monitor workflows, and it is the best at the technology. That is the power of Control-M. It is very good. There is no problem for any new team member to walk in and learn the product. It is pretty easy, and compared to other tools, the learning curve is very easy.
We have offloaded the complete operations of Control-M to our L1 team. They don't have a technical background, but they are still able to manage the complete operations. That is the power of the product, because if the product were so complex, we would not be able to run it. We would need specialists. We have specialists, but not in my operations team. I have them in my technical and engineering team.
To run it for this large scale of users and these kinds of applications, we manage almost 6,000 plus jobs, so you can understand how often these jobs change and how their schedules change. There are releases, and all of this has to be managed by a team. Considering this much application support, we may need 20 or 30 plus resources just to manage and run the operations of the controller. We are doing it with a very minimal number, fewer than 10.
Those are our L1 resources, so they also get some technical exposure, and we reduce the burden on operations so we can focus mainly on the engineering perspective.
What is most valuable?
The best features we use and appreciate most in Control-M are the integrated orchestration and the compliance and governance capabilities. We run finance-related applications, and since I am from internal IT, we run a lot of finance work and get audited often on the workflow automations, because this happens behind the applications.
Control-M has given us a lot of visibility from the audit perspective and the governance aspect. We don't have to spend so much time telling the audit teams, "Okay, this is what we have." We have readymade things available in Control-M to provide the details auditors have been requesting. That is the other thing I find attractive about this solution.
Before we started using Control-M, we used a Redwood product called CPS. It is from SAP, actually. SAP acquired it, and we used that until we moved away from it during the COVID times.
My role is technical mentor and infrastructure solution architect, which generally means I look at infrastructure feasibility, automation governance, and all those things from the application side. I implement the same things and do the feasibility checks. We do the same thing for infrastructure. That is my role.
The orchestration, the automation, and the stability are the more important things I need to mention. We have not had any bigger outages or anything of that sort, which we had problems with in the earlier tool. The stack is pretty cool and stable, so we don't want to put effort into maintaining the tool, but rather leverage what the tool has to offer. That is another thing I can tell.
What needs improvement?
Orchestrating Kubernetes jobs or cloud-native workflows with Control-M presents some challenges and opportunities, and we are working through them. The major challenge we have is from the security perspective, because of the strict governance and controls from our company. If you want to run any of your agents, it requires bi-directional communication between the Control-M server and the agent at this moment. That is what I understand from them.
In some places, for example, if I place my agent on my cloud, such as Azure Kubernetes, I need bi-directional communication from Azure Kubernetes, which might not be allowed these days because of security controls. We have communicated and highlighted to our Control-M team that it may not be feasible for the company to provide full-fledged bi-directional communication. Instead, they could proxy it or forward the traffic to the different cloud provider or different environment protected by firewalls.
These are the things we are having some challenges with in adopting some of the cloud-native workloads. We are still seeking some of our security approvals, because generally any traffic inwards to the corporate network is disallowed, including from the cloud. Apart from normal HTTPS and HTTP, if you want DB connectivity from my cloud to my on-prem, that is generally not allowed. That kind of communication is required for the Control-M agent to talk to the Control-M server. That is where we have some problems at this moment, and we are trying to work through them.
At the same time, we are also exploring the SaaS part of it, but that is another challenge for us, though we have started exploring. We got the demo tenant, and we are trying to do some POCs on it to see whether the security challenges posed by our company can be accommodated in the SaaS version.
In my opinion, regarding areas in Control-M that have room for improvement, at this moment I don't see anything that is missing. We are not leveraging most of the features, as I understand it. We have the file transfer capability and many other capabilities. Because of our use case, we are destined to use some OS jobs, DB jobs, and SAP jobs at this moment. We are planning to explore cloud-native, then Kubernetes, and then AI. That is our roadmap at this moment. I don't have any feature request or anything pending with BMC.
That was the main problem we had with Control-M. If you ask me about challenges, I remember one now, which is the integration with an external CMDB, or Configuration Management Database. For example, we have 300 plus applications run and hosted within Control-M. I cannot give Control-M access to the whole team, because their jobs and workloads are all different. I need to provide 300 groups with different logins or different ways to communicate, and they should see only their own jobs.
Those capabilities were not present in Control-M when we were looking at options a year back: the external integration with CMDBs. That is the reason we built our own layer, our own self-service portal on top of it, which we integrate. We integrate our CMDB from our wrapper service, and then we call your API and do the Control-M work. That is how we are doing it right now.
Because that particular external integration is not there, we are doing it with our self-service portal at this moment. That is one challenge we have, the external integration with the CMDB. Since the automation APIs are available, we are making use of them and getting around that challenge at this moment. It would be good to have external integration with CMDBs built into the system, so you wouldn't need to manage and build this system for us.
For how long have I used the solution?
My experience with Control-M is more than six years now.
What do I think about the stability of the solution?
Stability is one of the main reasons I am still with Control-M, because my team doesn't have to spend a lot of time on the stability part. Once it has been set up, the product is very stable, apart from the external ecosystem where it runs, such as VMs or other ecosystems we have, and that is where the challenges come from. As a product, I don't see issues such as a bug in the product, frequent hangs, or unexplainable outages. I am not seeing anything like that with Control-M right now.
We are migrating from our VMs to physical machines, because we are exiting VMware and moving to physical servers and similar machines. Previously, we ran Control-M on VMware, and now we are moving to physical servers. Some cutovers are planned for today, and I am still talking to you, which means I have that much stability in my team. That is very good.
I would rate Control-M's stability at 98%, or more than that. Maybe you can put 99%. I just keep that 1% with me.
What do I think about the scalability of the solution?
The number of platform admins using Control-M is less than 10. The business applications, meaning the application owners, number 1,000 plus. They have visibility into the systems. They get a read-only version of their jobs, and they can look at the monitoring console and all those things to see whether their jobs are running. They can see the logs and their schedules, but they cannot make schedule changes or anything on the platform side. The platform side is less than 10, and the users might be more than 1,000 plus.
I think scalability is nine out of 10. It is pretty much able to run. I think we run more than 10,000 jobs, from what I understand of the overall workloads. It is able to manage them with no problem. There are no unexplainable outages, no non-scheduled jobs being missed, and no vanishing schedules, which were very frequent in my earlier tool. Compared to the earlier tool, this is a big boon for us, from the stability perspective as well as the governance perspective.
How are customer service and support?
Technical support from Control-M is very good. It is excellent support. Even with any issues, they make sure we get a technical solution, or if it cannot be technical, they can come to a logical conclusion as well. The technical support of Control-M is the best I have seen, because I have worked with more than 20 or 25 products, not only Control-M, but other workload products, cloud products, cloud hosting providers, and many other products. Control-M has one of the superlative support teams I have seen.
I would rate Control-M a nine.
Which solution did I use previously and why did I switch?
When I compare Control-M to other solutions or vendors, that is always in regard to the features I mentioned earlier that I appreciate most. The orchestration part, the integrated orchestration, lets us use SAP, non-SAP, DB, and open-source technologies in all formats. We are able to stitch together all the application requirements and data movements across all these platforms. I am not sure whether other products have this feasibility, because I haven't had a chance to review them, but I know about one tool we were using prior to Control-M, which doesn't have this flexibility. Stitching across or cutting across multiple technologies is always a bigger problem.
From the automation perspective, we have built an in-house tool that helps the application teams or business teams trigger jobs based on their needs. We use the Control-M APIs, which the product uses internally for scheduling and running all those things. We use those same APIs and expose them to our in-house applications, providing an interface for our business teams to trigger jobs as and when they need. That is the self-service portal I mentioned earlier.
That kind of flexibility is not available in the earlier tool. You had to go to the tool and do it yourself, and because of some restrictions, we could not give access to our tools. So we provide simplified dashboards or screens with access controls.
How was the initial setup?
Our overall experience with the migration process with Control-M is very smooth. The migration perspective is very smooth, because for any upgrades or migrations, you have the migration approaches built into the way the product is designed. We have primary and secondary concepts. First, we do it on the secondary, then we monitor it for some time, then we fail over to the secondary and see whether things are working wherever we have upgraded. Then you have the option to do it on the primary.
The way Control-M is built, upgrades and migrations are all considered in the tool engineering itself. That is the best thing for adoption, as well as for any migration or upgrade that brings more features. That helps us adopt it. If upgrades are difficult, people will be reluctant to move to the next versions because of the effort involved, and whether that effort is worth the features in the next version. Those kinds of concerns don't come to mind when we do a Control-M upgrade.
What was our ROI?
The return on investment we see is more than 50% for sure. It is not 100%, I would say, maybe because we are not using it to the fullest of its features, whatever is available to us. That is also on us. We have yet to adopt the modern workloads as well as the cloud-native workloads because of the security controls we have. I would say more than 70%. That might be my ballpark number.
What's my experience with pricing, setup cost, and licensing?
Pricing for Control-M is not cheap and not expensive. I would say it is cost-effective. It is not cheap.
What other advice do I have?
Control-M does require maintenance, and it is very easy to maintain. The complexity is very low. It is easy to maintain, it is stable, and it is pretty good compared to the other tools I have used.
Centralized workflows have reduced manual effort and have improved container-level tracking
What is our primary use case?
My main use case for Control-M is batch job scheduling, data pipeline and ETL architecture, and enterprise application workloads.
For a recent example, we used Control-M for orchestration, where automated workflows were created around a business use case to make tracking easier for us. My application is for a shipping company. We work at the container level, so Control-M has made it easier to build an application that tracks what happens to a container, specifically to design these workflows.
Control-M is deployed as a hybrid cloud in our organization and is used to orchestrate workflows across on-premises systems and cloud platforms. It serves as a central scheduling and monitoring solution for critical business processes, data pipelines, and operational jobs.
For our hybrid cloud deployment, we primarily use Amazon Web Services (AWS) as our cloud provider. Control-M is used to automate and monitor our flows running in AWS.
How has it helped my organization?
Control-M has positively impacted our organization by reducing manual effort through automating repetitive tasks, batch jobs, and operations. This allows the team to work more on architecture and new features, rather than spending time on repetitive jobs that need manual intervention every time.
Application reliability has also improved, and Control-M has been reliable since we started using it. We can also predict a better SLA based on the tickets we receive. In addition, central operations have improved because multiple schedules and workflows are consolidated into a single platform, which reduces complexity. These impacts have significantly improved our organization.
In terms of measurable outcomes, we have reduced manual effort by almost 50 percent and job failure dependency by around 30 to 40 percent.
What is most valuable?
In my opinion, the best features of Control-M are centralized scheduling across different locations, cross-platform workflow orchestration, dependency-based and event-based automation, and SLA management.
Control-M also offers extensive integrations with SAP, Oracle, Snowflake, Kafka, and Kubernetes. These integrations bring information and data from those platforms into one place so that we can automate those processes, which is very useful.
Regarding governance and security, Control-M provides strong capabilities through role-based access controls, audit trails, and centralized management and control of workflow execution. These features help ensure that only authorized users can create, modify, or execute jobs while maintaining visibility into operational activities.
From a governance perspective, the centralized management capabilities help organizations enforce standards and maintain compliance across teams and environments. Overall, I believe its governance and security features are mature and suitable for enterprise-scale operations.
Regarding the accuracy and reliability of Control-M's AI output, my experience has been positive. The AI-generated insights and recommendations are generally accurate and helpful for understanding workflows. They have helped reduce investigation time and improve productivity.
Although critical decisions require human validation, the AI has helped a lot. The accuracy has been very high, and it has met my expectations.
What needs improvement?
There are a few areas where Control-M could be improved, such as licensing and cost. It is expensive compared to alternatives such as Autosys. Faster troubleshooting, enhanced root cause analysis, and more diagnostics for failed jobs would also help support teams resolve issues. Control-M is a mature and reliable workload automation platform, but it should be improved through a more modern user interface, simplified administration, and more flexible licensing.
The main improvements I would like to see in Control-M are UI simplicity, advanced reporting, and faster troubleshooting.
While Control-M is a mature and reliable workload automation platform, the main improvements I would like to see are more intuitive AI, better AI-powered troubleshooting, and more flexible licensing. These enhancements would further improve the overall user experience and operational efficiency.
For how long have I used the solution?
I have been using Control-M for around a month.
What do I think about the stability of the solution?
In my experience, Control-M has been stable. I do not think we have faced any downtime. It has been very stable.
What do I think about the scalability of the solution?
Regarding scalability, Control-M has scaled up effectively to handle our increased workload. We have been able to scale the number of jobs and flows while maintaining performance, reliability, and operational visibility. This has enabled our support team to grow without a proportional increase in manual effort.
Which solution did I use previously and why did I switch?
Control-M currently serves our needs.
What was our ROI?
Control-M delivered an ROI primarily through time savings and operational efficiency. We estimated that it reduced manual effort.
What's my experience with pricing, setup cost, and licensing?
We purchased Control-M through the AWS Marketplace.
My experience with Control-M's cost and licensing has been reasonable for an enterprise-grade workload automation platform. The organization mostly handles the cost and licensing side, and we were involved only in the selection criteria. That said, the reduction in effort justifies the investment well, but I feel there could be a little bit more.
Which other solutions did I evaluate?
However, based on my experience using Control-M, it has proven to be reliable. Some common alternatives suggested during that time were Tidal Automation, IBM Workload Scheduler, and Stonebranch. We finally decided on Control-M, and it has been good for us.
What other advice do I have?
I would rate Control-M a nine out of ten.
I rated Control-M a nine because it is a highly reliable and mature workload automation platform. I did not give it a ten because there is still room for improvement in areas such as licensing cost, user interface modernization, reporting capabilities, and some cloud-native features. These are the factors that led me to take a point off.
My recommendation to others reading reviews on PeerSpot is to use Control-M, since it has been a great help for our organization and our team. For someone with a use case like ours, it has been a great help, and they can look forward to using it.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Workflow automation has transformed file transfers and cloud data pipelines
What is our primary use case?
As a specific example, I use Control-M for job scheduling and for batch processes in the data.
Beyond that, I also use Control-M for hybrid and multi-cloud environments, specifically with Azure. So, I use Control-M for the cloud.
What is most valuable?
The file transfer feature particularly helps us in the cloud, because we are using AWS, so it is useful for S3 buckets.
Control-M has positively impacted our organization because it is very helpful for integrating with GitLab, where we push our code. As a result, our CI/CD pipeline is running.
Integrating Control-M with GitLab has benefited us because we are integrating the code that we develop in the pipeline and jobs by pushing it to GitLab. That is how it is helpful.
What needs improvement?
If I had to suggest one area for improvement in Control-M, I would suggest it in the future if I find something very useful.
For how long have I used the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
How are customer service and support?
Which solution did I use previously and why did I switch?
What was our ROI?
What's my experience with pricing, setup cost, and licensing?
Which other solutions did I evaluate?
What other advice do I have?
The reason I gave Control-M a nine is that I have been using it for the past three months. For these few months, it has been very good, and for that reason, I have given it a nine.
Regarding governance and security in Control-M, it is good while using data, but I have not worked much on the security side so far.
Regarding the accuracy and reliability of Control-M's output, it is good overall.
My advice for others considering Control-M is that it is very good at saving time and integrating with other tools they are using. It will be useful for them to use Control-M.
Automation has transformed soc workflows and now frees analysts to focus on real security threats
What is our primary use case?
I primarily use Control-M to automate and schedule our routine SOC tasks and daily security reports. For example, we run scheduled batch jobs to pull threat intelligence feeds, automate daily log and backup scripts, and generate automated compliance and alert summary reports from our SIEM, such as FortiSIEM. Instead of manually running scripts or checking whether the overnight data transfer completed, we monitor all of those workflows from a single dashboard to make sure our security logs and reports are ready on time every morning.
The other key use case for us is automating our system health checks. Usually, this is not automated, and we do it manually. In the SIEM, we go to the CMDB, the query analytics, and the scripts, and we have to do all of that manually. Because of Control-M, we can automate our system health checks and log forwarding validations across multiple servers. In the SOC environment, if log forwarding stops sending data to the SIEM, we lose visibility. So, we use Control-M to run a scheduled dependency workflow that checks whether log collectors and critical security services are running properly. If a job fails or the log transfer gets stuck, Control-M automatically alerts us or triggers a restart script. It basically acts as our safety net to make sure the SIEM data pipelines stay healthy without us having to manually verify every single server.
Our organization offers three main services. The first is security and managed SOC services. We run a 24x7 cyber defense center offering real-time threat monitoring, SIEM management, incident response, vulnerability assessment, and more. The second is cloud and data center infrastructure, where we handle hybrid and private cloud deployments, servers, virtualization, and modern data center management. The third is data protection, which is very important for business continuity. We provide enterprises with backup, disaster recovery, data replication, and data loss prevention (DLP) solutions.
For machine learning workloads, and the security, access, and operational considerations we followed, in our organization we use Control-M as the central orchestrator to coordinate the end-to-end pipelines behind our machine learning and security analytics workloads, such as anomaly detection models, user and entity behavior analytics (UEBA), and threat scoring pipelines. Rather than letting ML scripts run in isolation, Control-M ties together the entire lifecycle, pulling raw telemetry logs from on-prem servers and AWS, running data cleaning and enrichment scripts, and triggering model retraining or retirement jobs on the cloud platform, such as AWS SageMaker.
Finally, it pushes the scored risk alerts back into FortiSIEM, which we mainly use. We have multiple SIEMs. This helps our L1 analysts with investigations. For security and access control, we have role-based access control, separation of duties, vaulted credentials, least privilege, network isolation, and audit trails. From an operations standpoint, we consider strict data dependencies, resource management, and SLA management.
In our SOC and IT operations, there are three main scenarios where Control-M policy enforcement, approval gates, and risk gating have been essential. The first is automated incident containment and high-impact remediations. The second is promoting new workflows from test to production, where we enforce workload policies before they go live. The third is data integrity and pipeline risk gating, where we use condition-based risk gating to verify that the upstream log ingestion finished cleanly.
In our environment, since we primarily run on AWS alongside our on-prem infrastructure, we especially integrate Control-M with Amazon SageMaker to orchestrate our security analytics and anomaly detection pipelines. The main MLOps workflows we coordinate are automated data preparation and ingestion, batch inference and threat scoring pipelines, and scheduling model retraining and validation.
In our organization, as far as I know, Control-M is acting as the central orchestration for around 150 core automation jobs and pipelines. While a large portion of our current usage is tied to our SOC operations, such as scheduling daily log backups, orchestrating threat intelligence feeds, and managing data, it is not strictly limited to the SOC. We also use it across the broader IT and infrastructure services, including coordinating hybrid cloud workloads, managing AWS data preparation for machine learning and analytics modeling, and supporting automation, backups, and disaster recovery processes across our managed service client environments.
How has it helped my organization?
Before using Control-M, handling repetitive scripts, log backup schedules, and health checks required a lot of manual effort and constant monitoring of different servers. Now, everything is automated and visible in one place. Because we do not have to manually trigger routine jobs, it saves us time. If the overnight batch process succeeds, our L1s, such as me as an L1 analyst, can focus much faster on the investigation of real threats and real security alerts on FortiSIEM, which is the same SIEM we use.
As far as I know, there are a lot of things Control-M makes easier and error-free, because they do not need much human interaction. First, it has improved our SLA and our reporting accuracy. Reporting accuracy improves because if you set up the automation, you do not need manual interaction again and again. It avoids errors and saves time, which is why it improves our SLA as well. Because daily compliance reports, log backups, and threat intelligence updates run on a strict automated schedule with dependency checks, we rarely miss deadlines or deliver incomplete data to our managed clients.
Second, it optimizes our team's productivity and shift handovers. That is a very highlighted point because a shift handover is very important. If another shift does not know what happened in the first shift, they are not aware of the threat. So, it helps with this as well.
Typically, our flow is to come in, take the handover properly, understand it, make our own notes, and then start making reports manually, running the analytics queries, and building the dashboards, all of which is manual. Because of Control-M, in terms of time saved, our SOC team easily saves around 1.5 to 2 hours per shift, which adds up to roughly 10 to 12 hours a week across our daily operations. Before Control-M, L1 analysts would spend the first 30 to 45 minutes of our shift manually logging into different servers, checking whether the overnight log backups completed, and taking the handover. We have also seen about a 70 to 80% reduction in manual script errors and failed report deliveries. That is how much time we can save, which is a minimum of 1.5 to 2 hours per shift per day.
What is most valuable?
All of the features are, to be very honest, the very best. But especially for me, the best feature of Control-M is the single pane of glass dashboard combined with dependency-based workflow scheduling. Because I am in the SOC, we deal with different server scripts and data transfers running at the same time. With Control-M, I do not have to log in to multiple machines to check whether a job finished or not.
Dependency-based workflows help us, for example, avoid running scripts blindly or at a fixed time. They also prevent cascading errors across SOC operations. They help us save time by avoiding errors. First, they eliminate manual mistakes because they do not require much manual interaction and are automated. Second, dependency checks prevent bad data from moving forward if the overnight log collector script fails or only partially completes.
One more thing worth adding is how easy Control-M makes troubleshooting and root cause analysis. When something goes wrong in a traditional setup with basic cron jobs or Windows Task Scheduler, if a script fails overnight, you have to manually log into that specific server, hunt down the log files, and figure out what broke. Control-M helps us with troubleshooting and root cause analysis, and it is easier and more helpful.
I use Control-M's AI capabilities in a straightforward way, specifically the recent generative AI and security capabilities. I have been using them for only a few months, not for years, and I use them for specific tasks. Especially in the SOC environment, where speed and strict access control both matter, features such as the GenAI Advisor and the AI Workflow Creator make daily operations much faster. Instead of manually writing complex job definitions or digging through documentation when setting up a new log transfer or SIEM reports workflow, you can use natural language to build and troubleshoot workflows. For an L1 analyst, having an AI assistant that can quickly analyze a job failure and explain the error inside cuts down troubleshooting time during a busy shift. From a security and governance standpoint, what stands out is that BMC did not just add AI without guidelines. They included granular AI access.
Integrating Control-M with AWS services and our CI/CD tools has been moderately straightforward, as far as I know, although I am a SOC analyst. It is definitely manageable, but it does require some initial setup. With AWS services, it is quite smooth. Control-M provides native plugins and integrations for major AWS services such as S3, EC2, Lambda, and SageMaker. Because we use AWS IAM roles and securely pass credentials via vaulted integrations, connecting Control-M agents on our cloud instances or triggering cloud-native workflows does not take too much custom scripting.
CI/CD and DevOps tools require a bit more effort. As far as I know, integrating Control-M into our deployment pipelines, such as Jenkins or Git-based workflows, to automate job definition updates as code takes more time, effort, and configuration. Once our L2 team set up the API endpoints and pipeline templates, it became very efficient. Out of the box, however, it is not a single-click setup. You need someone familiar with APIs and pipelines to stitch it together.
My impression of Control-M for helping business users is that it gives business users and non-admins, such as the SOC manager, a clean self-service web view to track their jobs in real time without needing technical skills or back-end server access. It is far more efficient and effective. This is important for our organization because it eliminates bottlenecks. Managers and auditors can verify morning compliance reports or trigger approved reruns themselves instead of raising tickets with our L1 and L2 teams, while strict role-based permissions ensure they still cannot alter critical back-end scripts or security settings.
For DevOps, Control-M eliminates the need for disconnected scripts by coordinating the entire data lifecycle, from ingesting raw security logs across our on-prem servers and the AWS S3 bucket, to transforming and validating that data before it lands in the SIEM or analytics models. Because it enforces strict dependency rules and data readiness checks before downstream reporting or threat scoring jobs, those jobs only run once the upstream data transfer is 100% verified. This ensures data reliability and keeps SLA timelines intact.
For DevOps, Control-M also supports a job-as-code approach using its Automation API. Instead of our engineering team manually clicking through the UI to build or update job schedules, they define workflows in JSON or Python, store them in Git, and automatically test, validate, and promote them into production through our existing CI/CD pipelines. This lets our engineering team deploy workflow updates at the same speed as application code while still maintaining full audit trails and governance.
Control-M helps our organization stay audit-ready and secure in three simple ways. First, the audit trails automatically log every job run, manual rerun, and workflow change with the timestamp and user IDs, making client and security audits much faster. Second, lineage tracking lets us trace the final compliance report or SIEM alert all the way back to the exact upstream log collection and processing job that created it. Third, policy enforcement automatically checks and blocks workflows before they run if they do not follow our security rules, naming standards, or vaulted credential policies.
What needs improvement?
I am not sure what can be improved, but there are a few things I have observed from my point of view. The first is the user interface. It feels a bit cluttered and overwhelming at first, especially for a newer L1 analyst like me. Since it is a very powerful enterprise tool with tons of menus and tabs, the learning curve is a bit steep during the first few weeks. A cleaner, more modern UI with simpler role-based views for L1 monitoring would make onboarding much faster. That is my perspective.
The second is that out-of-the-box integration with security and SIEM tools, such as FortiSIEM and Splunk, could be smoother. Right now, setting up custom API triggers for forwarding specific job alerts into our SIEM workflows often requires writing custom scripts or manually configuring webhooks. Having more plug-and-play connectors for security tools would save a lot of setup effort.
Lastly, the documentation and error messages can sometimes be too generic or too technical, giving just a numeric exit code without clear guidance. Specifying troubleshooting hints inside the dashboard would help make shift work faster.
I would have to think about the needed improvements further, based on what I have seen. One more area is better customization, specifically for alerts and notifications. Right now, on my present shift, I observe that if a non-critical job gets slightly delayed or a minor warning appears, it can create a bit of alert noise. Having more granular filtering would mean we only get high-priority pings for critical SIEM or log transfer failures, while a minor delay is just shown as a passive dashboard warning. That would reduce alert fatigue for our L1 teams.
For how long have I used the solution?
I have been using Control-M for four months.
What do I think about the stability of the solution?
In terms of reliability, the core scheduling engine is rock solid once the workflow is set up. It runs predictably without dropping a task. The AI-side features, such as the GenAI assistant and the AI pilot for monitoring, are reliable because they pull context directly from our actual job definitions, the actual logs, and official documentation. The accuracy is very strong because it takes very little human interaction. That accuracy extends to summarizing job statuses, spotting recurring failure patterns, and drafting standard workflow templates.
That said, like any generative AI, it is not 100% infallible. When we generate a complex custom workflow, especially one that touches SIEM scripts, we still treat the AI output as a solid first draft and verify the logic and parameters before pushing it into production. That is the Control-M accuracy impact and reliability impact in our SOC, our security, and our production environment.
What's my experience with pricing, setup cost, and licensing?
As a SOC analyst, I do not handle the direct billing side myself, as that is managed by our IT leadership and other senior people. However, as far as I know, we acquired our licensing through the AWS Marketplace via a private offer from BMC, rather than the standard public click-to-buy listing.
What other advice do I have?
I would tell anyone researching Control-M on PeerSpot that I rate it a 9 out of 10 overall. If you had asked me this question first, I would have rated it a 10. But because you asked me repeatedly what we can improve, I rate it a nine.
I gave it a nine because of its reliability and, from an operational standpoint, it delivers almost everything our SOC needs. Once the workflow's dependency chain and the automated health checks are configured, Control-M runs like clockwork for us. It has eliminated manual script errors, first of all. Second, it saves the L1s' time for everything, including making reports, handling the logs, and doing the handover. It also ensures the SIEM data pipelines and daily reports stay completely on track, and it helps us avoid mistakes and human errors. This helps us a lot. It would have earned a 10, but because of the dashboard, I rate it a nine.
In our organization, we do not have a single deployment model. We use a hybrid deployment model, with the core Control-M component hosted primarily on-prem in our private cloud environment. We use lightweight agents to connect across both internal servers and public cloud instances, because we operate a SOC environment handling sensitive security logs, compliance reports, and SIEM data pipelines. We primarily use AWS, Amazon Web Services, alongside our on-prem infrastructure.
Many people interact with Control-M, and they have different roles. Around 12 to 15 team members interact with it across our daily SOC and infrastructure operations. Mainly, 6 to 8 users are SOC L1 analysts, and 3 to 4 are our L2s, such as SOC L2 engineers, and the automation leads, who also use it. Two are Control-M or infrastructure admins, and the SOC manager is also a user.
We are planning to increase our use of Control-M, because we plan to expand its usage across both new teams and additional workflows. We are looking to expand to more teams, onboarding our infrastructure, cloud engineering, and client-facing managed services teams, so they can leverage it.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Job scheduling has simplified ETL monitoring and has improved workflow tracking efficiency
What is our primary use case?
As a data engineer, my main use case for Control-M is production monitoring. I have worked with Control-M for the past four years, and I use it for production monitoring.
A specific example is the production monitoring of ETL jobs. I schedule ETL jobs in Control-M, which makes them very easy to monitor. I schedule a large number of workflows there.
How has it helped my organization?
Control-M has positively impacted my organization by making it easier to track workflows efficiently. It is very effective. With fewer people, we can track workflows easily, and if any errors occur, I can track them very easily. It reduces the time I spend tracking workflows and jobs, which increases the efficiency of work.
I cannot put an exact number on how much time Control-M saves me, but it reduces the employee count. It is very useful because I can track workflows very effectively in one place. I can check the dependency matrix easily in Control-M, whereas tracking it in my ETL is difficult. I can check the workflow name and the dependency matrix in Control-M, and then I go into my ETL to download my logs very easily. This reduces time, and that is the main benefit.
What is most valuable?
Among the best features Control-M offers, the one that stands out most to me is scheduling jobs. Scheduling jobs is the one thing I am very interested in. If any job fails, we can also check the dependency matrix, so we can track the dependent workflows very easily by using Control-M.
When it comes to using these features, I rely on Control-M to troubleshoot failing production jobs. If a production job fails with an error, I can check which job is failing and why by reviewing the error in the logs. If there is a data issue or any other kind of issue, I can track it very easily in Control-M.
After that, I go into my ETL, download the logs, and rectify the issue very easily and effectively.
What needs improvement?
When it comes to improving Control-M, I did not observe any area for improvement right now. As of now, I am satisfied and good with this, so my answer is no.
For how long have I used the solution?
I have been using Control-M for more than four years.
What was our ROI?
From my experience, Control-M has delivered a return on investment through fewer employees and saved time. With fewer employees, I can handle the work, and a significant amount of time is saved. I can complete my work in less time, and it works very effectively.
What other advice do I have?
On a scale of 1 to 10, I rate Control-M overall a nine.
My rating of nine for Control-M reflects how I see AI as the next generation. AI is moving fast, and I need to see how Control-M will perform with AI. That is why I gave this rating.
Regarding Control-M's AI capabilities, its governance and security look solid to me, especially for permissions. From a permissions point of view, it is good, with no doubt about that.
Control-M is deployed in our organization across on-premises and hybrid cloud environments, including AWS and GCP. I use Redshift and GCP.
For others looking into Control-M, I would say it is a very easily handled product. I suggest it for monitoring purposes.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Control-M: Powerful Workload Automation with Centralised Monitoring and Reliable Job Scheduling
Automated security data pipelines have improved threat visibility and streamline nightly operations
What is our primary use case?
My primary use case for Control-M is heavy-duty security data pipeline orchestration and automated workflows running strictly on-premises.
A great example of a workflow I run recently on Control-M is my automated nightly security log ingestion and threat intelligence staging pipeline for an on-premises enterprise client.
My main use case for Control-M is on-premises security data pipeline orchestration.
Control-M supports several core services and business use cases across organizations from a broad enterprise perspective.
Regarding specific workflows, while dedicated data science platforms have native pipeline tools and orchestration, ML operations across a hybrid enterprise environment often requires integrating platforms like Amazon SageMaker or Google Cloud Vertex AI directly with the broader AI and security infrastructure.
My organization utilizes Control-M as a core operational backbone for orchestrating sensitive on-premises security data pipelines, automated managed file transfer routines, and local log staging tasks that feed directly into my SIEM ecosystems like Splunk and FortiSIEM.
I use Control-M to orchestrate workloads across multiple environments, mostly on-premises and virtual.
How has it helped my organization?
The biggest positive impact I have seen from Control-M is zero pipeline blind spots because everything runs on strict dependency mapping, and log ingestion and threat intelligence syncs never fail silently.
While I don't look at the business ROI dashboards all day, from a day-to-day SOC operation standpoint, I track a few key metrics and outcomes with Control-M.
What is most valuable?
The standout feature of Control-M for me is its end-to-end workflow dependency mapping combined with its managed file transfer capabilities.
Regarding AI capability with Control-M, while my primary focus with Control-M is handling secure, on-premises data pipelines, I have also looked at AI capabilities and security.
Control-M utilizes its built-in AI assistant like Jet and Natural Language Processing to help build and troubleshoot workflows.
In my SOC and MSSP environment, I rely on Control-M's built-in approval workflows and risk gating to ensure that high-impact automation or pipeline modifications do not go live unmonitored.
Control-M smooths and modernizes workflows by shifting from traditional GUI-driven configuration to an API-first workflow-as-code model in terms of ease of integration with technology of data operations and DevOps processes.
Control-M, through the lens of business user visibility and stakeholder transparency, offers a strong bridge between raw technical execution and high-level operational outcomes.
Control-M supercharges my data operations and DevOps initiatives by bridging traditional IT orchestration and application delivery.
When integrating AI and ML operations workflows into my security operations, Control-M acts as a critical runtime governance layer in terms of integration governance.
What needs improvement?
From a SOC perspective, there are a couple of areas where Control-M could be improved for security operations.
Sometimes, brief temporary network drops trigger immediate failure notifications before Control-M's internal retry logic has a chance to kick in and successfully complete the task.
For how long have I used the solution?
I have been using Control-M for around three to four months.
What do I think about the stability of the solution?
For workflow automation, data pipelines, and MFT operations, stability is a core metric that separates Control-M from lightweight schedulers and native cloud cron tools.
What do I think about the scalability of the solution?
Control-M achieves enterprise-grade scalability through its decentralized three-tier architecture, allowing my MSSP to seamlessly scale from tens of nodes to thousands of simultaneous endpoints.
How are customer service and support?
For a mission-critical orchestration engine, Control-M customer support is vital for my MSSP SOC.
How was the initial setup?
When deploying Control-M in an MSSP or SOC environment like mine, I follow a structured phase approach focused on local control and security.
For my specific use case, I deployed Control-M strictly on-premises.
What about the implementation team?
Deploying and managing an on-premises Control-M environment within a hybrid SOC or MSSP structure requires a team highly specialized in it because Control-M acts as the foundational mission-critical platform.
What was our ROI?
The automated threat intelligence and log staging pipeline transformed my operations. Before Control-M, my MSSP SOC relied on a custom chain of scripts.
What's my experience with pricing, setup cost, and licensing?
When evaluating Control-M from an enterprise and MSSP budget perspective, it sits firmly within the category of premium mission-critical infrastructure software.
What other advice do I have?
I gave Control-M an 8 out of 10 because it is an absolute powerhouse for on-premises security data pipeline orchestration, managed file transfer, and strict dependency mapping.
Control-M is used by a few specific roles depending on whether they are building, monitoring, or auditing the work.
When I integrate AI workloads and drive adoptions, especially around automated security data pipelines and orchestrations, I focus heavily on balancing agility with strict security controls.
Assessing the creation and automation of data pipelines across on-premises environments requires balancing infrastructure control, deterministic reliability, and strict security compliance.
My advice for engineering teams and organizations evaluating Control-M, especially those operating in high-stakes environments such as security operations, MSSPs, or complex data engineering pipelines, is to adopt a jobs-as-code approach from day one.