Skip to main content
TrustRadius
Progress Chef

Progress Chef

Overview

What is Progress Chef?

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,…

Read more
Recent Reviews

TrustRadius Insights

Chef is a versatile and powerful tool that has been widely embraced by various teams within organizations. Whether it's automating the …
Continue reading

Chef EAS Experience

10 out of 10
October 05, 2022
Incentivized
We are leveraging Chef Enterprise Automation stack for its numerous benefits. Chef Habitat allows us to be more agile in our application …
Continue reading

Get Cookin with Chef

9 out of 10
November 28, 2018
Incentivized
Chef is a tool that is being used as part of a DevOps enablement movement that we are implementing throughout our business unit, and …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Progress Chef?

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…

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

23 people also want pricing

Alternatives Pricing

What is Microsoft System Center?

Microsoft System Center Suite is a family of IT management software for network monitoring, updating and patching, endpoint protection with anti-malware, data protection and backup, ITIL- structured IT service management, remote administration and more. It is available in two editions: standard…

What is AWS CloudFormation?

AWS CloudFormation gives developers and systems administrators a way to create and manage a collection of related AWS resources, provisioning and updating them in a predictable fashion. Use AWS CloudFormation’s sample templates or create templates to describe the AWS resources, and any associated…

Return to navigation

Product Details

What is Progress Chef?

Chef Infrastructure Management enables DevOps teams to model and deploy secure and scalable infrastructure automation across any cloud, VM, and/or physical infrastructure.


Progress Chef Video

In this video, we will show you What Chef is in 60 seconds. Chef has made infrastructure automation and system compliance easier with Chef Workstation. New resources and tooling make the Chef experience lighter, simpler, and even more powerful than before. We continue to enhan...
 Show More

Progress Chef Integrations

Progress Chef Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

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 auditing and managing architectures.

Red Hat Ansible Automation Platform, HashiCorp Terraform, and Jenkins are common alternatives for Progress Chef.

Reviewers rate Ease of integration highest, with a score of 9.6.

