We primarily use this solution for network configuration pushes. We use scripts from Ansible to push configurations to specific devices such as routers.
Techinal Solution Manager/ Hybrid Cloud Enterprise Architect at Kyndryl
Stable and scalable but needs templates for common configurations
Pros and Cons
- "Red Hat Ansible Automation Platform is quite stable. If you set it up correctly with the right configurations and there are no hiccups during installation and deployment, it will be stable. I'd give stability a rating of eight out of ten."
- "It would be helpful to have templates for common configurations. It would make it much easier and faster rather than creating a whole script. The templates would decrease the learning curve as well."
What is our primary use case?
What is most valuable?
The best features are the orchestration and flexibility of the solution.
What needs improvement?
It would be helpful to have templates for common configurations. It would make it much easier and faster rather than creating a whole script. The templates would decrease the learning curve as well.
For how long have I used the solution?
I've been working with Red Hat Ansible Automation Platform for a year.
Buyer's Guide
Red Hat Ansible Automation Platform
June 2025

Learn what your peers think about Red Hat Ansible Automation Platform. Get advice and tips from experienced pros sharing their opinions. Updated: June 2025.
860,592 professionals have used our research since 2012.
What do I think about the stability of the solution?
Red Hat Ansible Automation Platform is quite stable. If you set it up correctly with the right configurations and there are no hiccups during installation and deployment, it will be stable.
I'd give stability a rating of eight out of ten.
What do I think about the scalability of the solution?
It's a scalable solution. The capacity of the single instance is quite enough to hold up an enterprise. From a resilience perspective, you have to have a cluster that actually holds the whole thing.
On a scale from one to ten, I'd rate scalability at seven.
How are customer service and support?
I would rate technical support at nine out of ten.
How would you rate customer service and support?
Positive
How was the initial setup?
Once all of the components are in place, there are no issues with the initial setup. I would rate the initial deployment process at seven out of ten.
The deployment can take two days to a week depending on the requirements and resources available.
What's my experience with pricing, setup cost, and licensing?
Red Hat Ansible Automation Platform is an expensive solution. There may be additional fees to use advanced features.
What other advice do I have?
I would highly recommend Red Hat Ansible Automation Platform, especially to organizations that are moving toward a cloud or hybrid cloud infrastructure.
Overall, I would rate this solution at seven on a scale from one to ten.
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner

Consultant at Pi DATACENTERS
Useful for configuration management with a great GUI-based interface
Pros and Cons
- "We can manage all the configuration consistency between all our servers."
- "It should support more integration with different products."
What is our primary use case?
We have a lot of Red Hat servers in our data center environment, so we use this solution to manage the configuration, deploy and push configuration management. In addition, we use the Red Hat Ansible Automation Platform to automate deployment tasks.
How has it helped my organization?
We can manage all the configuration consistency between all our servers. It is a configuration management tool, so we can easily manage our consistent configuration course over different Red Hat or Linux servers. We have not used Windows recently and are using only Linux now.
What is most valuable?
We like the GUI-based interface for the tower. Before, we only had a command-line interface to run all the Ansible tasks. Now, the Ansible tower provides the complete GUI functionality to run, manage, and create the templates and the Ansible jobs. This includes the code and YAML file we can create. The GUI interface is the added advantage of this solution, including some integration with the different plugins.
What needs improvement?
It should support more integration with different products. For example, it is for network security automation, and with the VMware product, they don't have an integration for NFTX right now. So they should include this integration capability so we can automate more tasks with this solution.
For how long have I used the solution?
We have been using Red Hat Ansible Automation Platform since 2021, and we are using version 3.2. It is deployed on-premises.
What do I think about the stability of the solution?
It is a stable solution.
What do I think about the scalability of the solution?
It is a scalable solution and is based on your node license. We are using more than 400 servers right now, and it requires one senior system engineer for maintenance and deployment. We plan to increase the usage using Windows automation.
How are customer service and support?
I rate the technical support an eight out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We used a Puppet configuration in the past. We staged with Puppet and then moved to Red Hat Ansible Automation Platform.
How was the initial setup?
The initial setup and deployment were easy, but the first two days of operations were a bit complex. We completed the deployment in-house.
What was our ROI?
There is a return on investment as a technical person. It has saved time and effort in maintaining the deployment environment. So on the technical side, it's saved lots of time and effort on the configuration.
What's my experience with pricing, setup cost, and licensing?
I believe the cost per node basis is around $125 per node.
What other advice do I have?
I rate this solution a nine out of ten. Regarding advice, for the deployment, I would suggest working on inventory first. They should also consider their use cases and which workflow they want to implement. In the next release, they should have VMware tight interrogation.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Red Hat Ansible Automation Platform
June 2025

