We performed a comparison between Chef and UrbanCode Deploy based on real PeerSpot user reviews.
Find out in this report how the two Release Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."We have had less production issues since using Chef to automate our provisioning."
"The product is useful for automating processes."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"Chef can be scaled as needed. The Chef server itself can scale but it depends on the available resources. You can upgrade specific resources to meet the demand. Similarly, with clients, you can add as many clients as you need. Again, this depends on the server resources. If the server has enough resources, it can handle the number of servers required to manage the infrastructure. Chef can be scaled to meet the needs of the infrastructure being managed."
"If you're handy enough with DSL and you can present your own front-facing interface to your developers, then you can actually have a lot more granular control with Chef in operations over what developers can perform and what they can't."
"The most valuable feature is the language that it uses: Ruby."
"I wanted to monitor a hybrid cloud environment, one using AWS and Azure. If I have to provision/orchestrate between multiple cloud platforms, I can use Chef as a one-stop solution, to broker between those cloud platforms and orchestrate around them, rather than going directly into each of the cloud-vendors' consoles."
"It is very easy to make a software release. It used to take us at least a couple of hours to make a release, now we went to production with a new one last night. This new release took me five minutes."
"The stability is good. I haven't experienced any issues."
"The most valuable feature is the snapshot functionality, which allows us to access previous versions of the artifacts."
"Stable solution that's good for automating the CI/CD pipeline: from development to production."
"The most valuable functionality is the ability to define the deployment process, schedule the deployment and automatically execute the deployments to different environments."
"The solution handles complex deployments very efficiently."
"I would like them to add database specific items, configuration items, and migration tools. Not necessarily on the builder side or the actual setup of the system, but more of a migration package for your different database sets, such as MongoDB, your extenders, etc. I want to see how that would function with a transition out to AWS for Aurora services and any of the RDBMS packages."
"They could provide more features, so the recipes could be developed in a simpler and faster way. There is still a lot of room for improvement, providing better functionalities when creating recipes."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"The agent on the server sometimes acts finicky."
"I would like to see more security features for Chef and more automation."
"I would also like to see more analytics and reporting features. Currently, the analytics and reporting features are limited. I'll have to start building my own custom solution with Power BI or Tableau or something like that. If it came with built-in analytics and reporting features that would be great."
"The solution could improve in managing role-based access. This would be helpful."
"There appears to be no effort to fix the command line utility functionality, which is definitely broken, provides a false positive for a result when you perform the operation, and doesn't work."
"I would like to have the agent up and running at all times, as opposed to only while it is in the DevOps pipeline."
"The interface allows access in a number of ways but that can be confusing."
"I certainly would like to have a better way to pass information between deployment steps using UrbanCode Deploy because that's really difficult to do."
"I would like to see more reporting for container architecture."
"The technical support of the solution could definitely be improved as PMRs take long to resolve."
"The scalability of this application needs improvement. Changes and variations in the application become bottlenecks as they need to be more seamless and comfortable."
Chef is ranked 15th in Release Automation with 18 reviews while UrbanCode Deploy is ranked 6th in Release Automation with 27 reviews. Chef is rated 8.0, while UrbanCode Deploy is rated 7.8. The top reviewer of Chef writes "Useful for large infrastructure, reliable, but steep learning cureve". On the other hand, the top reviewer of UrbanCode Deploy writes "It offers OOTB plugins for middleware". Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps and Microsoft Configuration Manager, whereas UrbanCode Deploy is most compared with GitLab, Red Hat Ansible Automation Platform, Microsoft Azure DevOps, HCL Launch and Spinnaker. See our Chef vs. UrbanCode Deploy report.
See our list of best Release Automation vendors.
We monitor all Release Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
