Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Progress Chef
Score 6.5 out of 10
N/A
Chef IT infrastructure automation suites were developed by Chef Software in Seattle and acquired by Progress Software in September 2020. The Chef Enterprise Automation Stack is an integrated suite of automation technologies presented as a solution for delivering change quickly, repeatedly, and securely over every application's lifecycle. The Chef Effortless Infrastructure Suit is an integrated suite of automation technologies to codify infrastructure, security, and compliance, as well as…N/A
Puppet Enterprise
Score 8.9 out of 10
N/A
Puppet Enteprise is an IT automation and configuration management solution that enables users to manage and automate infrastructure and complex workflows. The vendor states Puppet Enterprise combines both model‑based and task-based capabilities in a way that enables organizations to scale their multi-cloud infrastructure as their automation footprint grows, with more flexibility from both agent-based and agentless capabilities.N/A
Ansible
Score 9.2 out of 10
N/A
The Red Hat Ansible Automation Platform (acquired by Red Hat in 2015) is a foundation for building and operating automation across an organization. The platform includes tools needed to implement enterprise-wide automation, and can automate resource provisioning, and IT environments and configuration of systems and devices. It can be used in a CI/CD process to provision the target environment and to then deploy the application on it.
$5,000
per year
Pricing
Progress ChefPuppet EnterpriseRed Hat Ansible Automation Platform
Editions & Modules
No answers on this topic
No answers on this topic
Basic Tower
5,000
per year
Enterprise Tower
10,000
per year
Premium Tower
14,000
per year
Offerings
Pricing Offerings
Progress ChefPuppet EnterpriseAnsible
Free Trial
NoNoNo
Free/Freemium Version
NoNoNo
Premium Consulting/Integration Services
NoNoNo
Entry-level Setup FeeNo setup feeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Progress ChefPuppet EnterpriseRed Hat Ansible Automation Platform
Considered Multiple Products
Progress Chef
Chose Progress Chef
We considered the three leading competitors in the field: Chef, Puppet and Ansible. Ansible is a very strong competitor and has a nice degree of flexibility in that it does not require a client install. Instead the configuration is delivered by SSH which is very simple. Puppet …
Chose Progress Chef
Chef is the more developer-oriented of the three main tools in this space. It has a steeper learning curve as a result but it allows you to do more. Puppet seems to be more geared towards automated the management of the operating system. Ansible is an excellent tool but …
Chose Progress Chef
Puppet Labs and CFEngine are also open source and competes with Chef. Chef has more support from the community with templates available for large scale IT deployments. RedHat Ansible is better suited when you are already using RedHat OS and OpenShift since it comes as it comes …
Chose Progress Chef
Briefly looked into Puppet but ended up going with Chef because a colleague had experience with it instead. Didn't get far enough into a deployment to even really compare the two.
Chose Progress Chef
We found that Chef was easy to use, and we liked the whole concept of recipes and cookbooks. We were using the concept of recipes and cookbooks for our SQL development, so Chef was a natural fit for our team members and environment. That whole paradigm is easy for everyone …
Chose Progress Chef
I've mostly explained the differences between Ansible and Chef in my previous answers. I generally prefer Chef over Ansible because the platforms we use have very convenient cookbooks.
Chose Progress Chef
Chef is easy to install and manage, and the learning curve is minimal, as most of the engineers are already aware of the syntax to configure services. With flexible crating recipes and cookbooks, Chef made our jobs easier, and also it integrates well with Puppet. Overall …
Chose Progress Chef
Chef is something we have been using for a while, so it is the natural choice when training new engineers to maintain our systems. If I was to choose a configuration management tool now, I would pick Ansible mainly because of its agentless nature and YAML cookbook language …
Chose Progress Chef
We believe Chef is a great tool for DevOp. It works really well with repository tools such as Bitbucket and artifactory. The other products we evaluated either were too pricey or did not have the support we needed for a company that was very vanilla with automation. We selected …
Chose Progress Chef
We were evaluating Ansible as it was agent less, SSH based, simple to use and is completely based on SSH protocol. As and when the servers count increase the performance might degrade. One main disadvantage with Ansible is it is more suitable for linux based systems where SSH …
Chose Progress Chef
I really found that Chef to be much friendlier and innovative than Puppet. There is an opinion in the DevOps community that says that Chef is friendlier to programmers whereas Puppet is friendlier to system administrators. This might be true, as I do come from development …
Chose Progress Chef
Chef is good for organizations with many servers, because of the client-server approach. I guess Ansible can be used for some 20-40 servers, just ssh and run the playbook. Chef is in ruby which is a really simple to learn language as opposed to competitiors.
Chose Progress Chef
Chef was easier to setup than Puppet. It also has better Windows support and documentation. Reading through the Chef documentation gave good examples on how to configure things for Windows environments, however Puppet was a bit lacking in that regard. Puppet has better support …
Chose Progress Chef
Ansible and salt stack seem to be the new cool kids on the block because they are easier to setup and manage across smaller teams. I think the use of puppet is dying down in favor for these new technologies. I would like to see chef use cases with simpler implementation.
Puppet Enterprise
Chose Puppet Enterprise
As I mentioned before Ansible is a great tool. There is no question about it. It has very simple syntax (YAML), is very easy to learn, and is scalable as well. But the only thing that Ansible lacked at that time was the actual agent that have to go into each server. Ansible
Chose Puppet Enterprise
[Both] products are comparable. There is a good open source community for each, but we found Puppet to be the most mature for our specific use case.
Chose Puppet Enterprise
Puppet was selected before I joined the team, had it been my choice I would have much rather went with Chef as it has the ability to do things that Puppet has not yet added to their system such a the ability to quickly query what host currently are allowing puppet to maintain …
Chose Puppet Enterprise
I have not used any other Configuration Management System since cfengine back in about 2007 so I have little current input on alternatives to Puppet having never used them, though Chef seems to have gained some traction as has Ansible.
Chose Puppet Enterprise
We evaluated Chef and Ansible. Puppet Data Center Automation was cleaner and we were more familiar with the product.
Chose Puppet Enterprise
Puppet has a very wide user base with many organizations tht support it as well as conferences and events. Puppet DSL is based in Ruby while the server is now in Clojure providing ease of configuration with the power of scale. Puppet is a great entry point into the world of …
Ansible
Chose Red Hat Ansible Automation Platform
AAP delivered a more complete solution at all steps of our process across different silos.
Chose Red Hat Ansible Automation Platform
AAP is much easier to use/configure/maintain.
Chose Red Hat Ansible Automation Platform
We were Puppet users. Red Hat Ansible Automation Platform made more sense to us because of the focus on Ansible content to support our AIX systems and RHEL systems. We have also seen that the learning curve for Red Hat Ansible Automation Platform is better than we experienced …
Chose Red Hat Ansible Automation Platform
Ansible is much easier to use and configure than Puppet.
Chose Red Hat Ansible Automation Platform
It was much simpler to deploy and use Red Hat Ansible Automation Platform in our enterprise environment. Red Hat has great training to get our users up to speed. YAML is easy to write (although watch out for spacing) and run playbooks. We can easily generate infrastructure …
Chose Red Hat Ansible Automation Platform
All three of these competitors are agent based. I did not want an additional service that needed to run absolutely everywhere. I also did not want to maintain a load balanced cluster of master servers that grows in resource requirements as your infrastructure scales.
Chose Red Hat Ansible Automation Platform
My experience with Puppet and Chef is limited, but as a total non-programmer Ansible was just worlds easier for me to implement.
Chose Red Hat Ansible Automation Platform
Ansible is much easier than Puppet, more enterprises are switching from Puppet to Ansible due to ease of use. Ansible has integration modules which allow you to transition from Puppet or Chef to Ansible. IT Automation space has a CAGR of 200%+ what are you doing to not get left …
Chose Red Hat Ansible Automation Platform
Ansible has unique features in terms of server managing and configuring. It is easy to use and fits the Red Hat Linux well since they are closely related. Our servers are mostly Red Hat, so it makes sense to use Ansible. But we are still exploring which is the best.
Chose Red Hat Ansible Automation Platform
Chef is something that was used previously by our head engineer and is quite similar to Ansible. They're both great configuration management tools. However, since Ansible is agent-less, we decided to switch for the convenience and quick-start nature of Ansible. Along with that …
Chose Red Hat Ansible Automation Platform
Ansible is a great product, which we really love as it is compatible running along side and with other DevOps tool. The integration features allows other teams to participate in our shared objective. Ansible is easy to use as many programmers are familiar with Python and RHEL. …
Chose Red Hat Ansible Automation Platform
In the time of integration, we chose Ansible instead of Puppet because it was simpler to use, based on Python and didn't require additional server environments to run. Of course, there are a lot of different alternatives like Chef or Salt Stack.
Chose Red Hat Ansible Automation Platform
Ansible is sufficient for our purposes because our configurations are relatively simple. Chef and Puppet would work better for more complex configurations. Also, our applications are deployed using Docker which simplifies our configuration requirements. An organization with …
Chose Red Hat Ansible Automation Platform
  • Ansible is much simpler to get up and running with than Chef, as it requires no infrastructure or agent process or any configuration on the target machine. All you need is SSH access! However, you lose the capabilities that Chef server offers such as data bags (centralized data …
Chose Red Hat Ansible Automation Platform
I haven't used Puppet personally, but I believe Ansible is a robust solution which can serve many purposes. Puppet I'm sure is customizable in similar ways, I just don't have the experience to speak intelligently on the subject.
Chose Red Hat Ansible Automation Platform
I have used Puppet, Chef during my career and Ansible seems to be the most efficient tool by far, in terms of its implementation, configuration and ease of use.
Top Pros
Top Cons
Features
Progress ChefPuppet EnterpriseRed Hat Ansible Automation Platform
Configuration Management
Comparison of Configuration Management features of Product A and Product B
Progress Chef
-
Ratings
Puppet Enterprise
-
Ratings
Red Hat Ansible Automation Platform
8.6
44 Ratings
7% above category average
Infrastructure Automation00 Ratings00 Ratings9.244 Ratings
Automated Provisioning00 Ratings00 Ratings8.841 Ratings
Parallel Execution00 Ratings00 Ratings8.840 Ratings
Node Management00 Ratings00 Ratings8.432 Ratings
Reporting & Logging00 Ratings00 Ratings7.841 Ratings
Version Control00 Ratings00 Ratings8.738 Ratings
Best Alternatives
Progress ChefPuppet EnterpriseRed Hat Ansible Automation Platform
Small Businesses
HashiCorp Terraform
HashiCorp Terraform
Score 8.4 out of 10
HashiCorp Terraform
HashiCorp Terraform
Score 8.4 out of 10
HashiCorp Terraform
HashiCorp Terraform
Score 8.4 out of 10
Medium-sized Companies
Ansible
Ansible
Score 9.2 out of 10
Ansible
Ansible
Score 9.2 out of 10
AWS CloudFormation
AWS CloudFormation
Score 8.8 out of 10
Enterprises
Ansible
Ansible
Score 9.2 out of 10
Ansible
Ansible
Score 9.2 out of 10
AWS CloudFormation
AWS CloudFormation
Score 8.8 out of 10
All AlternativesView all alternativesView all alternativesView all alternatives
User Ratings
Progress ChefPuppet EnterpriseRed Hat Ansible Automation Platform
Likelihood to Recommend
8.8
(18 ratings)
7.0
(12 ratings)
9.5
(108 ratings)
Likelihood to Renew
-
(0 ratings)
-
(0 ratings)
8.2
(3 ratings)
Usability
7.3
(1 ratings)
-
(0 ratings)
7.3
(1 ratings)
Performance
9.4
(5 ratings)
-
(0 ratings)
8.7
(5 ratings)
Support Rating
7.7
(3 ratings)
8.0
(1 ratings)
7.3
(3 ratings)
Implementation Rating
-
(0 ratings)
-
(0 ratings)
8.2
(1 ratings)
Contract Terms and Pricing Model
6.4
(1 ratings)
-
(0 ratings)
-
(0 ratings)
Ease of integration
9.6
(5 ratings)
-
(0 ratings)
8.6
(5 ratings)
Professional Services
9.1
(1 ratings)
-
(0 ratings)
-
(0 ratings)
User Testimonials
Progress ChefPuppet EnterpriseRed Hat Ansible Automation Platform
Likelihood to Recommend
Progress Software Corporation
Chef is a fantastic tool for automating software deployments that aren't able to be containerized. It's more developer-oriented than its other competitors and thus allows you to do more with it. The Chef Infra Server software is rock-solid and has been extremely stable in our experience. I would definitely recommend its use if you're looking for an automation framework. And it also offers InSpec which is a very good tool for testing your infrastructure to ensure it deployed as intended.
Read full review
Perforce Software
Puppet is good enough to get the job done, you can use it to automate deployments and maintain files and configurations, if this is all you're looking for it's great. If you're looking for more control over your systems as a whole without having to write your own scripts or install multiple configuration management systems then Puppet is not what you're looking for.
Read full review
Red Hat
It has helped save us so much time, as it was designed to automate mundane and repetitive tasks that we were using other tools to perform and that required so much manual intervention. It does not work very well within Windows environments, understandably, but I would love to see more integration. I want it to be sexy and attractive to more than just geeky sysadmins.
Read full review
Pros
Progress Software Corporation
  • Chef is great at deploying code to both small and large groups of servers.
  • We use chef to standup new servers as well as deploy updated code to existing servers and it does this very well.
  • Being able to make a change and have it push manually or automatically to any subset of servers has changed the landscape of how our IT teams operate.
Read full review
Perforce Software
  • Provides a clear map of how a system is configured
  • Eases the creation of a system in a specific cluster as it is scripted in code
  • Simplifies configuration changes to a cluster or to every system such as rolling out vhost configurations, updating ldap roles, NFS mounts, etc
  • The syntax is very easy to read and carries a lot of fluidity once the language is learned.
Read full review
Red Hat
  • Debugging is easy, as it tells you exactly within your job where the job failed, even when jumping around several playbooks.
  • Ansible seems to integrate with everything, and the community is big enough that if you are unsure how to approach converting a process into a playbook, you can usually find something similar to what you are trying to do.
  • Security in AAP seems to be pretty straightforward. Easy to organize and identify who has what permissions or can only see the content based on the organization they belong to.
Read full review
Cons
Progress Software Corporation
  • Chef could do a better job with integration with other DevOps tools. Our company relies on Jenkins and Ansible, which took some development and convincing for plug-ins to be created/available.
  • It would be nice if kitchen didn't only have a vagrant/virtual-box prerequisite. Our company one day stop allowing virtual-box to run without special privileges, and that caused a lot of issues for people trying to do kitchen tests.
  • Chef could use more practice materials for the advanced certification badges. There was not a lot of guidance in what to study or examples of certain topics.
Read full review
Perforce Software
  • The setup of Puppet is a nightmare compared to ansible. Anyone watching a youtube video can easily set up ansible with minimal IT knowledge. All one needs is the source IP addresses and we are good to go. Setting up Puppet is a more hands-on task and pushing the puppet agents to all the boxes is another issue. If the installation and setup were simplified like ansible that would attract a lot of people to this platform
  • The syntax of the code for Puppet is not as easy as ansible. Ansible simply follows a YAML format and it's like typing in normal English. Even complicated tasks can be written by just understanding YAML syntax. Perhaps Puppet needs to revisit the lanugage used and try to come up with a much simpler lanugage for writing code. This will make day-to-day usage easier.
Read full review
Red Hat
  • YAML is hard for many to adopt. Moving to a system that is not as white space sensitive would likely increase uptake.
  • AAP and EDA should be more closely aligned. There are differences that can trip users of the integration up. An example would be the way that variables are used.
  • Event-driven Ansible output is not as informative as AAP.
Read full review
Likelihood to Renew
Progress Software Corporation
No answers on this topic
Perforce Software
No answers on this topic
Red Hat
Even is if it's a great tool, we are looking to renew our licence for our production servers only. The product is very expensive to use, so we might look for a cheaper solution for our non-production servers. One of the solution we are looking, is AWX, free, and similar to AAP. This is be perfect for our non-production servers.
Read full review
Usability
Progress Software Corporation
The suite of tools is very powerful. The ability to create custom modules allows for unlimited potential for managing all aspects of a system. However, there is pretty significant learning curve with the toolset. It currently takes approx 3-4 months for new engineers to feel comfortable with our implementation
Read full review
Perforce Software
No answers on this topic
Red Hat
the yaml is easy to write and most people can be taught to write basic playbooks in a few weeks
Read full review
Performance
Progress Software Corporation
It loads quick enough for basically all our systems. Because we have this for local dev environments, speed isn't really a big issue here. Yes, depending on the system, sometimes it does take a relatively long time, but it's not an issue for me. One thing that is annoying is that if I want to make a small change to a cookbook and re-run the Chef client, I can't just make the change in the cache and run it. I have to do the whole process of updating the server.
Read full review
Perforce Software
No answers on this topic
Red Hat
Great in almost every way compared to any other configuration management software. The only thing I wish for is python3 support. Other than that, YAML is much improved compared to the Ruby of Chef. The agentless nature is incredibly convenient for managing systems quickly, and if a member of your term has no terminal experience whatsoever they can still use the UI.
Read full review
Support Rating
Progress Software Corporation
Support for Chef is easily available for fee or through the open source community as most the issues you will face will have been addressed through the Chef developer community forums. The documentation for Chef is moderate to great and easily readable.
Read full review
Perforce Software
Puppet has top class support. You can simply mail them with their query and they will respond to your query in a timely manner. We do have enterprise license for puppet. Also there is a vibrant community for puppet out there. So even if you dont purchase a premium support option you can simply google your queries and get answers
Read full review
Red Hat
There is a lot of good documentation that Ansible and Red Hat provide which should help get someone started with making Ansible useful. But once you get to more complicated scenarios, you will benefit from learning from others. I have not used Red Hat support for work with Ansible, but many of the online resources are helpful.
Read full review
Implementation Rating
Progress Software Corporation
No answers on this topic
Perforce Software
No answers on this topic
Red Hat
I spoke on this topic today!
Read full review
Alternatives Considered
Progress Software Corporation
We considered the three leading competitors in the field: Chef, Puppet and Ansible. Ansible is a very strong competitor and has a nice degree of flexibility in that it does not require a client install. Instead the configuration is delivered by SSH which is very simple. Puppet seems like it has fallen off the pace of the competition and lacked the strong community offered by Chef. We chose Chef because of the strong support by the company and the dynamic and deep community support.
Read full review
Perforce Software
HPSA is a licensed product and incurs significant upfront investment costs due to COTS licensing. Puppet Data Center Automation has a significantly lower upfront investment and product documentation is more readily available. Chef is a very similar offering, however, at the time our decision was considered, the adoption of Chef vs. Puppet was significantly less in the community.
Read full review
Red Hat
I haven't thought of any right now other than just doing our own home-brewed shell scripts. Command line scripts. And how does this compare? It's light years ahead, especially with the ability to share credentials without giving the person the actual credentials. You can delegate that within, I guess what used to be called Ansible Tower, which is now the Ansible Automation platform. It lets you share, I can give you the keys without you being able to see the keys. It's great
Read full review
Contract Terms and Pricing Model
Progress Software Corporation
The pricing seemed inline with our products in this space. Nothing out of the ordinary in contract, term, or pricing structure
Read full review
Perforce Software
No answers on this topic
Red Hat
No answers on this topic
Professional Services
Progress Software Corporation
The entire professional services team was great to work with. The curriculum was tailored to our specific use cases. The group we worked with were very responsive, listened to our feedback, was very easy to schedule and accommodate. I cannot say enough good things about our professional services experience
Read full review
Perforce Software
No answers on this topic
Red Hat
No answers on this topic
Return on Investment
Progress Software Corporation
  • Chef is a good tool for baselining servers. It will be a good ROI when there are huge number of servers. For less number of servers maintaining a master will be an over head.
  • One good ROI will be that the Operations Team also gets into agile and DevOps methodologies. Operational teams can start writing scripts/automations to keep their infra more stable and their application stack more reliable.
  • Implementation of Chef eliminates the manual mode of doing things and everyone aligns to automation mind set. It helps in change of culture.
Read full review
Perforce Software
  • Cut deployment times down to around 1 hour from 4-5 hours.
  • Allows us to get a fully running system up from scratch in around 30 minutes.
  • Allows for a more clear view of what is required to get a host running.
Read full review
Red Hat
  • Red Hat Ansible Automation Platform offers automation and ML tools that allow me to automate complex IT tasks.
  • Through automation analytics, it is seamless to gain full visibility into automation performance allowing me to make informed decisions.
  • Red Hat Ansible Automation Platform allows me to move rapidly from insights to action.
  • Creating and sharing automation content in one place unify a team in one place hence enhancing real-time collaboration.
Read full review
ScreenShots