The most common users of Progress Chef are from Mid-sized Companies (51-1,000 employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(49)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Chef is a versatile and powerful tool that has been widely embraced by various teams within organizations. Whether it's automating the deployment of development demo systems, configuring complex and interconnected systems, or managing large clusters, Chef has proven to be an invaluable asset for many users. According to Rizing, Chef has significantly reduced deployment time while improving consistency and quality. It has also addressed the challenge of having a repeatable setup, allowing users to reliably deploy similar environments multiple times. Additionally, having standard recipes for different server types has helped achieve a more consistent deployment and improved speed to market.

Many teams, such as the DevOps team at Rizing, use Chef to automate the deployment of infrastructure related to non-production development boxes. This enables rapid project setup regardless of the application or servers involved. The Infrastructure Engineering team leverages Chef to automate server deployment, perform functions like adding servers to Active Directory and installing applications, and configure HAProxy servers. AWS environments can be quickly built using Chef, with servers becoming fully functional in as little as 30 minutes. Moreover, Chef is utilized for managing Linux machines running NoSQL databases efficiently, facilitating changes to cluster environments and seamless machine replacement.

Chef's versatility extends beyond individual teams. It serves as middleware for private managed cloud software by installing a Chef-agent on each server and running the necessary cookbooks. Development teams also benefit from Chef's framework for creating repeatable infrastructure through automated application deployments. Furthermore, Chef enables scalable growth by allowing for the automated deployment and updating of configurations across large groups of servers.

Organizations have embraced Chef as part of their DevOps enablement movement, automating server creation, configuration, compliance testing, and infrastructure maintenance. Multiple Chef servers are used both within business units and organization-wide for Infrastructure as Code IaC purposes. From provisioning dev servers to managing on-premise systems and providing a single window into the status of managed endpoints, Chef proves valuable in various operational and development contexts. It is a trusted configuration management tool that spans both cloud and on-prem infrastructure, creating AWS environments with infrastructure as code using Chef cookbooks to create and configure services.

Powerful Configuration Management: Many users have found Chef to be a powerful tool for system configuration management, allowing them to efficiently manage and control the configurations of their infrastructure. With its comprehensive features and capabilities, Chef provides users with a reliable solution for ensuring consistency across their systems.

Flexible Code-Based Configuration: The use of code-based configuration in Chef has been highly praised by users for its flexibility and customizability. This feature enables users to easily define and modify configurations using code, providing greater control over their infrastructure. Additionally, the ability to track changes in a source control repository adds an extra layer of visibility and traceability.

Excellent Windows OS Support: Users appreciate Chef's excellent support for Windows OS properties, making it an ideal choice for configuring Windows systems. This robust support ensures that administrators can effectively manage and maintain their Windows servers, simplifying tasks such as software installation, configuration updates, and server deployment.

Confusing Array of Tools: Some users have found the array of tools in Chef to be confusing, making it difficult for them to navigate and use effectively. They suggest a unified approach that would make it easier for users to understand and utilize the various tools.

Steep Learning Curve with DSL: Users have mentioned that while the domain-specific language in Chef is powerful, it comes with a learning curve. Several reviewers have expressed that it can be challenging to grasp initially, requiring time, patience, and practice to become proficient.

Managing Large Clusters Can Be Messy: Managing large clusters with Chef has been described as messy and hard to troubleshoot by some users. This is especially true when nodes within the cluster have different sources for variables, leading to confusion and potential errors during configuration management.

Attribute Ratings

Reviews

(1-18 of 18)
Companies can't remove reviews or game the system. Here's why
October 05, 2022

Chef EAS Experience

Score 10 out of 10
Vetted Review
Verified User
Incentivized
Once the basics are understood, Chef provides a valuable tool in managing the state of systems. The integration of the various tools in the suite, while not perfect, do provide enough flexibility to cover any custom use cases. Chef seems to fit best in organizations that have experienced engineers to have some development background.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
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.
Rob Ericsson | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Chef is a very nice tool for establishing and maintaining a consistent configuration across a range of servers. In addition, Automate allows the continued monitoring and maintenance of servers so they don't drift from established standards. Overall, it deals very well with complex systems.

Chef is slightly less applicable for a micro-services approach where the servers are replicated from a simple and known starting point.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Chef is very well suited if you already have an in-house DevOps teams that have many years of experience working on Chef or related tools. Chef also works well when you need a lot of customization of the monitoring and management tool and related dashboards due to the complexity of the underlying IT. It is less appropriate for small IT environments or where internal IT expertise is limited.
February 21, 2020

Yes, Chef

Score 9 out of 10
Vetted Review
Verified User
Incentivized
Once you get your head around what it's supposed to be for, it can save massive amounts of time and headache. Getting a working cookbook is the first time you get to see its value. For me, until that point, I thought Chef was a waste of time. It's very well suited for setting up and managing lots of servers that all need the same configuration, and allows for integration testing as well. I'd say it's not well suited the other way, like if you're only building one persistent machine. It would take more time to write a cookbook to set it up than just to set it up manually.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Chef is extremely valuable when there is a need to manage configurations. Chef is also becoming extremely useful for one-off changes with their chef-run tooling in Chef Workstation. Habitat is becoming increasingly beneficial for the cloud/containerized immutable world. Inspec is something companies shouldn't live without. Chef appears to be working hard to ensure that no matter the use case they have the ability to help make lives easier and more automated.
Gene Baker | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Chef is a great tool to have when you need to have consistent server deployments as it offers the use of recipes and cookbooks. Because the recipe is used, the process is repeatable, and you can expect consistent deployment results. This helps prevent drift in the configuration deployments and that allows for standardization which helps for troubleshooting server and configuration issues. For me it is critical that if we deploy 7 reporting servers, that they are all configured the same, unless requirements call for them to be different. I prefer this, what we call the "Southwest model," being that Southwest Airlines uses one type of planes, 737s, albeit different variants. We prefer all of our Linux reporting boxes to be configured alike, all the same. It's the same with our database servers; they should all be the same unless we find a valid reason for them to differ. This is where the recipes are extremely helpful and valuable.
Christopher Maggiulli | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We run a large Liferay platform with a heavy load and high availability. We may have 6 developers working on the platform at a given time, and it takes them a week just to learn to set the environment up. With Chef, we can provision them a "local" environment with the push of a button.

In some instances we find Chef to be overkill. We have a large application landscape and some of our applications don't follow the traditional DTAP model (especially in systems that have serverless cloud components). We find the time it takes to write a cookbook for these systems may not provide a return on investment, especially if it isn't a critical system
Score 10 out of 10
Vetted Review
Verified User
Incentivized
For our cloud-based applications with multiple environments and microservices, Chef made life easier with infrastructure as code. Along with using puppet, we can bring up or configure the environments in minutes. Any charges to services can be easily managed using recipes and cookbooks. It's easy to learn, with much less/no learning curve if you know Linux/ruby. It's flexible to manage multiple cookbooks for different environments, and works well with the puppet.
Dylan Cauwels | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
Chef is great for managing large amounts of servers and ensuring that your applications run the same on all of them. While it may take a bit to learn Chef, the time saved is incredible at the end of it. However, if you are just getting into configuration management tools I would recommend looking into Ansible as it has a few key tradeoffs with Chef that can be substantial resource savers.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Our organization uses Chef to deploy new code in an automated fashion and it excels in this aspect. It is also well suited to updating existing configurations and push those changes in an automated fashion to large groups of servers. Having the ability to deploy simple or full system changes out to a large group of servers with little human interaction has cut down on time lost spinning up individual servers and allowed our teams to focus on other, operational problems and made us more efficient in dealing with problems with impact customers as opposed to building servers. Chef has enabled us to deploy at scale and helped grow our infrastructure as our company grows.
November 28, 2018

Get Cookin with Chef

Score 9 out of 10
Vetted Review
Verified User
Incentivized
Chef is really great when teams are attempting to migrate over from legacy systems. In our case, it was a switch over from AIX to Linux. Thus, it was a great opportunity to use Chef to build out deployment cookbooks that could then be used win order to set up the new servers in preparation for the upgrade.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Chef is useful for maintaining the servers in a known stable state for in-house datacenters. It helps to achieve infrastructure as code and helps in deployments as well. It is suitable for when there are a huge number of servers and you have to bring up the entire application stack in a safe and reliable way. It also helps in baselining the servers with same packages and corresponding versions.
Aiman Najjar | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Chef is great for managing complex and interconnected ecosystems. The centralized server makes it easy to gather facts from all nodes and store all parameter in centralized repository. For example, consider a scenario where your shared, main database hostname is going to change. With Chef, you can change the data bag and it will update all applications that are using this parameter.

For simpler, quick and dirty needs. Chef overhead may not always be necessary. In those cases, Chef solo can be used but I still see other tools are more appropriate for that case.
Kevin Van Heusen | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Chef is great for ensuring you have a repeatable infrastructure. Gone are the days of manually tweaking settings and then trying to remember what you did six months later. Chef enables your team to keep tabs on what's being changed due to its ability to keep its configuration and scripts inside source control. You can look at the history of what was configured and when.
Dan Lepinski | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Chef is suited for just about any situations in which you need to automate a process on a server. Once you've built out a cookbook, the chef run with take care of everything for you. Assuming nothing changes, you never have to worry about it again. The great thing about it is it's meant to automate everything so you, and your colleagues don't have to worry about it anything. You can make changes in one cookbook that can then update an entire farm of servers.
Score 7 out of 10
Vetted Review
Verified User
Incentivized
Depends if your operations team has a programming background. If your operations team is not well versed in programming then it might be difficult or you are working with an outdated team. Things like puppet, ansible, or even saltstack seem to be more user friendly for older operations people. Also, the learning curve for chef can be intimidating.
Return to navigation