We also looked at Puppet, Ansible, and Jenkins. Chef rolled things into one for us with the way that they were running their deployments.

It was more of a one stop convenience going with Chef. A lot of the features, plugins, and compatibility items that we were looking for were already bundled into the package. Rather than piecemeal things together with the other services, we directly went with Chef to make sure it was a smooth, functional package for us. We went with Chef and its suite of tools to manage things more centrally.

We considered Chef, Puppet, Ansible, and homegrown solutions. We had a couple people who used to use Ansible and some people who had previously used Chef. I think we just settled on Chef after trying it because we liked that it was Ruby-based, and there were a lot of community cookbooks already. This lined up parallel with what we wanted to be doing.

We have also looked at Ansible, Puppet, and SaltStack. They all sort of have managed solutions which you can potentially purchase. Puppet definitely has a sort of old school thought process working behind it.

Over two to three years, we have not seen a stable release of Salt. They have some good ideas, but it isn't stable enough yet to use in a production environment.

Make sure that the operations crew has a background in Ruby, if you're going to choose Chef. If you have a Python crew, then look at Ansible as a potential option. Because I think they're catching up, and they will surpass Chef in pretty much every way sometime in the next 12 to 18 months.

Though, Chef Automate is still the most reliable solution.

We were already using Chef and Puppet for most of our DevOps. These were our only choices.

We were able to evaluate Terraform and Ansible.

We looked at a combination of open source and other paid solutions. It was hard because Chef offered many options that others didn't, so it wasn't a one-to-one comparison.

Chef had better functionality, flexibility, and price. It is a clean product that is easy to work with and our customers like the product.

We looked at other product like Puppet. We are also using Ansible. However, Chef is the market leader, so we went with that.

Chef is more effective. It provides the hooks, so we can do customization. The product is more versatile. For example, we can deploy using this tool, not only with cloud, but simultaneously on-premise. So, it is quite powerful.

We used SPO Orchestrator. And before Chef there was one proof of concept with Puppet but for some reason, Puppet was not as developer-oriented. Many of our in-house people found Chef to be more user-friendly, from an administrative perspective, so we narrowed it down to Chef.

I don't like some of the products offered by VMware. I like the automation offered by Chef and Puppet.

We chose Chef because some clients have some legacy systems and decided to work with them. We don't really like work with VMs, but when we have to, we use Puppet.

We have also used Ansible and Puppet. We have been using Ansible ever since it deployed a Docker containers with Kubernetes. We are also using Kubernetes to help manage our product assistance. 

We have our product integrated with Chef and Ansible. They are not integrated on the same system because we use two different systems. We are not using Puppet anymore.

We tried Ansible and Jenkins. However, because we use Terraform in our products, these weren't the most fitting solutions. Chef was the best solution for helping us build our infrastructure.

We considered Puppet and Ansible. We went with Chef because Chef uses Ruby and Ruby is pretty popular right now.