Learn what your peers think about Red Hat Ansible Automation Platform. Get advice and tips from experienced pros sharing their opinions. Updated: June 2025.
860,592 professionals have used our research since 2012.
Student at ARTH
Helpful for creating an environment and easy to use with dynamic inventory capability
Pros and Cons
- "Ansible is agentless. So, we don't need to set up any agent into the computer we are interacting with. The only prerequisite is that the host with which we are going to interact must have the Python interpreter installed on it. We can connect to a host and do our configuration by using Ansible."
- "Ansible is great, but there are not many modules. You can do about 80% to 90% of things by using commands, but more modules should be added. We cannot do some of the things in Ansible. In Red Hat, we have the YUM package manager, and there are certain options that we can pass through YUM. To install the Docker Community Edition, I'll write the yum install docker-ce command, but because the Docker Community Edition is not compatible with RHEL 8, I will have to use the nobest option, such as yum install docker-ce --nobest. The nobest option installs the most stable version that can be installed on a particular system. In Ansible, the nobest option is not there. So, it needs some improvements in terms of options. There should be more options, keywords, and modules."
What is our primary use case?
Basically, Ansible is a configuration management tool. Mainly, I've been using Ansible for making changes and for deployments, such as of web servers. I also use it for servicing instances, mostly from AWS. I use AWS Cloud, and I configure the instances that I've launched.
Recently, I've also created an Ansible role. Basically, you can contribute to Red Hat in the form of an Ansible role. Everybody can share their code with just simple commands, such as Ansible Galaxy. With a few commands, we can share each other's infrastructure.
How has it helped my organization?
It helps us to create an environment. I'm a student. As students, when we get into newer technologies, we can't share our infrastructure with each other, and it gets difficult to explain to everybody. For example, I want to tell my friend to do certain things so that his infrastructure is similar to mine. In such a case, I'll just create a playbook from Ansible, and I'll just share it with him. He will just run that playbook, and we both will have the same infrastructure.
It doesn't require us to change our existing infrastructure in any way. We just need Ansible software on the managed host. So, it just needs to have Ansible. The host with which we are going to connect should have the Python interpreter installed, and nothing else.
It saves time when it comes to service deployment, moves, or updates. We have created playbooks, which are very easy to create. They are scripts in Python. A playbook also acts as a documentary for you. You can refer to a playbook any time, and it definitely saves a lot of time. It gives very good results in a long run. You just have to invest time in creating the first playbook. After that, you just use it. While creating a playbook, you can specify keywords by using Ansible variables. For example, to launch an instance in AWS Cloud, I need to specify a name to it. If I need to launch two to three instances at once, I will create a variable for it and pass it externally through the Ansible playbook. Next time, you can change the keyword and run the playbook.
What is most valuable?
Ansible is agentless. So, we don't need to set up any agent into the computer we are interacting with. The only prerequisite is that the host with which we are going to interact must have the Python interpreter installed on it. We can connect to a host and do our configuration by using Ansible.
Its dynamic inventory capability is very useful. For example, we are provisioning instances in AWS, and I want a particular name tag. My name tag is my instance, and I've been running a lot of instances in AWS Cloud. If I want, I can filter and configure all instances running with a specific name. I can also dynamically fetch IPs. What happens in the AWS cloud is that if you shut your operating system down, and you do some reboot and stuff like that, then you'll lose the public IP. Being able to dynamically fetch IP is the main capability that I like in Ansible.
It is very easy to use. Anybody who has studied computer science or is from the mathematical field can easily use Ansible. You just have to know how to do a certain task. For example, if you want to make some changes to your firewall and maybe set up a web server, you don't have to know all the commands with respect to different operating systems such as Linux and Windows. You don't need to know commands, and you just need to have a basic idea about how you want to do it. It is very easy to use. You just have to know how to do it.
What needs improvement?
Ansible is great, but there are not many modules. You can do about 80% to 90% of things by using commands, but more modules should be added. We cannot do some of the things in Ansible. In Red Hat, we have the YUM package manager, and there are certain options that we can pass through YUM. To install the Docker Community Edition, I'll write the yum install docker-ce command, but because the Docker Community Edition is not compatible with RHEL 8, I will have to use the nobest option, such as yum install docker-ce --nobest. The nobest option installs the most stable version that can be installed on a particular system. In Ansible, the nobest option is not there. So, it needs some improvements in terms of options. There should be more options, keywords, and modules.
For how long have I used the solution?
I've been using Ansible for about one and a half years.
What do I think about the stability of the solution?
It is quite stable. It has been good so far. I didn't find any bugs.
We do our operating system-related configurations and router configurations by using Ansible. I am focusing on operating system-based configuration because I use it in the operating system, and it has been quite stable.
What do I think about the scalability of the solution?
It is scalable. You just need to know the IP address of the new operating system with which you are going to interact. You just need to enter credentials into Ansible inventory. You have to make entries to this inventory, and you are good to go. You can use the same configuration that you have been using in your previous host.
How are customer service and technical support?
I have not interacted with their technical support because I didn't come across any issues from Red Hat's side. It has been stable, and there was no need to contact them.
There is an open-source community of Red Hat and Ansible Galaxy where users contribute. I've contributed two to three times.
Which solution did I use previously and why did I switch?
I just started using Puppet and Chef. The main thing where Ansible stands out is that you don't need to make any changes to the upcoming hosts. With Puppet and Chef, you have to install an agent program that will act as a layer for interacting with the host. You need to install an agent in between, which takes time as well.
How was the initial setup?
It is a very straightforward process. There is a package available on their site. After we download their software for the respective distro, we just write the installation command, and everything runs greatly. After installing the product, most people make use of Ansible roles. Ansible Galaxy is already filled with a lot of roles. A lot of developers have already contributed to a great setup with their proper codes. As a user, I have to just install a role or just download it from the site. It was not a lengthy or complex process. It was very easy.
For the initial setup, it takes about 10 to 15 minutes in going through sites and searching for a particular version. The installation will take about 5 minutes. After that, you have to configure Ansible properly, which might take a little bit of time, but it also depends on whether you know the IP address of the host. If you know the IP address and credentials, then you just have to enter it in the Ansible configuration file, and it is done.
There is good integration between RHEL and Ansible. There are repositories configured for Ansible and you just enter the yum install ansible command, and it will do all the setup and it will also create a basic configuration file. The only remaining task would be to configure that inventory. You need to know the IP address of the host to which you are going to connect and the password. After you enter it into the inventory, it runs very quickly. There is no need to download it from any site. If you're using Ansible with Red Hat, then there is very little chance of any error while using Ansible.
Ansible's documentation is well-maintained and updated very frequently. You just need to go through the documentation. It is very easy to read. There is nothing much to worry about.
What other advice do I have?
Ansible Tower has great integration capabilities with enterprises solutions such as OpenShift and many more. I've seen many people integrating OpenShift with Tower, but I have not done it.
Before going for automation, one must first know the manual approach to it. After you've applied a manual approach, you can easily understand what type of automation you can do for your environment and infrastructure and how to do the automation.
When it is utilized with RHEL, things are very easy to understand. If someone has knowledge of RHEL, then they also have knowledge of Ansible. There is no need to study more about this. While using Ubuntu or different distros, you have to know more about Ansible, your OS-based package managers, and your internal configuration.
I'm currently preparing for the Ansible examination. I connect with their products remotely. They have configured every repository that one needs in their licensed products. Subscription will definitely be needed if you want to use it in the industry. If you just want to know about it, a subscription is not required.
I would rate Ansible an eight out of 10.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Owner at Inventrics technologies
Offers powerful automation with playbooks but could benefit from improved user-friendliness
Pros and Cons
- "The playbooks and the code the solution uses are quite useful."
- "It would be good to make the solution more user-friendly,"
What is our primary use case?
The primary use case is mostly automation. In technical terms, the solution uses a playbook. The playbooks contain code. If you have written all the code in the playbook, you just execute that code. You can automate depending on the environment.
What is most valuable?
The playbooks and the code the solution uses are quite useful.
What needs improvement?
It would be good to make the solution more user-friendly for customers who aren't skilled in coding and don't know how to use the playbook's code. If we have many customers and the modules already exist, the user can just plug and play.
For how long have I used the solution?
I have been using the solution for one year.
What do I think about the stability of the solution?
We don't have many issues with stability, so I rate the solution's stability a nine out of ten.
What do I think about the scalability of the solution?
I rate the solution's scalability a nine out of ten. We have two customers using the solution.
How are customer service and support?
The technical support is good.
How was the initial setup?
The initial setup is complex, and OpenShift would be much easier. It took a week to deploy the solution. When deploying the solution, you must download the installer and install the solution on the server.
It requires two engineers for maintenance and deployment.
What's my experience with pricing, setup cost, and licensing?
Customers need to pay yearly for the license. The pricing is acceptable. It is not expensive.
What other advice do I have?
If you know the basics of coding for you to write the playbook's code, and if you have a midrange environment with up to 1,000 servers, Red Hat Ansible Automation Platform is a good option to automate daily tasks.
I rate the solution a seven out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Senior Site Reliability Engineer
Highly scalable and helps with automation, but the product could do a better job at building infrastructure
Pros and Cons
- "The most valuable feature of the solution is that we don’t need an agent for it to work."
- "The product could do a better job at building infrastructure."
What is our primary use case?
I use the product mostly to configure virtual machines.
How has it helped my organization?
The solution helps us to have a standard configuration for all the virtual machines. It helps our virtual machines have the same configuration every time they restart. It also helps with automation.
What is most valuable?
The most valuable feature of the solution is that we don’t need an agent for it to work.
What needs improvement?
The product could do a better job at building infrastructure.
The product should add a feature that alerts us if someone changes the configuration.
For how long have I used the solution?
I have been using the solution for two years.
What do I think about the stability of the solution?
The product has high stability.
What do I think about the scalability of the solution?
The solution has high scalability. It can be deployed on thousands of machines. Seven people in our organization use the solution.
How was the initial setup?
The initial setup was straightforward.
What's my experience with pricing, setup cost, and licensing?
We use the open-source version of the solution. The product can be used for free.
What other advice do I have?
The tool should be used for server configuration but not for creating resources on the cloud. Overall, I rate the solution a seven out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Intern at a university with 1-10 employees
Stable and scalable automation platform that is highly compatible with other tools
Pros and Cons
- "The API for exposing all our infrastructure services is the most valuable feature."
- "From Red Hat Insights point of view, the product is not on top as it is not responding as per the demand...Like on cloud platforms, you can see the main parts of Red Hat Insights, along with the inventory of all your apps. So, that is missing in Red Hat Ansible Automation Platform."
What is our primary use case?
We use the solution for provisioning on different providers like VMware, and OpenStack because it was so easy to implement. This product is also helpful to create a job workflow including the approval steps.
It also includes DevOps tools for making an easy automation process.
How has it helped my organization?
It brings a lot of time-saving.
What is most valuable?
The API for exposing all our infrastructure services is the most valuable feature.
For how long have I used the solution?
I have been using Red Hat Ansible Automation Platform for three months.
What do I think about the stability of the solution?
It is a stable solution.
What do I think about the scalability of the solution?
It is a scalable solution.
How are customer service and support?
The technical support is very good. We asked the support team about applications, and they answered us. I rate the technical support a nine out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We used multiple tools in the past three years, but we did not use any other similar product to Red Hat Ansible Automation Platform.
How was the initial setup?
The initial setup was easy. I was not a part of the deployment process, but my team members told me about the deployment process.
What about the implementation team?
The in-house team asked the support team questions.
What's my experience with pricing, setup cost, and licensing?
It is an open source product but needs a license subscription to use it. The price depends on the number of nodes supported by the platform (the nodes correspond to a host which can be for example a VM or a data center).
The price is really different depending on the customer's needs.
Which other solutions did I evaluate?
We have evaluated other solutions but this is the one that best meets our need for provisioning automation and addresses the different infrastructure and cloud providers we use
What other advice do I have?
The product can be very easy to use, provided what you are using in it. I did not use the product myself, but it was really impressive when they showed the POC process. I rate it eight out of ten.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Managing Director at AgileWorks Information Systems
A good open-source software offering broad support and reliability to its users
Pros and Cons
- "Feature-wise, the solution is a good open-source software offering broad support. Also, it's reliable."
- "What we need is model-driven, declarative software infrastructure management. However, things tend to break with new versions, requiring a lot of work to fix…The focus should be on improving the support for Ansible in the area of AI coding."
What is our primary use case?
We use Red Hat Ansible Automation Platform in our company to implement a software-defined infrastructure, which involves defining the desired configuration of machines in terms of their components, setup, security, user roles, software deployment, and certificate deployment. With this platform, we are able to set up new environments and manage the lifecycle of instances across various stages, such as development, production, and pre-production. We also use it for routing up and back of new software.
What is most valuable?
Feature-wise, the solution is a good open-source software offering broad support. Also, it's reliable.
What needs improvement?
I think some community projects support Ansible Playbooks, but they often break with version updates. It's a difficult problem to solve. DevOps should have a library with common components to make Ansible more productive when there are updates to Ansible and the operating system. What we need is model-driven, declarative software infrastructure management. However, things tend to break with new versions, requiring a lot of work to fix. It becomes a cost-benefit analysis of reusing old Ansible scripts versus rewriting them from scratch after updates. The problem is that it becomes quite fragile over time, and this fragility is a problem.
If the IDE and auto-completion of the solution are based on Checkpt, it is important to ensure that the AI coding tools support writing in a more declarative way. While I have not yet tried coding with this assistance, Microsoft and Keylabs both offer AI coding assistants. The focus should be on improving the support for Ansible in the area of AI coding. It is crucial to see how well they work with the new versions of Ansible.
For how long have I used the solution?
I have been using Red Hat Ansible Automation Platform for almost five years. My company is an end-user of the solution.
What do I think about the stability of the solution?
The product's stability is very good. I rate it an eight out of ten.
What do I think about the scalability of the solution?
Ansible is a configuration tool that doesn't have to scale like other tools. So scalability does not apply to the solution. Also, it's not a tool used by thousands of users. I am unsure if it can be used to manage thousands of servers. Small teams, like the DevOps team, use the solution. We service large groups of servers with it using a very small team of about two or three and a maximum of four people.
How are customer service and support?
I have never contacted technical support. We use open-source support.
How was the initial setup?
The solution's initial setup process was simple. The solution gets used in various ways, and it's essentially a configuration tool you run from any node with access to other nodes. It has got server versions as well. So, you can use it either way.
Which other solutions did I evaluate?
We compared it to other configuration management tools before choosing Red Hat Ansible Automation Platform. We did not choose others since they were not as centralized. It doesn't need a server since you can run it from your clients, and it doesn't need a central deployment service or server.
What other advice do I have?
Red Hat Ansible Automation Platform is a declarative infrastructure management system that works fine if supported by the environments you use to set up. I rate the overall product an eight or nine out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Senior Solutions Architect at Jihu GitLab Technology Limited
It's easy to use if you have Linux skills, but it's not yet widely accepted in Hong Kong
Pros and Cons
- "I like Ansible's ease of use. If you have Linux skills, you can create a reusable template for the dependencies and other configurations. I can store the templates in a repository and share them with my customers or other developers. It's a popular solution, so there is a large user base that can share templates."
- "It could be easier to integrate Ansible with other solutions. No single tool can do everything. For example, we use Terraform for infrastructure and other solutions for configuration management and VMs."
What is our primary use case?
I'm a software architect at a DevOps platform called Jihu. We use Ansible to provision Kubernetes clusters. For example, if the cluster has dependencies, we provision for the specific package manager version and dependencies, so they can scale for the CI/CD line. Ansible helps us provision the Kubernetes cluster for single-cloud or hybrid-cloud scenarios.
What is most valuable?
I like Ansible's ease of use. If you have Linux skills, you can create a reusable template for the dependencies and other configurations. I can store the templates in a repository and share them with my customers or other developers. It's a popular solution, so there is a large user base that can share templates.
What needs improvement?
It could be easier to integrate Ansible with other solutions. No single tool can do everything. For example, we use Terraform for infrastructure and other solutions for configuration management and VMs.
For how long have I used the solution?
I have used Ansible for around four years.
What do I think about the stability of the solution?
Ansible is stable as long as you have the connections between the machine and the server you use for all of this.
What do I think about the scalability of the solution?
Ansible has some built-in mechanisms to help you scale. There are different playbooks or steps. I have various multi-project partners that handle these kind of jobs, so I can do the provisioning simultaneously. Of course, we still need to do some prerequisites and there are dependencies between various jobs.
How are customer service and support?
I don't typically raise support tickets, but I frequently work with the Red Hat presales staff because we sell their solutions.
How was the initial setup?
Setting up Ansible is straightforward because we use the Docker image. There may be some challenges if you have large-scale VMs. It's typically fine if we use configuration management for the credentials and SSH. If you want to use Ansible to provision VMs like TerraForm, then we need to clearly understand the mechanism. The time needed to deploy Ansible depends on the type of applications and infrastructure you're dealing with. It isn't only about the specs of the VM. The network speed and complexity also factor into it.
What other advice do I have?
I rate Red Hat Ansible Automation Platform seven out of 10. I give it a seven in the Hong Kong context. It's about the culture, not the technology. Most of the infrastructure and network people in Hong Kong find it hard to accept a new solution, and it isn't easy to transform this kind of culture. They have one or two OEMs running on some simple web servers. Their teams are not familiar with the infrastructure cost calculators and configuration management stuff.
We don't push them to use anything like this, but if they have lots of things they need to manage, then it's an opportunity for us to sell them solutions. We ask them questions. How many standard operations are you using? What is the approval flow? How long would take if you want to release or deploy applications? We make the case that they could shorten the time spent on SOP by eliminating manual work in the approval flow.
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner

Buyer's Guide
Download our free Red Hat Ansible Automation Platform Report and get advice and tips from experienced pros
sharing their opinions.
Updated: June 2025
Popular Comparisons
Microsoft Intune
Microsoft Azure DevOps
Microsoft Configuration Manager
Cisco DNA Center
VMware Aria Automation
Red Hat Satellite
AWS Systems Manager
SolarWinds Network Configuration Manager
HashiCorp Terraform
UrbanCode Deploy
Buyer's Guide
Download our free Red Hat Ansible Automation Platform Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- What are the pros and cons of Ansible vs Red Hat Satellite?
- What is the difference between Red Hat Satellite and Ansible?
- How does Ansible compare to Microsoft Endpoint Configuration Manager (SCCM)?
- Which Infrastructure as Code (IaC) Configuration Management platform would you choose - Red Hat Ansible Automation Platform or HashiCorp Terraform?
- When evaluating Configuration Management, what aspect do you think is the most important to look for?
- Infrastructure-as-code vs infrastructure configuration
- What is automated configuration management?
- What are the advantages of using Infrastructure as Code (IaC) tools?
- Why is Configuration Management important for companies?